Link to home
Start Free TrialLog in
Avatar of sypv_mullins
sypv_mullinsFlag for United States of America

asked on

Domain computers cannot map network drives

We are using Windows Server 2003 SR2.  We have 10 computers on our domain.  We came in this morning and all of the computers were having issues loggin in.  They were really slow.  All drives that are mapped to the server cannot be accessed and when disconnected, cannot be remapped.  We get "there are currently no logon servers available to service the logon request" when trying to map the drives back.  I was able to map some of the drives on some of the machines by using the administrator login, but the default log in "User" that we use on the machines will not map.  I can ping the server ip and dns name fine.  Any ideas?
Avatar of sypv_mullins
sypv_mullins
Flag of United States of America image

ASKER

Also note that we use Terminal Services and our EHR software is horribly slow through it.
ASKER CERTIFIED SOLUTION
Avatar of Darius Ghassem
Darius Ghassem
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Also of note, I can log in to our Terminal Services via the local ip address, but the external ip will not connect.  It's like something is blocking access to this machine or something.  I'm thinking more and more it's DNS related.  
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
seems a big part of the issue was Eset firewall.  I had it turned off, but I guess it reenabled itself after a server reboot this weekend from Windows updates.  I will update if I have any more issues on this.  Still checking all of the computers.  So far, so good.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial