DNS stops working after mapping network drives

Question

Weird problem here. My company has replaced a computer for one of our clients. It's a new Windows 10 Pro machine but with an old SBS2011 server as the domain controller running as the DCHP and DNS server. The computer was working normally when it was initially setup. The client then called back complaining that they couldn't access anything. One of their software stores data on this server as well and points to it using the FQDN instead of the IP address. So this caused problems with the software and the client couldn't access any of the shared folders on this server. Upon doing some troubleshooting we noticed that you can access network shares on the SBS2011 server but only if you use the IP address, not the FQDN. Windows will throw an error saying that it cannot find the computer with the hostname of the server. We did some troubleshooting, and we thought we solved the problem as the computer started working normally again. However, the group policy kicked in and re-mapped the drives that we removed (since they were not working anyways). Then, the client calls back again and complains that the problem has returned. Being puzzled, one of my colleagues realizes that as soon as you disconnect the mapped network drives, the problems go away. When you map the network drives again, the problems return. This is the only computer that does this and there are other Windows 10 Pro machines that do not have this problem. I've never seen this problem before so I'm really curious as to what could be causing this.

Answer 1

Might want to check they're all on the same page as far as SMB version is concerned.
https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Hi ,

Based on my understanding, if client machine is mapping network drive then they cannot access file share via \FQDN. Is that right? Please feel free to let me know if I have any misunderstanding.

In order to get a more concreted idea of this issue, I would appreciate your help to collect the following information for further troubleshooting:

1.In order to narrow whether this issue is related with GPO mapping, please try to manually map network drive and then see if the problem still happens.

2.What's the OS version of your windows 10? 2004 or 20H2?

3.What's the NSlookup FQDN result when the problem happens?

4.Check SMB client log on windows 10 to see if there are something related for us to troubleshooting.

Best Regards,

Candy

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.