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.
playtonAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ewkellyCommented:
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.
0
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.
0
KevinTHayashiCommented:
When you say that you type in the path, are you using the FQDN or just the Server name?

For example: \\SERVER.DOMAIN.LOCAL\SHARE or \\SERVER\SHARE ?
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

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.
0
bigg_oilCommented:
this indeed is a dns issue make sure the dns for each computer is pointed at that networks domain controller
0
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.

Kevin
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.