People keep losing connection to file server
Hi,
Ive got a bunch of people who access a file server on a different domain but it is in the same network subnet. When the connection fails, Im still able to ping the server so its definetly still online - the problem seems to be something to do with no domain controllers available to service the logon to that particular server. The odd thing is thou, the mapping to the server is done via the map drive option in Windows Explorer and the tick box is enable to reconnect at logon, also selected is the option to use other credentials.
The file server is Windows 2012 whilst the local domain which all the computers are in different domain which is Windows 2008 R2 as the main DC.
Why would the mapping just fail? If left alone for 5 minutes or so, it starts working on its own accord.
All desktops are running Windows 7.
Thanks
SycamoreIT
Ive got a bunch of people who access a file server on a different domain but it is in the same network subnet. When the connection fails, Im still able to ping the server so its definetly still online - the problem seems to be something to do with no domain controllers available to service the logon to that particular server. The odd thing is thou, the mapping to the server is done via the map drive option in Windows Explorer and the tick box is enable to reconnect at logon, also selected is the option to use other credentials.
The file server is Windows 2012 whilst the local domain which all the computers are in different domain which is Windows 2008 R2 as the main DC.
Why would the mapping just fail? If left alone for 5 minutes or so, it starts working on its own accord.
All desktops are running Windows 7.
Thanks
SycamoreIT
ASKER
All the connections are wired John. The trouble is, when it happens the users let me know and by the time Ive connected remotely, the issue is fixes itself. I will setup a batch file for the most persistent offenders and ask them to run the batch file next time the issue strikes and see if it they get the "no logon servers error" when its run.
On a test workstation, type NET USE and look for connections that should not be there. Then:
NET USE X: /Delete
NET USE X: \\server\folder and authenticate.
NET USE X: /Delete
NET USE X: \\server\folder and authenticate.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Try mapping with a script like NET USE X: \\server\folder and then authenticate. Does the connection drop when mapped this way? I prefer this instead of just Browsing as persistence issues can get in the way.