Windows XP drive mapping problems when Domain connection lost

[thilzer]

I have 3 Windows XP SP1 workstations located at a remote office that are the members of a Domain. The Windows 2K3 Server resides at the "Corporate" office and the communication between the computers at the remote office and the domain controller at the Corporate office occur via a VPN connection going over a couple of Netgear boxes. The Windows XP workstations run a local application that requires a shared folder on 1 of the Windows XP workstations and a drive mapping from the other 2 Windows XP workstations to the shared folder on the 1st, call it drive R:. Drive R: maps fine, as long as the connection to the domain is working. However, if the VPN goes down for any reason, then the local drive mapping is lost and the machines at the remote office are no longer able to get to the shared application. I would like to make sure that the remote office workstations can continue to function even if their connection to the domain controller is lost. Has anyone else experienced this type of thing? Is it by design? I'm considering putting a local HOSTS file on each of the machines so that they can get their name resolution information without having to query the domain controller's DNS Server. I'm also considering using a different set of credentials for the drive mapping. Sorry for the long winded explanation. Anyone have any suggestions on this or experienced anything like this?

Thanks in advance

TH

 

[mrdenny]

If the network connection is that unstable it might be worth it to deploy an inexpensive domain controller to the remote office for the users to use for authentication.

The fact that the users can't connect to the network share is by design. With no way to confirm the authentication, the server rejects the connection attempt until the domain controller is available again.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[thilzer]

Thanks for the feedback Denny, that is really helpful. What do you think about using local logon credentials for that drive mapping instead of domain credentials? The goal being that the machine would not be looking to the domain controller. The VPN connection is mostly stable, but just in case it does go down it would be nice for the remote office not to be completely down.

Thanks again.

TH

 

[roytheboy]

Either putin a cheaper DC .. or setup some scripts on the winxp pc's thatdrop the drive coneciton and remap it.

In the event of a VPN failure then the script can be ran o the pc.. drive r is dropped and remapped with credentails within the script.

i agree with mr denny... that a DC would be far more suitable ...however.. as a quick fix while sourcing funds.. maybe this could work.

Romolo

 

[mrdenny]

If you didn't want to put in a new dc then local cridentials would work. It just defetes the purpose of having a domain, since you won't be using it.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[thilzer]

Thanks Denny and Romolo. I think putting in a DC is the best long term solution and one that we will do soon, but in the meantime, the local credentials will get us through for now. This is in the wake of some flaky network performance at the remote office, so I'm working that angle as well, trying to get the network as stable as possible so that disconnections to the domain do not occur. The reality though, is that VPN connections can get a little bit flaky at times, so I want to have some type of insurance policy if the connection drops for a few minutes or hours. I agree that having local credentials defeats the purpose of the domain, but barring putting in another DC, I can't see any other way to ensure that the application can run.

Thanks again for you feedback, it really has been invaluable.

TH