UNSOLVED
Accessing Celerra CIFS share from non-Windows client
I need to be able to access CIFS shares on our Celerra from our network scanner/copier which can dump scanned images onto a share on the network. The shares in question run on a VDM on server_2. I originally thought this may be an SMB signing issue, similar to what I used to go through getting a DOS network client to access Windows 2003+ shares. So, I looked that up, and found the smbsigning parameter on Celerra and switched it to 0 (default is 1) so that I would effectively disable SMB signing. After rebooting the datamover, I was no longer able to connect via CIFS from ANY client, so I had to put that back to default. Unfortunately I was short on time for more in depth testing tonight, and not at work with the scanner to test access from there with smbsigning set to 0.
Does anyone have experience trying to get something like this working? I know on Windows servers there is an option for the SMB signing which enables signing if the client supports it as well, but from what I can tell this is an all or none option on the Celerra. Am I understanding that correctly? I believe that is the reason I lost access as the clients I was attempting access from wanted SMB signing enabled and the Celerra disabled it completely when I flipped that parameter.
I Hope this makes sense!
Thanks!
Carlos
have you seen the description of the smbsigning param?
"Used to enable or disable SMB signing "globally" on the Data Mover. param cifs smbsigning=1 enables SMB signing, and is the default setting param cifs smbsigning=0 disables SMB signing Disabling this parameter will not work unless it is also disabled on the Windows 2003 clients. "
So if you disable it on the DM, you need to disable it on all clients.
Rainer_EMC
6 Operator
•
8645 Posts
740
0
Posted May 18th, 2010 07:00
I bet its got nothing to do with smbsigning - more likely authentication
Officially we only support Windows and MacOS CIFS clients
Take a Network trace and see whats really happening
Rainer
OK, I just did some additional testing. Rainer_EMC was right, this doesnt appear to have to do anything with the smbsigning. I was just able to connect to the same share on this server from a DOS client, which would not be possible at all if SMB signing was the issue. However, when I map a drive to a share on the Celerra from DOS I get the following after issuing a DIR command:
Volume in drive Z has no label.
Directory of Z:\
.
05-13-10 12:41p 0 file(s) 0 bytes
1 dir(s) 6,024,375 bytes free
So, even though I am able to connect, I am not seeing any of the directory structure or files underneath the share at all. I have a feeling that if I get it working from DOS, that this will also fix the network copier/scanner issue as well. Unfortunately I can't really test anything from the scanner, so this is all I have to go on.
Also, in response to Ken's query, this was working fine before I migrated the share to the Celerra, so yes the account definitely has rights to this directory. I also double-checked the Share perms and NTFS security to be 100% sure.
Thanks!
Rainer_EMC
6 Operator
•
8645 Posts
740
0
Posted May 21st, 2010 09:00
I dont think a DOS system is a good test - DOS uses a really really old LanManager version of the protocol that we never officially supported
Most likely your scanner is using some form of Linux and smbclient/smbfs
If it also allows you to use ftp or NFS this would be easier
please keep us updated
Rainer
Peter_EMC
674 Posts
740
0
Posted May 18th, 2010 01:00
Which NAS version are you using?
Is the scanner using an existing windows user account or is using a Nullsession?