Recently I switched back to a Windows XP box (XPB) from an OS X Leopard (OSXBL) machine. Since OSXBL would have a new user, I figured that I might as well install Snow Leopard (OSXBSL) on the machine. Everything worked out pretty well; but I was surprised to find that OSXBSL could no access SMB shares on XPB. This surprised me as nothing changed on XPB; so seemingly it was Snow Leopard to blame. I went through a standard checklist, followed by “tips” from the web:
- Reboot both machines
- Confirm share settings (passwords, share name)
- Turn off share passwords
- Verify firewall on XPB; also tried out turning off firewall (both McAfee and built in)
- Enabled ports that windows sharing might use
- Can ping XPB from OSXBSL
- Set a workgroup name on OSXBSL
- Turned on SMB sharing on OSXBSL (via a tip, it sounds odd, but I gave it a try)
- Turned off IPV6 on OSXBSL
None of that helped.
Reading on I found a lot of people angry about this kind of issue. Posts go back to at least 2005, and they seem to be facing the exact same problem. Eventually I came upon a post that mentioned the problem is that finder can’t mount the shares, but you can mount them just fine using ‘mount’ command. While that did not work for me, it got me going in the direction of trying to access the share using ‘smbclient’ (via this post), and that is when things got a lot more interesting (there were literally hours and hours of banging my head against the wall to reach this point).
Here is what it reported:
zen:~ admin$ smbclient -L stargate Password: Domain=[STARGATE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Sharename Type Comment --------- ---- ------- IPC$ IPC Remote IPC R$ Disk Default share Grant Disk O$ Disk Default share ADMIN$ Disk Remote Admin C$ Disk Default share S$ Disk Default share Domain=[STARGATE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- Workgroup Master --------- -------
That confirms that OSXBSL can “see” XPB’s SMB shares. Next I tried mounting a share and found this:
zen:~ admin$ smbclient \\\\stargate\\Grant --user=grettke Password: Domain=[STARGATE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES
Here are the errors that showed up in the System Event Log on XPB:
Type: Error Source: Srv Description: The server's configuration parameter "irpstacksize" is too small for the server to use a local device. Please increase the value of this parameter.
Searching for this error message, I found this thread (and many like it) that essentially says that you get this error when you use virus scan software. McAfee lives on this computer (while I’ve never had a problem with a Windows box, ever, I don’t want there to be one and I don’t want to have to spend too much time administrating this thing). Here is what McAfee had to say.
After making the changes I reset everything to its normal state (OSXBSL no sharing, IPV6 automatic, no workgroup name and on XPB turned on the firewall and set the share permissions again). Testing out smbclient, no errors were reported, and finder quite happily mounted the shares, too.
What a time-consuming problem; the solution was not obvious at all!
Added a local copy of the solution here.
11 thoughts on “Snow Leopard Can't Access Windows XP Over SMB Woes”
What a lot of work to do something simple. I’m sorry you had to go through that, but undoubtedly you’ll save someone else a lot of trouble.
The title of this post is what I thought was the simplest thing for which someone would search for in Google in regards to the problem (It is what I searched for and found nothing).
Hopefully no one would have to go through it again.
I wonder if many people are connecting OS X to Windows?
I, too, have a slight problem. I’m working with OS X 10.6.3 and have access to a drive through Windows. I have no problem accessing the folders there, HOWEVER, by boss has issues in the drive. See below.
I can not create a folder or save a file in any folder you create. This is the error I get.
Error when creating a folder: Unable to create the folder “New FOlder” Access is denied.
Error when saving a file: Word cannot save or create this file. Make sure that the disk you want to save the file on is not full, write-protected, or damaged.
She has Windows XP Professional Service Pack 3.
Hat’s off to you Grant!! I’ve been working on this problem for 3 hours (probably far longer than you spent) with no luck until I found your post. As soon as I saw your reference to ‘irpstacksize’ the lights went on as I had seen this error in the event viewer but didn’t make the connection.
Thanks for your generosity, sir!
The pleasure is mine knowing that knowing that it helped someone else.
Thanks for letting me know!