playton
asked on
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.
ASKER
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?
For example: \\SERVER.DOMAIN.LOCAL\SHAR E or \\SERVER\SHARE ?
For example: \\SERVER.DOMAIN.LOCAL\SHAR
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
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.