Can't access smb shares after 10.9.5 upgrade

After the upgrade to 10.9.5 (from 10.9.4) I can not anymore access my smb shares on a NAS server (Thecus N3200PRO) dispite the upgrade says that it "improves the reliability of accessing files located on an SMB server". It had the exact opposite effect with my system.
The NAS server is visible, but after I log in no files or folders are shown (finder window is empy). Also to disconnect the smb share it takes much longer than usual.
To access it with cifs protocol does not help, neither.
Also the workaround by Reinfire (Michael Larson in Can't connect to SMB share after upgrade, to use smb1 instead of the upgrade) does not help at all.
Any solution out there?
-- thanks

hi there,
just a wild guess, but have you tried to connect via Terminal?
/sbin/mount_smbfs //userid:password@ip-of-server/name-of-share
or
/sbin/mount_smbfs //userid:password@dns_name-of-server/name-of-share
You need to have administrative privileges on your Mac to execute said command successfully.
For additional information you can enter (while in Terminal):
man mount_smbfs
and
man nsmb.conf
Glad to hear the problem is solved

Similar Messages

  • TS3899 Can't access my email after restore and iOS upgrade

    I restored my iPad -which wiped out my email accounts - and upgraded t latestt iOS
    I re-entered my email account properties but now I can't receive or send email any longer. Error states it can't access the pop server.
    I've checked account settings are same as iPhone and pc which are accessing email just fine
    Help to troubleshoot / fix appreciated
    Thx
    Rob

    The easiest thing to do is to restore from backup if you have one. The backup will continue the email settings. Do you have a recent backup?

  • Windows computers can not access smb-shares in Lion

    I have updated von SL to Lion Server. Now, I don't gave Access to my Windows shares from any Windows Computers. If I connect a Windows share u.e. froom Windows 7 Workstation I will see a window with username and password for the share. But the username und password from lion for this share will not work. It was no problem in SL. Any idea?

    To get this to work on windows 7 I...:
    Start > Computer
    Disconnected my mapped netowrk drive that would not connect
    Selected the Map network drive button in the toolbar at the top
    Typed in the folder location manually (if you try the browse it will fail)
    Selected Connect using different credentials
    Selected Finish
    On the credentials screen that pops up:
    User name: <SERVER\username>I found that my server name had to be in capitals (/private/var/log/krb5kdc/kdc.log helps you know exactly what it is)
    Password: <your password>
    Select Remember my credentials
    Select OK
    After this i found no issues access any of the shares on the server and everything came back to life

  • Can't access any shares on the network

    Hi,
    As the topic says, I can't access any shares on the network. I've tried connecting to a Iomega NAS, Windows 7 laptop, and a macMini. In the "Shared" list in finder im able to see all the shares, I'm able to click them and see the folders they share, but when I try to open one of the folders I get an error, no matter which share it is:
    +"The operation can’t be completed because the original item for “<folder name>” can’t be found."+
    The shares can all access each other, and they can access my folders. I just can't access any folder on the network.
    I got a mac pro with osx 10.6.2 and have all the latest updates.
    How can I solve this problem?
    Thanks.

    Well, try this (I was able to fix my with these steps):
    Go Utilities > Disk Utility
    Select your Startup Disk, e.g. Macintosh HD
    Then, under the First Aid Tab, click Verify Disk Permissions.
    If there are errors, then click repair Disk Permissions.
    After it is done, restart the computer and see if your problem is resolved.
    I hope this help.
    Zeke
    www.ZekeYuen.com/blog/

  • I can't access folder share in WIndows Server 2012 R2 from windows 8.1

    i have a strange case:
    I have a Windows Server 2012 R2 machine with a shared folder. Accessing this folder using a Win7, Win8,
    Win 2008 R2 machine using \\servername  works fine but form windows 8.1 or windows
    2012 r2 i can't so any one can help me. 

    Hi,
    Would you please let me know the complete error message that you can find, when can’t access to the share folder
    that host in the Windows Server 2012 R2?
    If you logon the Windows 8.1 (or server 2012 r2) with administrator account, will encounter the same issue?
    Meanwhile, please access the share folder via \\server’s IP address\share folder. Then please check if this issue still persists.
    In addition, there is a similar thread. Please refer to and check if can help you.
    Can't
    access UNC share on Windows Server 2012 R2
    Hope this helps.
    Best regards,
    Justin Gu

  • How can i access mocha in after effects cs6

    how can i access mocha in after effects cs6

    To use mocha AE in After Effects CS6, select the item to track and choose Animation > Track in mocha AE.

  • How can I access apple store after updated to OS- 6?

    How Can I access apple store after updating my i pad to OS-6?

    Look here:
    C:\Program Files\National Instruments\LabVIEW x.x\examples\imaq\*.*

  • Why the apple store is so expensive and why the apple users can't access for free after spending huge amount in apple phone ?

    Why the apple store is so expensive and why the apple users can't access for free after spending huge amount in apple phone ?

    The Apple store is correct. The warranty is not international, and Apple will not accept or return iPhones shipped from a different country.  You need to ship the phone to somebody in Hong Kong who can take it in to Apple for repair, or pay a third party repair shop in the Philippines to fix it.

  • Can't access suggestions in Google toolbar dropdown since upgrading to F4.Suggestions appear but when I click on one nothing happens.

    Can't access suggestions in Google toolbar dropdown since upgrading to F4.Suggestions appear but when I click on one nothing happens - it just returns to what I've typed already.
    eg If I type the word 'honey' a number of suggestions appear. One is 'honey crackles'. If I click on that I'm back to 'honey' again

    Try reading the steps at [[Websites look wrong or appear differently than they should]]

  • Mac Pro accessing SMB shares on a windows server. After being left on all night, the MP gets "file unavailable" messages when opening files on the share.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

  • Windows XP users can't access SMB/CIFS shares on MAC OSX10.4.4 Xserve bug?

    The Xserves are new for us. This problem involves two of the 10.4 xerserves.
    1 serves as an Open Directory System Master(10.4.3). 2 Serves as a file share & backup (10.4.4).
    Both are production machines and cannot easily be restarted.
    There is no Windows network, Active Directory or Windows domain in our network.
    We created a SMB and AFP share on the file server which is a member of the Open Directory. (It is bound and kerberized to server 1).
    The users all have accounts in the OD system and all passwords are Open Directory. Our users can ssh into the various xserves (including the file share server 2) and authenticate against OD.
    We made the shares available via smb under Protocols --> Windows File Settings. We turned the Windows Service on in Server Admin. I'ts a standalone server and all the authentication types are checked under access.
    The MAC (powerbook) users can access the share fine. The Windows users can't. The Windows laptops can see the file share server (through search - not visable is Network Neighborhood) but when they try and connect they are presented by an authentication box that just keeps cycling over and over regardless of what the user types as user name & passwd.
    I tried to access the smb share with my powerbook(10.4.4) and have the same issue. I'm presented with an authentication box but authentication fails.
    The Windows File Service Log shows:
    auth.c:checkntlmpassword(312)
    checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
    [2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
    User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
    [2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
    opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
    [2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
    checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
    [2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
    User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
    [2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
    opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
    [2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
    checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
    [2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/smbd/server.c:exit_server(595)
    Closing connections
    I've googled this error and it seems that there a lot of engineers out there with the same problem but no answers. Could this be a bug with Apple's SMB process? Is there something I've missed? (I've looked at the smb.conf and have even turned off deny clear text passwords - I've even tried granting guest access) Anyone have any ideas?

    On the server itself, run the following in the Terminal:
    (from a few different sources):
    run ps -auxw | grep Password
    to see if Password service is running
    Also check the logs in /Library/Logs/PasswordService
    Try: id username
    and see if you get some info returned.
    Ex: id jimguy
    You should get some info about uid, gid, groups.
    sudo killall -USR1 DirectoryService
    Then try to login from a client machine.
    Be sure to re-issue
    sudo killall -USR1 DirectoryService
    in order to stop the (far more) verbose logging.
    Then check the logs in /Library/Logs/DirectoryService
    In Open Directory, you might want to revert to standalone (this will destory the existing OD setup) and then re-promote to OD Master. You'll lose all OD users however when doing so. If you don't have many, this may be best.
    You'll want to verify the hostname, and forward & reverse DNS lookups before re-promoting, and watch for any errors when promoting to OD master
    See, when you say "The real clue is that I'm unable to access the shares from my Powerbook G4 with my Open Directory account. I can log in to the file share as the local admin though and that's why I'm thinking there is a bug in the samba/OD relationship. " - that's the real clue indeed.
    The local admin account, the first admin account you setup on the server, is indeed local, and resides in NetInfo, not Open Directory.
    So something is afoul in your OD.

  • Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

    I have two  I Mac's Intel i7 models.
    I have some problems getting them to write files to SMB shares.
    The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
    I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
    I have confirmed the user account can write to the share by having the user do so from a windows box.
    any help from any of you mac guys would be great!!!!
    Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
    Peace Out

    I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

  • Can't connect to SMB share after upgrade

    Just upgraded to 10.9 Mavericks and can no longer connect to our SMB file share on the network.  Several of us have tried connecting to it on this machine and all we get is
    There was a problem connecting to the server "xxxxxxx.domain.com".
    You do not have permission to access this server.
    Anyone else having this problem? 

    I have been searching high and low since yesterday afternoon for an answer to this.  My problem is not connecting to an SMB share (well, it was, as the old Cmd+K to connect to the SMB share would close quickly) but instead of the old Mac way of using Cmd+K and the IP address, I simply clicked on the available NAS SMB share under Shared and it is a massively fast connection.  The old SMB connection would take minutes to open the next folder. So, connecting as you would under Windows helped fix that problem, BUT...
    1.  The NAS SMB share times out regularly and you have to eject & reconnect.  Annoying.
    2.  Worse than this is I can not open any documents on the share, only navigate it.  I have to copy paste the documents to my local ssd, manipulate, copy back.  Any new file I copy on, or edit and copy on, the NAS SMB share I can navigate to and open.  But if I try to click a pre-Mavericks existing file, I get "Can not open 'excel/word/acrobat.app' with the -36" error.  Total BS. 
    3.  Even more weird, if I click spacebar on ANY file on the SMB Share it will pop up in preview.  Double click to open and error message.
    4.  If I copy a document attached to an email (Outlook 2011) to the server it is corrupt.  If I copy the file to local ssd, then to the NAS SMB, the same file works perfectly fine. 
    This is completely ridiculous and needs a fix immediately.  I'm going to try using Reinfire's link right now and see if that helps. 
    My NAS is a Netgear ReadyNAS 516 (linux/unix OS) I use in my office.  Computer is MBPr March 2013.    

  • All of the sudden our Mac OS X 10.7.4 operating systems are very slow to access SMB shares on our MS2008 file server

    Monday all of our OS X Lion Macs can access SMB file shares on our file server and we come in Tuesday morning and now they take at least 1 minute to pull up the file share and sometimes longer.   Windows PC's are immediate when connecting to the same shares.  I've seen where others with different versions of OS Xhave this issue but what gets me is it happend all at once to machines that were working perfectly the day before.
    I've also looked into changes on our servers and as far as I can tell there have been none. 
    Does anyone have any ideas?     Thanks....

    This solution worked for me!
    I had a MobileMe account with iDisk configured on my MBP even though I never actually used it.  The night they officially shutdown MobileMe the next morning I could no longer connect to my work's SMB file shares (Windows server shares).  I found a work around based on some other support threads.  If in the "Connect to Server" address field in Finder I specified my crendentials (i.e. smb://username:password@server/) then it worked perfectly fine.  This told me it was a crendential issue.  Simply deleting the saved server crendentials in KeyChain Access did not resolve the issue.  No matter what I would did it would not prompt for login crendentials.  Since my Mac login is different than my work domain login I was dead in the water without manually specifiying (not a permenant solution).
    After finding this thread I did the following steps and it resolved the issue 100%.
    1. Open Terminal
    2. cd ~/Library/Preferences
    3. ls .GlobalPreferences.plist to verify file exists in that directory
    4. rm .GlobalPreferences.plist to delete file
    5. ls .GlobalPreferences.plist to verify file no longer exists
    4. Go to Force quit to relaunch Finder
    5. Lauch "Connect to Server" within Finder and all was good, server connects perfectly
    Thank you very much DavidRSewell!!!!

  • Can't browse samba shares after samba upgrade (3.0.26a-4 - 3.0.27A-1)

    Hi all,
    After today's samba update, i am unable to browse my samba shares:
    As seen in pacman.log:
    [2007-11-16 15:55] updating smbclient (3.0.26a-2 -> 3.0.27A-1)
    [2007-11-16 15:55] updating samba (3.0.26a-4 -> 3.0.27A-1)
    Ive had this samba server running for a long time and never had any trouble. Apart from the system update i havent changed anything.
    I have tried two machines to access it, a ubuntu and a windows one. The ubuntu one would mount it all right, but when you try browsing it it gives an 'Input/output error', these are the last lines found in /var/log/messages file:
    Nov 16 19:42:06 Naboo kernel: [ 855.043000] SMB connection re-established (-5)
    Nov 16 19:42:34 Naboo kernel: [ 883.442000] smb_add_request: request [cdccae80, mid=11] timed out!
    Nov 16 19:42:34 Naboo kernel: [ 883.442000] smb_proc_readdir_long: error=-5, breaking
    Nov 16 19:42:34 Naboo kernel: [ 883.488000] SMB connection re-established (-5)
    Nov 16 19:42:36 Naboo kernel: [ 885.375000] smb_add_request: request [cdccac80, mid=18] timed out!
    Nov 16 19:42:36 Naboo kernel: [ 885.375000] smb_proc_readdir_long: error=-5, breaking
    Nov 16 19:43:04 Naboo kernel: [ 913.607000] smb_add_request: request [cdccae80, mid=21] timed out!
    Nov 16 19:43:04 Naboo kernel: [ 913.608000] smb_proc_readdir_long: error=-5, breaking
    Nov 16 19:43:05 Naboo kernel: [ 913.648000] SMB connection re-established (-5)
    The windows machine would actually show the files in the shared directory but after a very long wait. Browsing and reading files was taking such a long time that windows seemed like frozen so i had to restart.
    I also tried rebooting the server but to no avail.
    Anyone else with the same problem?
    Last edited by feralert (2007-11-16 20:48:31)

    Same problem here. I can Browse remote smb filesystem with smbclient but when I mount smbfs i cannot browse folder - my terminal hangs and in syslog i receive
    Nov 19 09:35:16 skyscraper SMB connection re-established (-5)
    Nov 19 09:35:16 skyscraper smb_proc_readdir_long: error=-512, breaking
    Nov 19 09:35:17 skyscraper SMB connection re-established (-5)
    Nov 19 09:35:18 skyscraper smb_proc_readdir_long: error=-512, breaking
    Nov 19 09:35:18 skyscraper SMB connection re-established (-5)
    Nov 19 09:35:27 skyscraper SMB connection re-established (-5)
    Nov 19 09:35:48 skyscraper smb_add_request: request [d34f2b00, mid=22] timed out!
    Nov 19 09:35:48 skyscraper smb_proc_readdir_long: error=-5, breaking
    Nov 19 09:36:18 skyscraper smb_add_request: request [d34f2b00, mid=31] timed out!
    Nov 19 09:36:18 skyscraper smb_proc_readdir_long: error=-5, breaking

Maybe you are looking for