No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


S5500T device can join the AD, but it can not look up user information

Publication Date:  2013-04-01 Views:  68 Downloads:  0
Issue Description
customer want to copy data from old NAS device to our S5500T device via robocopy tool, when they do the copy action, it displayed that the priority is insufficient.
Alarm Information
Handling Process
the netbios name is set as the cluster name, and the  value of realm same with AD domain name. We found if the value of realm is different from netbios name, it is successful to look up the user information. so we changed the cluster name manually.
Root Cause
1. via the commands bellow, we can see the device join the AD server successfully.
net ads info
net ads testjoin
wbinfo –t 

2. when we run the command bellow to check the AD information, it is failed
wbinfo –u
3. change the smb.con file to test the resolution as bellow, then we found it can look up the user information from AD server.
it is better to set the cluster name different from AD domain name.