Flakey directory mapping to remote trusted domain

Richard S. · 11-01-2008, 01:17 PM

Hi,
Our organization has a production domain (Win Server 2003) in a physically remote colocation site. We have a corporate domain for most other parts of the company. The production domain has mutual trust with the parent. We run a VPN for corporate and home users to be able to access directories in the production domain.
Our problem is that mapped devices/directories may work for days at a time and then
(1) Disappear for 20 seconds and return.
(2) Show a file after the user drills down but when they go to access the file the file is reported as not avaialbe. This can be fixed by remapping the file.

What could cause this kind of eratic behavior?
(a) Are there active directory settings involving timeouts that might be sensitive to latency in connecting to the remote site?
(b) are there other network isues which could be causing this? How should we approach tracking this down?

Many thanks

Richard

**XtabbedoutX** · 11-02-2008, 08:09 PM

Try modifying your mapped drive start up script to delete the drive first and then create the mapped drive again.

Is your network at the network level or at the OS level?

Richard S. · 11-08-2008, 02:08 PM

Thanks.
We are trying useing scripts with explicit removal.
It is hard to know if the problem is fixed since it only occurs ocasionally.

Is there a known reason why it would be necessary to delte a drive first? Is there a Microsoft bug report on this?

Richard

11-01-2008, 01:17 PM	#1 (permalink)
Richard S. Registered User Join Date: Oct 2008 Posts: 3 OS: Windows Server 2004	Flakey directory mapping to remote trusted domain Hi, Our organization has a production domain (Win Server 2003) in a physically remote colocation site. We have a corporate domain for most other parts of the company. The production domain has mutual trust with the parent. We run a VPN for corporate and home users to be able to access directories in the production domain. Our problem is that mapped devices/directories may work for days at a time and then (1) Disappear for 20 seconds and return. (2) Show a file after the user drills down but when they go to access the file the file is reported as not avaialbe. This can be fixed by remapping the file. What could cause this kind of eratic behavior? (a) Are there active directory settings involving timeouts that might be sensitive to latency in connecting to the remote site? (b) are there other network isues which could be causing this? How should we approach tracking this down? Many thanks Richard

11-02-2008, 08:09 PM	#2 (permalink)
XtabbedoutX TSF Enthusiast Join Date: Sep 2007 Location: Oklahoma City Posts: 1,189 OS: Server 2K3 R2 SP 2, Server 2K SP4, XP PRO SP 3, Mac OS X 10.5, iPhone My System	Re: Flakey directory mapping to remote trusted domain Try modifying your mapped drive start up script to delete the drive first and then create the mapped drive again. Is your network at the network level or at the OS level?

11-08-2008, 02:08 PM	#3 (permalink)
Richard S. Registered User Join Date: Oct 2008 Posts: 3 OS: Windows Server 2004	Re: Flakey directory mapping to remote trusted domain Thanks. We are trying useing scripts with explicit removal. It is hard to know if the problem is fixed since it only occurs ocasionally. Is there a known reason why it would be necessary to delte a drive first? Is there a Microsoft bug report on this? Richard