Smb error -36 always in Finder, Terminal works

**Giaguara** · #1 August 22nd, 2007, 05:12 PM

This is turning me nuts.

Every single computer at work (7) are affected by this. Any help appreciated at this point ...

All hardware are intel based Macs (Mac Pro, MacBook Pros, MacBook, Mac mini)
10.4.10, also present in 10.4.8 and prior

When connecting to windows server / share using smb in Finder's Go > Connect to Server dialogue, this is always the result

error code -36

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.

Sometimes this goes as far as select the share to mount screen, and I can insert the username, workgroup and username - connection fails then after a few seconds of trying.

Code:

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

Terminal works.

Code:

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

gets connection as it should.

http://www.macwindows.com/tiger.html and http://docs.info.apple.com/article.h...580suggestions 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 don't have physical or admin access to change the settings on the smb server - only share connect details.

All Windows and Linux clients and guest operating systems work without problem.
Suggestions at http://www.macosxhints.com/article.p...70815135359143 would suggest editing Windows server .. not an option.

Smb when connected from Terminal gives

Code:

Domain=[dnsnameofwhereconnected] OS=[EMC-SNAS:T5.4.21.400] Server=[NT1]

Suggestions?

**Giaguara** · #2 August 22nd, 2007, 05:19 PM

Since this should work from Finder, there are ONLY workaround so far.

- Terminal. I don't mind cli but I'm not the only user for these.
- Virtual machines. Did I say a bit complicated solution?
- Using a third computer to achieve this. So mount both the smb and the Mac that the files need to be copied to via smb, and copy and paste or drag and drop. Linux, or Windows Explorer, or even Winscp .. this should work entirely with Mac itself, not needing operating systems ad not educating every single user about cli usage and smbclient.

What is this EMC-SNAS?

Domain=[servername] OS=[EMC-SNAS:T5.4.21.400] Server=[NT1]

eric2006 · #3 August 22nd, 2007, 05:44 PM

Have you tried everything here?

Some report firewalls on the host side as a cause for the error, but given that you can connect in other ways, that seems unlikely..

Apple discussion forums only echo the KB article, from what I've seen..

**Giaguara** · #4 August 22nd, 2007, 05:55 PM

I'll test those tomorrow and see what happens.

**Giaguara** · #5 August 23rd, 2007, 03:03 AM

Block UDP traffic was off so that wasn't it either.
Using cifs gives the same exact errors.

mount_smbfs: error from NetrShareEnum call: exception = 382312500
still.

Domain=[servername] OS=[EMC-SNAS:T5.4.21.400] Server=[NT1] ..
I start to wonder if this is SNAS specific? How do I get the IP address for the SNAS from the DNS name??

macbri · #6 August 23rd, 2007, 03:06 AM

Quote:

Originally Posted by Giaguara

How do I get the IP address for the SNAS from the DNS name??

ping whatever-the-dnsname-is.com?

**Giaguara** · #7 August 23rd, 2007, 05:36 AM

D'oh

smb and cifs with the IP using Finder give the same error than using the dns.
Even ftp gives the same error -36 'some data could not be read or written' if using a path that should be able to be accessed.
Ftp in Finder with only ftp://dnsname gives authentication screen and does then mount the share.
Ftp in terminal gives

Code:

230- No driectory! Logging in with home=/.
230 UNIX User [username] logged in.
Remote system type is UNIX.
Using binary mode to transfer files.

I tried earlier MS UAM as well. Installation errors...
Also smbMount (which still pulls Finder's smb authentication).

So, third workaround = ftp.

More smb ideas?

Kees Buijs · #8 August 23rd, 2007, 06:56 AM

Quote:

Originally Posted by Giaguara

I'll test those tomorrow and see what happens.

Are you sure the drive is not bad ? Check if possible with e.g. an XP machine and check if you can access the smb drives ...

Good luck, Kees