Slow opening file dialog boxes on home network

16 Oct 2006 12:44 AM

BruceBrad

When I try to open files when I am attached to my home network, the file open
dialog often hangs for a minute or so. I'm guessing that it is trying to find
files on my office shares which are no longer available.

Is there a way of telling Windows (XPpro, sp2) to timeout faster on the
network connection?

I found this KB article - but I'm not sure that it is relevant.
http://support.microsoft.com/kb/829700/en-us

16 Oct 2006 1:29 PM

Lanwench [MVP - Exchange]

In news:CA6C03C6-C8AD-467A-B581-A323F502868B@microsoft.com,

BruceBrad <BruceB***@discussions.microsoft.com> typed:

> When I try to open files when I am attached to my home network, the
> file open dialog often hangs for a minute or so. I'm guessing that it
> is trying to find files on my office shares which are no longer
> available.
>
> Is there a way of telling Windows (XPpro, sp2) to timeout faster on
> the network connection?
>
> I found this KB article - but I'm not sure that it is relevant.
> http://support.microsoft.com/kb/829700/en-us

This is quite normal behavior. Why are the shares not available, and why not
disconnect the mapped drives if so?

net use x: /del

If you take this computer to different locations, use a batch file to map
drives - if you connect to a domain at work, the admins should have set up a
login script, perhaps as follows:

net use * /del
net use x: \\server\share1 /persistent:no
net use y: \\server\share2 /persistent:no
net use z: \\server\share3 /persistent:no

16 Oct 2006 11:36 PM

BruceBrad

> This is quite normal behavior. Why are the shares not available, and why not
> disconnect the mapped drives if so?

Sorry I was a bit cryptic. They are available when the machine (a
notebook) is in the office. They are not available at home (I was
hoping they would automatically disconnect).

> net use x: /del
>
> If you take this computer to different locations, use a batch file to map
> drives - if you connect to a domain at work, the admins should have set up a
> login script, perhaps as follows:
>
> net use * /del
> net use x: \\server\share1 /persistent:no
> net use y: \\server\share2 /persistent:no
> net use z: \\server\share3 /persistent:no

At the moment we have the shares on the server setup to be persistent
(due to some problems connecting to an old NT4 box in a different
domain). We will be changing that tomorrow. I will see if that solves
the problem (and will also try simply deleting the shares).

Thanks.

17 Oct 2006 12:27 AM

Lanwench [MVP - Exchange]

In news:1161041798.610400.3070@h48g2000cwc.googlegroups.com,

BruceB***@iname.com <BruceB***@iname.com> typed:
Show quoteHide quote

>> This is quite normal behavior. Why are the shares not available, and
>> why not disconnect the mapped drives if so?
>
> Sorry I was a bit cryptic. They are available when the machine (a
> notebook) is in the office. They are not available at home (I was
> hoping they would automatically disconnect).
>
>> net use x: /del
>>
>> If you take this computer to different locations, use a batch file
>> to map drives - if you connect to a domain at work, the admins
>> should have set up a login script, perhaps as follows:
>>
>> net use * /del
>> net use x: \\server\share1 /persistent:no
>> net use y: \\server\share2 /persistent:no
>> net use z: \\server\share3 /persistent:no
>
> At the moment we have the shares on the server setup to be persistent
> (due to some problems connecting to an old NT4 box in a different
> domain). We will be changing that tomorrow. I will see if that solves
> the problem (and will also try simply deleting the shares).
>
> Thanks.

No prob - post back if you need anything more with this.