General discussion

Locked

Browsing network neighborhood slow.

By dthiele ·
I have an NT4.0 SP6 PDC BDC W2000 server and attached W98, W95, WNT and W2000 clients.
Network Neighborhood can take 30 seconds to 1 minute to see each click starting from the net neighborhood start all the way down to the server or client only when using the W2000 clients to browse the network. All other browsing using other clients is very quick. TCP/IP, Wins, Dhcp, netbeui etc is in use.
Any one know why W2000 clients tend to be slow navigating net neighborhood. An added network place always responds fast. Just navigating the net neighborhood is slow.

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Browsing network neighborhood slow.

by mmcdade In reply to Browsing network neighbor ...

Just a suggestion off of the top of my head (and it may not apply to W2K, which isn't my strongest OS). I know that in WIN98SE, you can choose to disable Browse Master via the properties of Net Hood. Select the properties of Client for Microsoft Networking and then for the Valuse beside Browse Master select "Disabled".

Don't know if that'll help, but I just thought I'd throw it out there.

Best of luck,

- Mark

Collapse -

Browsing network neighborhood slow.

by dthiele In reply to Browsing network neighbor ...

Poster rated this answer

Collapse -

Browsing network neighborhood slow.

by dwooming In reply to Browsing network neighbor ...

Try removing NETBUI from that particular 2000 machine. If you have WINS, there should be no need for NETBUI.
Also make sure that in the advanced settings under properties of the TCP/IP settings, the WINS tab has the "Use netbios setting from the DHCP server" option checked.
If this still does not work, you can also try adding entries to the "lmhosts" file.

Collapse -

Browsing network neighborhood slow.

by dthiele In reply to Browsing network neighbor ...

After a lot of research I finally did the following:
PDC Event Log shows Clients wanting to be Browse Master
and
Network Browsing is slow on W2000 clients.
Using WNT4.0 SP6 Domain and W2K clients.
PDC log shows clients are wanting to be browse master.
W2K Client Browsing in Net Neighborhood takes 30 to 60 seconds per click.
1. On PDC do this?
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
IsDomainMaster="TRUE"
MaintainServerList="YES" Note: True is not correct here and event log will tell you if used it is illegal.
2. On W2000 Clients
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
IsDomainMaster="FALSE"
MaintainServerList="FALSE"
Above stops the Browser Master selection problem.
3. W2K NetBeui has to be on or the netbios names will not work and Wins will not work for the
machine unless NetBeui is active. Not too sure here but did by observation.
4. Browsing was still slow so I did the following:
On W2K client in TCP/IP settings, Wins, set Disable Net Bios over TCP/IP.
Now net browsing was very fast on the W2k client.
5. W2k system log show computer browser terminated with service specific error 2550
Go to the services and disable computer browser service.
Now reboot and error will not be there.
6.Now browsing on WNT 4.0 Server to W2k Clients was ok but browsing to W98 took up to 30 seconds.
Stopped the following registry key on the NT4.0 server from working by renaming.
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer \NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}

Collapse -

Browsing network neighborhood slow.

by dthiele In reply to Browsing network neighbor ...

This question was closed by the author

Back to Desktop Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums