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?
LVL 1
sypv_mullinsAsked:
Who is Participating?
 
Darius GhassemConnect With a Mentor Commented:
Make sure that the clients are only pointing to the DC for DNS in their TCP\IP settings. Also, make sure the DC is only pointing to itself for DNS as well in it's TCP\IP settings run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix on DC.
0
 
sypv_mullinsAuthor Commented:
Also note that we use Terminal Services and our EHR software is horribly slow through it.
0
 
nikko06Connect With a Mentor Commented:
try deleting all mapped drives using the net use command

net use \delete *


0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
nikko06Connect With a Mentor Commented:
then re-map
0
 
gshankConnect With a Mentor Commented:
All the above comments are good - I just want to add my 2 cents that I abhore mapped drives - think about using UNC (\\<server\share\path) instead and whenever possible
0
 
briandunkleConnect With a Mentor Commented:
Might check how many connections are being made to the server...if the name is actually "user" you may have unwelcome connections from around the world. :)
Check sharing control panel on the server.
Aaaand the usual "did you restart the servers?"
0
 
SysExpertConnect With a Mentor Commented:
Also, Check the event logs on the server and affected clients.
Reboot the server and see if this resolves the issue.

I hope this helps !
0
 
sypv_mullinsAuthor Commented:
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.  
0
 
Darius GhassemConnect With a Mentor Commented:
Please look over my post.

0
 
sypv_mullinsAuthor Commented:
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.
0
 
briandunkleConnect With a Mentor Commented:
Yeah, that'll do it, for sure. :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.