Slow W2K on NT4 Peer Network

[John John]

On a small static address TCP/IP peer network, 2 NT4 machines & 1 W2K,
all the machines are visible everywhere. The 2 NT4 machines access and
browse each other very fast. The W2K machine accesses and browses the
NT4's very quickly, but the NT4's take forever to access and browse the
W2K. Any ideas why the NT4's would be so slow in accessing the W2K?

John

 

[Michael Johnston [MSFT]]

I know of no reason why that would happen. The things to verify are that make sure that only one protocol is installed. If multiple
protocols are used, browsing will be problematic. Also make sure that only one NIC is installed. Lastly, 3rd party producst like
AV software or firewall software are always likely culprits with browsing problems. Try disabling this software or better yet,
remove these packages so that the kernel mode drivers these products install are taken out of the picture.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[John John]

Thank you very much for your help and advice Michael. These three
machines do indeed all have two protocols installed, TCP\IP and NetBEUI.
I was led to believe that this NetBEUI was necessary, I'll remove it
and see what happens. I'll let you know the results. Thank you for the
help and have a good weekend.

John

 

[John John]

Once again thanks for the help. Removing the unnecessary NetBEUI
protocol has greatly improved things. There is still however something
that is not quite right with the Windows 2000 station. Maybe you have a
suggestion or fix if I may indulge.

The browse access time from the NT4's to the W2K is now about 7 to 10
seconds, it was minutes before I removed NetBEUI. As I said earlier the
NT4's browse each other almost instantly.

Again, as I said earlier, the W2K browses the NT4's almost instantly.
However when at the W2K station and when browsing the network through
the Network Neighborhood "tree" the W2K is slow even browsing itself.
That is if I double click or expand the W2K machine itself it has a 5 to
8 second delay seeing itself. If I exit Explorer and open the Network
browser again still the same thing, the whirling flashlight does its
thing and the W2K lags seeing itself and still needs that 5 to 8 seconds
to show the shared resources, and of course the NT4's can't access the
shared resources on the W2K any faster than the W2K machine can find
them itself. There are no AV or Firewall programs in the picture.
There are no applications running in the background and few services or
processes running, all of my machines are set to start with the fewest
number of services/processes to start at boot time. Any other ideas?

John

 

[John John]

Eureka! Fixed!

In case the question comes up again here was the fix. I removed this
folder key from all 3 machines:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace

Select this key:- (select the whole folder)

{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

and delete it.

Now things are fixed and fast all over.

The answer was here:
http://users.bigpond.net.au/hutch/win2k/win982kptpnet.htm

John