Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

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?
0
sypv_mullins
Asked:
sypv_mullins
  • 3
  • 2
  • 2
  • +3
8 Solutions
 
sypv_mullinsAuthor Commented:
Also note that we use Terminal Services and our EHR software is horribly slow through it.
0
 
Darius GhassemCommented:
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
 
nikko06Commented:
try deleting all mapped drives using the net use command

net use \delete *


0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
nikko06Commented:
then re-map
0
 
gshankCommented:
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
 
briandunkleCommented:
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
 
SysExpertCommented:
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 GhassemCommented:
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
 
briandunkleCommented:
Yeah, that'll do it, for sure. :)
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now