XP Pro slow browsing on NT 4 Domain

[mhaase at spring-mind.com]

Hello All!

Been looking for an answer to this for awhile...and from what I can
tell from searching, many people are having similar problems - with no
joy as of yet.

We have an NT4 Domain which has been working fine with W98 clients for
years. Now, we're upgrading the clients to XP Pro, and are running
into a problem where the first browse to a server can take 15-30
seconds to bring up a display of the shares. After that (for awhile)
the display is near instantaneous. Same situation with mapped drives.

At first I suspected a name resolution problem, but if I enter
"\\192.168.0.10" in the "Run..." window, or in the "Address" area of
a folder, I get the same delay. From what I think I know, that would
eliminate the resolution problem.

Also interestingly:

Browsing to a Netware server (either by a mapped drive, or entering
it's IP address in the "Run.." window or "Address" area of a folder)
shows no delay at all.

NET USE commands to the same servers are very snappy.

And an XP client Machine WITHOUT SP1 installed performs the same
operations flawlessly.

So...what's the latest consensus on this situation? Has anybody come
up with answers?


Thanks for any help/ideas!


Mark

[Alex Walker]

I had the same problem on our network. Didn't find a soloution. But after a
few weeks or so, it seems to disapper. It's like XP is building a profile of
network info and seems to be fine when the profile is complete. Seems to be
on new builds and machines.
<mhaase at spring-mind.com> wrote in message
...
> Hello All!
>
> Been looking for an answer to this for awhile...and from what I can
> tell from searching, many people are having similar problems - with no
> joy as of yet.
>
> We have an NT4 Domain which has been working fine with W98 clients for
> years. Now, we're upgrading the clients to XP Pro, and are running
> into a problem where the first browse to a server can take 15-30
> seconds to bring up a display of the shares. After that (for awhile)
> the display is near instantaneous. Same situation with mapped drives.
>
> At first I suspected a name resolution problem, but if I enter
> "\\192.168.0.10" in the "Run..." window, or in the "Address" area of
> a folder, I get the same delay. From what I think I know, that would
> eliminate the resolution problem.
>
> Also interestingly:
>
> Browsing to a Netware server (either by a mapped drive, or entering
> it's IP address in the "Run.." window or "Address" area of a folder)
> shows no delay at all.
>
> NET USE commands to the same servers are very snappy.
>
> And an XP client Machine WITHOUT SP1 installed performs the same
> operations flawlessly.
>
> So...what's the latest consensus on this situation? Has anybody come
> up with answers?
>
>
> Thanks for any help/ideas!
>
>
> Mark
>
>

[mhaase@mindspring.com]

On Mon, 21 Apr 2003 12:46:31 +0100, "Alex Walker" >
wrote:

>I had the same problem on our network. Didn't find a soloution. But after a
>few weeks or so, it seems to disapper. It's like XP is building a profile of
>network info and seems to be fine when the profile is complete. Seems to be
>on new builds and machines.


Thanks for the input, but alas...not the case here. I've been
strugling with this for months...no joy yet. But thanks again!


><mhaase at spring-mind.com> wrote in message
...
>> Hello All!
>>
>> Been looking for an answer to this for awhile...and from what I can
>> tell from searching, many people are having similar problems - with no
>> joy as of yet.
>>
>> We have an NT4 Domain which has been working fine with W98 clients for
>> years. Now, we're upgrading the clients to XP Pro, and are running
>> into a problem where the first browse to a server can take 15-30
>> seconds to bring up a display of the shares. After that (for awhile)
>> the display is near instantaneous. Same situation with mapped drives.
>>
>> At first I suspected a name resolution problem, but if I enter
>> "\\192.168.0.10" in the "Run..." window, or in the "Address" area of
>> a folder, I get the same delay. From what I think I know, that would
>> eliminate the resolution problem.
>>
>> Also interestingly:
>>
>> Browsing to a Netware server (either by a mapped drive, or entering
>> it's IP address in the "Run.." window or "Address" area of a folder)
>> shows no delay at all.
>>
>> NET USE commands to the same servers are very snappy.
>>
>> And an XP client Machine WITHOUT SP1 installed performs the same
>> operations flawlessly.
>>
>> So...what's the latest consensus on this situation? Has anybody come
>> up with answers?
>>
>>
>> Thanks for any help/ideas!
>>
>>
>> Mark
>>
>>
>