asked on
Windows 10 PCs lose connection to mapped drives on windows 2008 r2 server
Running a Windows 2008 R2 server with DNS Server running. NIC on the server set to staic IP address with the DNS pointers going to 75.75.75.75 and 75.75.76.76 (Comcast).
Since converting workstations to Windows 10, they all lose their connection to mapped drives on the server. Every morning when accessing mapped drives we are prompted "The system cannot contact a domain controller to service the authentication request. Please try again later. On that same screen we enter our credentials and are connected to the mapped drives again (for the day).
This is not happening with workstations that are still Windows 7.
Suggestions please. What have I done wrong?
Since converting workstations to Windows 10, they all lose their connection to mapped drives on the server. Every morning when accessing mapped drives we are prompted "The system cannot contact a domain controller to service the authentication request. Please try again later. On that same screen we enter our credentials and are connected to the mapped drives again (for the day).
This is not happening with workstations that are still Windows 7.
Suggestions please. What have I done wrong?
Windows Server 2008
Last Comment
LockDown32
ASKER
My drives are deployed using login scripts. Probably should switch to GPO, but not really familiar with the process.
I would go in to Credential Manager and delete any stored password for the Domain. They could be corrupt. Also try turning off power management on the network card. Have you checked to see if the computer still has an IP address at that point?
Well if you are using login scripts then my answer not the solution.
It could be Windows 10 is dropping idle connections.
Take a look at following article and see if this helps:
http://www.thewindowsclub.com/mapped-drive-gets-disconnected
It could be Windows 10 is dropping idle connections.
Take a look at following article and see if this helps:
http://www.thewindowsclub.com/mapped-drive-gets-disconnected
Check whether there is an updated driver of network interface card if your win 10 OS.
I use the script here to disable the "Turn off this device...."
https://gallery.technet.microsoft.com/scriptcenter/Disable-turn-off-this-f74e9e4a
https://gallery.technet.microsoft.com/scriptcenter/Disable-turn-off-this-f74e9e4a
OPK. That takes power management out of play. If it happens again do a ipconfig /all on the problem workstation just to see if it has retained the IP settings.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Hello Bill and lockdown
I reset my server NIC so the Preferred DNS server is itself (192.168.1.2) and the Sec DNS Server is 127.0.0.1 and I still have the same problem.
DNS is somewhere that I am really lacking. Not sure how to set Comcast DNS on the Server as forwarders.
Although I figure it has to have something to do with DNS
I reset my server NIC so the Preferred DNS server is itself (192.168.1.2) and the Sec DNS Server is 127.0.0.1 and I still have the same problem.
DNS is somewhere that I am really lacking. Not sure how to set Comcast DNS on the Server as forwarders.
Although I figure it has to have something to do with DNS
Good deal jhillbos. It wasn't the cause of the mapping issue but you just corrected a flaw that really needed to be corrected. On that same note. Open the DNS Manager. Right click on the server. Properties. Forwarders TAB. Screen shot attached. I use Comcast tool. I use the two Google Public DNSs as #3 and #4. Don't worry about DNS. Yu don't mess with it that much. You'll pick it up in time.
Back to the issue... do you leave the computer running 24/7? When they are in this state have you checked their IP settings with a ipconfig /all at a command prompt and can you ping the server?
Capture.PNG
Back to the issue... do you leave the computer running 24/7? When they are in this state have you checked their IP settings with a ipconfig /all at a command prompt and can you ping the server?
Capture.PNG
One more last minute thought along the line of the DNS. What is acting as your DHCP Server? Can up post an ipconfig /all from one of the computers?
If so, take a look in the GPO for mapping your drives, should be located under: User Configuration > Preferences > Windows Settings > Drive Maps, and see if it is set to "Replace". If so change it to "Update" and this should solve the issue.
Replace has been an issue with drive mapping on Windows 8 and Windows 10.
Give it a test and see if it works out.