Q: Xsan 4 and SMB sharing on Windows: issues
Good Mornin Xsan Admins.
I recently setup an Xsan 4 Full yosemite 10.10.1 with OS X Server 4.0.3
The MDC1 and 2 are properly configured as DNS and OD master and Replica
Every workstation that regularly mount the Xsan volume, access to the San with an "Edit" user with ID 502
The resharing in AFP and SMB is done byt the MDC servers by a simple local user named "share", always with ID 502. No special permissions. The simplest of the simplest with R/W to everyone
The network resharing in connected from a Mac works flawlessly in both AFP and SMB. I can mount the Volume, read and write everything without issues.
The network connection from a windows machine is causing me troubles.
I can access the Volume with the user "share", and also map it regularly as network drive.
I can see all the files
I can access and create folders, and also delete folders (if empty)
BUT
I canNOT copy files inside the Xsan volume, nor copy them from the Xsan Volume to the Windows desktop.
When i try toi copy a file, Ihe progression bar of the copy on windows appears, showing that he's copying, but always not moving, and generate files of 0kb. I do not receive any error message. It just stays there stuck. This happens in both way, copying into the Xsan volume, or copying from.
No denied access, no errors at all.
No firewall, no antivirus running, tested on Windows 7, 8 and 8.1 and different physical machines
Same result connecting with Admin account 501
The volume has been created twice to test this: tried both with Native Extended Attributes enabled or Disabled. Same problem
Do you have any idea for this issues?
One last thing: If i share a LOCAL folder, outside the Xsan volume (let's say the desktop), i do not have any issues with that folder, and windows works perfectly
I've always shared an Xsan volume on Windows, since OS Leopard 10.5, till Maverick 10.9.5 without issues, and now this.
Could it be an OD problem?
Thanks you very much for your time
OS X Yosemite (10.10.1), Xsan on OS X Server 4.0.3
Posted on Jan 23, 2015 11:02 PM
Partial Solution: SMB 1 protocol, works !!!
Today i've tried to force old versions of SMB protocol from the windows client
using the commands described here (reboot the windows workstation to take effect):
http://kb.bodhost.com/steps-to-enable-and-disable-smbv1-smbv2-and-smbv3-...
I've forced the deactivation of SMB 2 and 3, leaving only SMB 1 active:
Open the command line (as administrator) on the windows machine.
To disable the SMBv2 and SMBv3 on the SMB client, use the below commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled
Enable the SMBv1 on the SMB client with the below commands (if, for any reason, is not already running):
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb10 start= auto
In this mode, the smb share of the xsan volume works properly.
No way instead with smb 2 and 3.
Tested on both Windows 7 and 8, the good old SMB 1 is functioning.
The incredible thing is this problem only affects Xsan volumes, while DAS volumes works properly in SMB 2 and 3 on windows.
That's why i'm not so sure it may be only an SMB 3 share issue, but also something related to the OD.
Maybe forcing the share to the old SMB 2, but i have no idea how to do this on Yosemite.
I'll keep you posted on this.
Meantime, i hope i've been of some help.
Posted on Jan 28, 2015 8:14 AM