User profile for user: dev0
dev0 Author
User level: Level 1
5 points

Finder error -36 when connecting to server - smbclient in terminal works

Finder > Go > Connect to Server

When ever I need to connect to a smb server using Finder, I get the constant error -36.

In console :

mount_smbfs: session setup phase failed: syserr = Socket is not connected
mount_smbfs: could not login to server EXIT15: syserr = Socket is not connected
mount_smbfs: 2 failures to open smb device: syserr = Resource busy
mount_smbfs: session setup phase failed: syserr = Authentication error
mount_smbfs: error from NetrShareEnum call: exception = 382312500

I can sometimes select the share to mount, and it tries for a few seconds, never succeeds.

10.4.10, but this was also case previously. We have every single Mac with this symptom so it is 7 work units at the moment, a Mac Pro, MacBook Pros, MacBook, Mac mini.
Wired, wireless, and even VPN, no matter how the mac is connected to the net.
Every non-Mac server at work tested gives this error when trying to connect to their shares.

smbclient in terminal works.

http://www.macwindows.com/tiger.html and Apple kbase article 301580 suggestions for nsmb.conf didn't make any difference. (the nsmb noauth being a very poor choice if it would work)
smb.conf and nsmb.conf any security settings don't make any difference.

I have working details for connection, so share, ip and dns name, username and password for connection work.

Connecting from Terminal works.
Connecting from any Windows or Linux virtual machine on Fusion on these same Macs work too.

I have changed the workgroup to the correct one in Directory Access.

I have tried all connection syntaxes suggested in http://www.macwindows.com/tiger.html - none of them still work in Finder, always identical results.

smbclient //dns-name-or-ip/sharename -W workgroup -U username

is the only viable workaround at the moment.

Domain=[dnsnameofwhereconnected] OS=[EMC-SNAS:T5.4.21.400] Server=[NT1]
is what smbclient gives for server details when its connected.

As smb works from command line, it's not smb itself that is affected. Just Finder.

I don't have access to edit any settings on the servers that we need to connect to. Only sharename and password that work for connection, but don't allow any editing on the server's settings.

Ideas? This should work in Finder.
Smbclient and Fusion area already somewhat workarounds, so I'm not looking for any third party software for dealing with this.

I spent way too much time with AppleCare on this, and all I got was 90 minutes wasted.

Ideas anyone???

MacBook Pro, Mac Pro, MacBook, Mac OS X (10.4.10)

Posted on Aug 22, 2007 11:18 PM

Reply
9 replies
Sort By: 
User profile for user: etresoft
etresoft
User level: Level 9
53,708 points

Aug 23, 2007 6:06 AM in response to dev0

dev0 wrote:
Connecting ... Linux virtual machine on Fusion on these same Macs work too.


If Linux, using SMB, can connection while the Finder, using SMB, cannot, then you need to track down what is different about the Linux SMB configuration from that of the Finder. SMB is quite complicated, so good luck. Hopefully the problem is just in the configuration files. It is possible (likely?) Linux uses a different version of SMB than the Mac. Or perhaps, it is linked with different libraries or different versions of those libraries.
Reply
User profile for user: etresoft
etresoft
User level: Level 9
53,708 points

Aug 23, 2007 7:27 AM in response to dev0

But is smbclient using exactly the same protocol and connection strategies as the Finder? To repeat myself, SMB is very complex. Clearly, most people have no trouble with the Finder's SMB. Therefore, there is something different about your particular Windows network. There is one or more specific tweaks you will have to make to get SMB in the Finder to work like the other SMB clients. I suggest running smbmount from the terminal, with debugging turned on, on both Linux and MacOS X. Compare the outputs and try to track down what is different.
Reply
User profile for user: dev0
dev0 Author
User level: Level 1
5 points

Aug 27, 2007 12:46 PM in response to etresoft

smbclient in Terminal is fine for me.

But there are other users who need it to use it as well.
I'll just need to make sure they are cli capable ... if I had to make any of those users to be limited or restrict their use of Terminal this wouldn't just work out.

What should I look for at tcpdump?
Reply
User profile for user: etresoft
etresoft
User level: Level 9
53,708 points

Aug 27, 2007 1:12 PM in response to dev0

dev0 wrote:
What should I look for at tcpdump?


I don't think you need to go that far. Just turn on debugging in the smbmount command on both machines and compare the output. Hopefully, they will be virtually identical but then diverge greatly at one point where one connects and the other doesn't.

Once you find out what is preventing a successful connection, you can work on changing the global configuration to use better values. Assuming all that works, the Finder should then work.
Reply
User profile for user: dev0
dev0 Author
User level: Level 1
5 points

Aug 29, 2007 12:34 AM in response to etresoft

All machines have the same issue. In every one of them, smbclient works from terminal. And smb and cifs connection never works from Finder.

Debugging option with smbclient wouldn't do it either as it wouldn't compare it to the working connection of terminal to the non-working of finder.

Turning on any debugging options on the server side is not an option.
Reply
User profile for user: etresoft
etresoft
User level: Level 9
53,708 points

Aug 29, 2007 6:21 AM in response to dev0

dev0 wrote:
All machines have the same issue. In every one of them, smbclient works from terminal. And smb and cifs connection never works from Finder.


That's not what you said before: Connecting from any Windows or Linux virtual machine on Fusion on these same Macs work too.

Debugging option with smbclient wouldn't do it either as it wouldn't compare it to the working connection of terminal to the non-working of finder.


Run smbmount with debugging on both the Linux and the Mac. Compare the differences.

Linux and MacOS X use the same software. Apparently, one or more of the 185,688,233,912 possible Samba configuration items is different between the two systems. If you are going to use Windows networks, you are going to have to figure it out.
Reply
User profile for user: dev0
dev0 Author
User level: Level 1
5 points

Sep 17, 2007 4:09 AM in response to dev0

I think I have found what caused it. Not solved, but at least this seems so far the most likely cause:

The share name contains hyphen.

http://docs.info.apple.com/article.html?artnum=106471 Mac OS X 10.1 or later: How to Connect to Windows File Sharing (SMB) : Date Modified: August 01, 2007

“6. You cannot connect to a share with a name that contains a hyphen. Resolve the issue by giving the share a name that does not contain a hyphen.”

smbclient in Terminal is not limited to this "feature" of Finder of Mac OS X 10.1 that was not fixed or recoded to solve it or modify it since adding smb in it in 2001.

It's not possible to test this changing the share name to one that does not contain a hyphen, nor to have one added in this server.

For users that won't have Terminal access, the solution are .. remote desktop with admin user, have admin user come to mount the share in location, or use virtualization software and with it anything that works.

Probably too optimistic to think the smb parts would have been rewritten for 10.5.
Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Finder error -36 when connecting to server - smbclient in terminal works

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up