3 replies
by buzzwang
If you have a larger network (200+ stations/systems) it could be that it is having to pause the display while it gathers more information from the network or a specific machine on the network.
I run w2kp on both my laptop and workstation and havehad similar issues in the past. I resolved them by making sure I had a primary and secondary WINS server specified, and that I had a computer account in the domain. Double-checking (and then updating) my WINs info helped out right away.
My other issue turned out to be software related. We run a mixed-mode network here (NT, Netware, SCO) and I found that the current Netware clients for 95, 98, NT & 2000 are still buggy and cause other problems on workstations. REmoving that helped. The other big one is the IPS protocol. IPX sends out hundreds of broadcast messages every second, which slows network response time considerablly. We run 8 netware servers, 2 SCO, and 23 NT servers here, and IPX has become the bane of my existence. But, removing IPX on my workstation accelerated all network activity by a good margin.
Just a few things to keep in mind while you investigate.
by buzzwang
Also, I forgot one other thing:
Microsoft has released SP1 for Win2K. If you haven't already applied it, I highly recommend you do so. Since I installed it here, I've had a significant drop in w2k problems.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending