SMB connections broken in Leopard

Add me to the list of people who can no longer connect to Windows

Same problem here, was able to mount the shared folders on my Windows machine under 10.5, but with 10.5.1 I can see the shared Windows machine (under 'shared') and even the shared volumes/folders, but it does not want to mount.

In my case, it seems to be a DNS Resolution issue, I can connect via smb://ipaddress but not by smb://servername...

I can't mount my PC's shared volumes from Finder. It just says that the mount failed, no error code. I found these lines in /var/log/system.log:

Dec 20 07:55:47 MacGeorge kernel[0]: smb_maperr32: no direct map for 32 bit server error (0xc0000205)
Dec 20 07:55:47 MacGeorge /System/Library/CoreServices/NetAuthAgent.app/Contents/MacOS/NetAuthAgent[173]: smb_mount: open session failed!: syserr = Broken pipe

The PC is domain-attached.

I've got the same problem. Macrumors's assessment of 10.5.2 says it will have some SMB fixes (see http://www.macrumors.com/2007/12/18/apple-seeds-mac-os-x-10-5-2-and-java-se-6-pr eview-8-for-leopard/) -- of course we don't know if this will fix our problems 🙂

So I finally got my HP MediaVault to mount (it now shows up on the "shared" list in the finder) by deleting /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist. I can't say that this is a permanent fix, as I've had the filesystem mount occasionally before (and quite at random), but now that it's mounted I don't want to mess with it.

Let's hope 10.5.2 fixes this
Bobski

Thanks, I tried this, but no improvement. I've also tried the other suggestions found on this and similar threads, such as smbclient, restarting the finder, and variations on the command syntax. Still, I always get the "broken pipe" error. I can mount a NetApp volume, but not my Windows XP volume.

George - yeh, I think there's so many things wrong with this part of the OS that I hit upon a little piece that happened to help me, but there's a ton more problems out there.

Anyway, another thing that I did as a work-around was find the IP address of the Windows (or in my case HP MediaVault) system, and use the Finder [Apple-K] ("Connect as..") and type in SMB://<ip address>. If your router supports it, have it assign the same IP address each time through DHCP (based on the MAC), then you can use the same address each time. (You may have to restart your router). So you might give that a try.
Cheers
Bobski

Solved! It appears that it was a 3rd party-related problem after all. Did a clean-up of the system (I went for the upgrade option in the Leopard installer in November last year) and now the contents of the folders magically appear. Some of the apps I removed (no definitive answer on the possible culprit unfortunately) are: Mozy Backup, Divx Player and Second Life. To try and resolve another problem with a firewire drive that does not mount I did a reset-nvram and reset-all in open firmware, but I don't think this is part of the solution. The final thing I did was a repair disk permissions (again) after the cleanup.

It re-confirms my experience that most problems with Os X can be traced back to third-party solutions (and I use a lot of them). Hope it's helpful to someone...

Hi

finally i also solved my samba connection issue...
I played with the /etc/nsmb.conf and tried the different minauth parameters and finally it worked for both finder and command line!

My /etc/nsmb.conf looks like this now:

[default]
#minauth=ntlmv2
#minauth=ntlm
minauth=lm
#minauth=none
port445=normal
#port445=netbios_only
domain=TDCH
streams=yes

Interestingly enough I have a similar problem, although not the same!

As I detailed in another thread, I have upgraded to Leopard recently and lost my NAS, however Windows XP shares are working prefectly.

Anyway, I don't ... yet ... have a solution, I just want my name added to the list! 🙂

Interesting. I can get my Windoze volumes to mount perfectly (though I use the IP address, not the DNS or WINS names) on my dual G5, but can't get them to mount at all (error -36) on my MacBook Pro.

For the most part, the people with the problem seem to be running Intel machines.

Wonder if that's relevant somehow....

/Bill

Well I thought dchao99's solution worked for me. I set up a new Network profile, switched to "workgroup" under WINS and hit Apply. Instantly my two SMB shares that were missing showed up. Woo hoo! But about 5 minutes later, they just disappeared. This is really frustrating! Looking forward to a lasting solution...

Stormbuster wrote:
Solved! It appears that it was a 3rd party-related problem after all. Did a clean-up of the system (I went for the upgrade option in the Leopard installer in November last year) and now the contents of the folders magically appear. Some of the apps I removed (no definitive answer on the possible culprit unfortunately) are: Mozy Backup, Divx Player and Second Life. To try and resolve another problem with a firewire drive that does not mount I did a reset-nvram and reset-all in open firmware, but I don't think this is part of the solution. The final thing I did was a repair disk permissions (again) after the cleanup.

It re-confirms my experience that most problems with Os X can be traced back to third-party solutions (and I use a lot of them). Hope it's helpful to someone...

The problem was DiVX Player QuickTime plugin. This is a known issue. To play a DiVX video file use the free Perian plugin.

I've got Perian installed (as well as
AC3MovieImport.component
Perian.component
AppleIntermediateCodec.component
Flip4Mac WMV Advanced.component
Flip4Mac WMV Export.component
Flip4Mac WMV Import.component
FLV.component
in /Library/QuickTime/. No DiVX that I can find, unless it's hiding somewhere else. Any suggestions as to where else it might be hiding?

Another piece of data to add here... every time I try one of the workarounds listed here - like the Command-K smb://address, using smbclient at the command line, or creating a new network profile - they all result in the smb shares showing up in the SHARED column, only to disappear soon after. It really feels like the SMB shares are responding to a "ping", regardless of what that ping is. They are "awakened" by this ping, then they "sleep" after a period of inactivity.

If I knew more about the internal workings of SMB within OS X, this might be an important clue as to what's going on. Maybe it will to someone else?