• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 272
  • Last Modified:

Mapped Network Drives on Network

I have just a few users and regularly I have issues with mapped drives not connecting on boot up. If I reboot 2 or 3 times I get a connection. When I do not get a connection and manually type the path I receive a message not allowing me access, but if I use the IP address and map it goes through. It seems to me to be a DNS issue but not sure where to look and why this is randomly occuring. These users are running a mapped drive script.
1 Solution
Do you have your own DNS server? If yes, is it first in the listing on each machine?
If yes, is the dns server too busy? you did mention that you have only a few users, but what else is the server running?

One way around it is to create a host file for each machine and put your servers in it.
playtonAuthor Commented:
You hit on something I looked at..   We have 2 networks in house. Both independent of each other. I do though have both DNS on both servers for auth. routing. The one in question is the second on the dhcp entry. So I reversed the two and will see if it being the primary fixes the issue.
When you say that you type in the path, are you using the FQDN or just the Server name?

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Neil RussellTechnical Development LeadCommented:
Active directory client workstations should ONLY have the DNS server of your AD set, to avoid LOTS of problems. Also a secondary DNS server should ALSO be on the same domain if you have one listed really.
this indeed is a dns issue make sure the dns for each computer is pointed at that networks domain controller
Kevin HaysIT AnalystCommented:
I absolutely hate it when I go into a clients business and see external dns ip's listed.  I hate it even more when I have to go in behind other admins at my company and find they did the same thing.

To reiterate the fact on DNS.
Run the following on the dns server.
dcdiag /v > c:\dnstest.txt
Just a simple test, you can get more advanced and make sure it passes.

Make sure your reverse lookup zone is configured properly and you have a pointer back to your DNS server.

If you have it setup correctly there shouldn't be any problems with either the IP or fqdn or netbios\share or however you are mapping them.

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.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

Tackle projects and never again get stuck behind a technical roadblock.
Join Now