Robert Pilcicki
asked on
Domain computer lose connection to mapped drives
I have a number of computers connected to a Windows Server 2012R2 Domain. Recently, a number of workstations are repeatedly losing access to the single mapped drive that was created through the server's GPO. When I click on the red X I get the following error that "The local device name is already in use"
When I expand the network locations, click on the server and select the shared drive it asks me to enter network credentials with a note: "The system cannot contact a domain controller to service the authentication request"
After I enter the administrator credentials (and check Remember my credentials) I get the following error
When I close out the error message connection to the shared folder is restored. This server has been running with the same configuration for over 2 years without incident. I have run DCDIAG but found no errors. I have tried deleting the network credentials from the workstations and reentering them, but that has no effect. All users have local admin privileges.
When I expand the network locations, click on the server and select the shared drive it asks me to enter network credentials with a note: "The system cannot contact a domain controller to service the authentication request"
After I enter the administrator credentials (and check Remember my credentials) I get the following error
When I close out the error message connection to the shared folder is restored. This server has been running with the same configuration for over 2 years without incident. I have run DCDIAG but found no errors. I have tried deleting the network credentials from the workstations and reentering them, but that has no effect. All users have local admin privileges.
On those workstations, what is reported for DNS with ipconfig /all?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"On the workstations that never had an issue the server's IP address was already listed in the DNS settings "
In general, I try to avoid static IP settings on anything except servers, routers, and switches. If I want anything else to have a consistent IP address, I set it up with a registration in the DHCP server. That can go a long way to avoiding this sort of issue.
In general, I try to avoid static IP settings on anything except servers, routers, and switches. If I want anything else to have a consistent IP address, I set it up with a registration in the DHCP server. That can go a long way to avoiding this sort of issue.
check the server's management, shared folders.
Do you use DFS or server based share?
profile corruption.
the "it has been working for x number of years." or "no changes have been made."
An update with an older system could explain.
Are all your system windows 8 and newer? or you have some older?