We have a mixture of Win2K Pro and NT4 clients. From a W2K Pro workstation, if you browse mapped network drives (on NT4 servers) from NT Explorer, Explorer will intermitently and for varying lengths of time enter a Not Responding state. This does not happen to our NT4 clients. We have a normal 100MB Switched Ethernet network with loads of spare capacity. I've racked my brains and can't figure out why W2K should be doing this.
This conversation is currently closed to new comments.
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.
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.
We have WINS configured perfectly and it is specified via DHCP. We have no NetWare of IPX, we have a pure IP network. If anything SP1 has made things worse. Thanks anyway!
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Win2K Pro NT Explorer freezes