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.