Shulou(Shulou.com)06/03 Report--

In recent days, we have encountered a problem of adding domains, which is basically something that everyone can do, and under normal circumstances, there will not be any problems, but we have encountered one in the past two days.

The problem is this: our domain is Windows Server 2016, and the server to add the domain is Windows Server 2003 R2. We found an error when we tried to add the domain.

Error message prompts the specific network name is no longer available

It sounds like it has something to do with DNS, but after confirmation, DNS parsing is all right.

Later, in order to verify the connectivity between the server and DC, I tried to access the netlogon folder on DC and suddenly found that the error message was the same as when the domain was added.

According to reason, accessing a shared folder should be a SMB or network problem. After some search, it is found that this problem is caused by the fact that Windows Server 2016 does not support SMB1.0 by default. The solution is actually very simple. There is a function called SMB1.0/CIFS File Sharing Support in Windows Server 2016.

After the installation is complete, note that DC needs to be restarted

After restarting, try to add the domain again, and this time you can join the domain normally.

Try to access the netlogon directory again, and sure enough, this problem has been solved.

Finally, I would like to say that Windows Server 2003 (R2) has finished its life cycle, so for enterprises still using these systems, it is recommended to upgrade as soon as possible, unless there is a real reason to have to.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.