Unsolved
This post is more than 5 years old
16 Posts
0
2592
VNXe3300 (access to CIFS shares) mapping shares as another user to the one who you have logged into the system as
Hi All,
I have a VNXe3300 with a CIFS server joined to domain "test" and active directory is enabled
For systems on the domain "test" i am able to access the CIFS server and shares from the user that i have logged on as
However for example if I am logged on as administrator and when i try and map \\CIFSServer\ > as a different user (Domain Admin) then it is giving me the following error message
"The account is not authorized to log in from this station"
For systems not on the domain "test"
VNxe
16 Posts
1
August 17th, 2012 09:00
If the user has permission on the share and still you are getting errors related to the credentials, authorizations then you should check the time skew between VNXe and DC . Also VNXe and the system from which you are trying to access the shares.
Please check the clock skew because windows authentication works on Kerberos and kerberos is time sensitive protocol. If there is a time difference then the authentication will fail and you will get autorization and authentication errors.
bergec
275 Posts
0
August 18th, 2012 10:00
Is there a trust relationship between the 2 domains?
Claude
Benz-Stevens
16 Posts
0
August 18th, 2012 10:00
The times are synchronized between systems and the DC as well as between the VNXe. Still getting issues. Any other ideas.
Benz-Stevens
16 Posts
0
August 18th, 2012 12:00
One of the systems is not on a domain at it is windows xp home edition in a workgroup. Apparently it was possible wih netapp.
nasemc
12 Posts
1
August 31st, 2012 13:00
Please verify that the SMB signing security signature is disabled on the Windows client\server getting the authentication failure:
SERVER
HKLM>System>CurrentControlSet>Services>lanmanserver>parameters:
enablesecuritysignature [REG_DWORD] = 0x0
requiresecuritysignature [REG_DWORD] = 0x0
CLIENT
HKLM>System>CurrentControlSet>Services>lanmanworkstation>parameters:
enablesecuritysignature [REG_DWORD] = 0x0
requiresecuritysignature [REG_DWORD] = 0x0
NOTE:
IF disable, the client or server does not support SMB signing.
IF enabled, the client or server supports SMB signing but is NOT required for all transactions
IF Required (requiresecuritysignature=1), the client or server requires SMB signing for all transactions
Please see the following MS article overviewing SMB signing:
http://support.microsoft.com/kb/887429/en-us