Mapped Drive Disconnecting frequently

I am currently using a batch script to map network shared drives for network users. Here is a sample of the command(s) in use.
NET USE W: \\MainServer\GroupShare /Persistent:YES

However, the mapped drive keeps disconnecting.

The issue appears to be on branch office client computers.

WAN Settings:
IP: XX.XX.XX.XX/24

Lan Settings:
IP: 192.168.3.x/24
DNS1: 192.168.1.5
DNS2: N/A

Router provides DHCP and DNS which connects to corporate office via VPN (192.168.1x/24, DNS 192.168.1.5).

When I enter the DNS setttings manully in to IPV4 DNS settings there are no issues. But when I let the the router provide automatically thats when I run into problems.

The problems lies on other branch offices too, and not just one office in particular.

What steps can I take to troubleshoot the disconnection of the map drive, and DNS settings.

What is best practice to configure branch offices via vpn connection.
oadmhernandezAsked:
Who is Participating?
 
Justin OwensConnect With a Mentor ITIL Problem ManagerCommented:
Looks like it was also a Domain Controller.  If this is the case, it will, indeed, cause all kinds of grief, especially if it was turned off longer than your tombstone.  I would recommend demoting it to a member server, and if that fails (which it well may), physically disconnecting and then force demoting the server and force removal of the server from AD metadata.  If you need help with any of these steps, let me know....

DrUltima
0
 
Justin OwensITIL Problem ManagerCommented:
I am assuming your DNS1 is an internal, AD aware DNS Server.

I am not sure what you mean by this statement:  

When I enter the DNS settings manually in to IPV4 DNS settings there are no issues. But when I let the the router provide automatically that's when I run into problems.

Would you mind clarifying for me?  Knowing a little more would be helpful:

1) Does your enterprise utilize DHCP?  If so, are the DNS settings universal or site specific?
2) Do you branch offices have a DC or RODC for authentication, or does your main office handle all AD authentication?  If yes to remote DCs, are Sites correctly configured in AD?

DrUltima
0
 
oadmhernandezAuthor Commented:
I am assuming your DNS1 is an internal, AD aware DNS Server.

I am not sure what you mean by this statement:  


When I enter the DNS settings manually in to IPV4 DNS settings there are no issues. But when I let the the router provide automatically that's when I run into problems.

Corporate Office holds AD/DC/DNS/DHCP. The DHCP has a scope of 192.168.1.x/24 (for corporate office only). DNS1: 192.168.1.5 (DC/AD).

As for the Branch Office the SonicWall Pro1260 Router Provides DHCP and DNS Settings(192.168.1.5)  and DHCP scope 192.168.3.x/24

When I leave the client pc to obtain DNS server address automatically I get constant map drive disconnects. However, if I manually enter the DNS servers (corporate) it works fine.


1) Does your enterprise utilize DHCP? YES  If so, are the DNS settings universal or site specific? all branch offices look to DNS1 = 192.168.1.5 (located at corporate office)

2) Do you branch offices have a DC or RODC for authentication, or does your main office handle all AD authentication?  Main Office handles all AD authentication, we are connected via vpn.
If yes to remote DCs, are Sites correctly configured in AD?

0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
Justin OwensITIL Problem ManagerCommented:
So, at your remote site in which your SonicWall provides DHCP addressing, please do (when using DHCP) an

IPCONFIG /all

Let me know what any DNS server addresses are.  Often times a SonicWall is not correctly issuing DNS due to error or misconfiguration.
0
 
oadmhernandezAuthor Commented:
I think I found the culprit. I believe a server that was once connected to our network functioned as a second DNS. It was turned off for a while because it was not needed. About a month ago we moved offices and the server was turned ON and I believe this is what is causing the issue. I will keep you posted. I ran cmd gpupdate /force and received the following message.

C:\Windows\system32>gpupdate /force
Updating Policy...

User policy could not be updated successfully. The following errors were encount
ered:

The processing of Group Policy failed. Windows could not resolve the user name.
This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain co
ntroller has not replicated to the current domain controller).
Computer policy could not be updated successfully. The following errors were enc
ountered:

The processing of Group Policy failed. Windows could not resolve the computer na
me. This could be caused by one of more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain co
ntroller has not replicated to the current domain controller).

0
 
oadmhernandezAuthor Commented:
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.