Suddenly unable to connect to ANY SMB share (XP, Vista, etc.)

Discussion in 'Mac OS X Server, Xserve, and Networking' started by striders, Oct 23, 2009.

  1. striders macrumors 6502

    Joined:
    Mar 11, 2009
    #1
    For the past 1 year, I am able to connect to my Windows "server", which is a Windows box running WinXP. All I need to do just go to Finder -> Connect and type this:

    smb://MYWINDOWSBOX/c$

    However, as of yesterday, suddenly it couldn't My MBP can ping, VNC and heck even do Windows RDP to ANY of my Windows boxes. It just does not want to connect via Finder file sharing (SMB).

    I am trying to trace back what I did this past week that may cause this problem, but I couldn't think of any. All I did these past 1 week are:

    1) Install DropBox client app
    2) Install new certificate in Keychain access (iPhone development)
    3) Uninstall StuffIt


    FYI, the error I am getting is:

    The Finder cannot complete the operation because some data in "smb://MYCOMPUTERNAME/c$" could not be read or written. [Error code -36]

    However, if I go to Terminal and type the following: smbclient \\\\MYCOMPUTER\\C$, it DOES WORKS!! I can browse the share, change directory, etc.

    It seems something is broken between Finder and SMB.

    Can anyone offer any advise? Any configuration file to change?
     
  2. efplaya85 macrumors newbie

    Joined:
    Mar 14, 2009
    #2
    Same issue

    I'm having the same issue where I suddenly I cannot connect to the smb. After I restart osx everything is back to normal and then after a few days the same problem. Bump... Anyone?
     
  3. striders thread starter macrumors 6502

    Joined:
    Mar 11, 2009
    #3
    I found the fix for this. Apparently, Norton Internet Security has a new update and it will block ALL SMB traffic. If you have NIS on the Win box, check the log and disable "Intrusion detection" or something like that.
     
  4. MagnusVonMagnum macrumors 601

    MagnusVonMagnum

    Joined:
    Jun 18, 2007
    #4
    I don't have NIS on my PC, but since the October 22nd Leopard Security Update, I cannot seem to properly access my SMB shares from my PowerMac. I knew something was up when it asked for permission to allow some process or the other to run (NMBD ?) related to NetBios and/or SMB. It asks this EVERY time I reboot now and even when I click allow, it doesn't function correctly anymore. Resetting Sharing settings and SMB in the System Preferences has no effect. This is making it nigh impossible to share files with my PC any longer and I'm not seeing much about the problem online. I may have to restore from a pre-update backup, which means losing the security patches an the last Safari update (only two things that could have caused the problem that I'm aware of). If I run findsmb from the command line, it shows the address for my computer as Samba 3.0. XBMC on my AppleTV cannot find anything through the normal SMB address either, but could locate them through the ZeroConf option which added a :445 to the address.
     
  5. dazey macrumors 6502

    Joined:
    Dec 9, 2005
    #5
    Norton, Mac and Security in the same sentence is just wrong ;)
     
  6. MagnusVonMagnum macrumors 601

    MagnusVonMagnum

    Joined:
    Jun 18, 2007
    #6
    It seems after much toying around that the problem was that configd was not running for some reason since the last network change. I had rebooted into Tiger a few days ago to update Safari to the latest version and when I rebooted into Leopard my network connection was fuxored somehow and it would not restart automatically so I manually set the connections to the router and all seemed to be well except apparently configd wasn't running since after a few reboots I re-enabled automatic mode and the first thing it did was ask permission to allow incoming connections to configd and then all my network connections for SMB magically reappeared. Why it's tying command-line programs into automatic versus manual configuration settings is beyond me as is why it failed on the reboot in the first place (not the first time that happened either, although I don't recall it screwing up the SMB connections before on manual).
     

Share This Page