10.4: Another fix for Windows 2003 share mounting
Aug 20, '07 07:30:01AM
Contributed by: GLG
Many users have problems mounting shares from Windows 2003 Servers from OS X Tiger (10.4 - 10.4.10) clients. The following solution has been tested in our enterprise where we have W2K3 servers, physical as well as virtual, and some within a SAN.
Problem: From the network view in OS X, we could browse to the servers, but when we tried to connect, we would get the Delete/Fix Alias error. When connecting from the Finder with Command-K (either with smb://servername, smb://ip.address, smb://servername.fqdn, cifs://servername, etc.), we would get the dreaded Error -36 and the Console would show:
mount_smbfs: session setup failed (extended security lookup2): syserr = Socket is not connected
mount_smbfs: could not login to server SERVERNAME: syserr = Socket is not connected
Using smbclient from the terminal would work fine.
Solution: After making sure that there are no Local or Domain policies interfering (NETBIOS, WINS, Kerberos, Firewalls, IRPStackSize problems, etc.), try the following.
On the server in question, in Control Panel » Network Connections, select the NIC, click on Properties, then on "File and Printer Sharing for Microsoft Networks," click on Properties and check the option for either Maximize Throughput for File Sharing or Maximize Throughput for Network Applications (depending on the use of the server). This changes the value of the REG-DWORD "Size" at HKEY_LOCAL_MACHINESYSTEM » CurrentControlSetServices » lanmanserverparameters from 1 or 2 to 3. From the command line or Services.msc, restart the "Server" service or reboot the machine. Thanks to Joel Ayala for the expert Windows perspective.
[robg adds: We have a few more Windows 2003 hints in the system.]
Comments (4)
Mac OS X Hints
http://hints.macworld.com/article.php?story=20070815135359143