Windows Explorer (2000)

I am using win2000 pro every time i use windows exlorer it is locking up when i explorer the netwrok drive taking 60% of CPU i have 128MB RAM and 1.0G Mhz CPU.

 

Xman - need a bit more information to help you troubleshoot this one.

Your network is how large?

Using domains or workgroups?

Using WINS or DNS or both or neither?

And the problem has always existed or started after a change in ____?

The other PCs on the (LAN, WAN, ??) do or do not have similar problems?

Your system and application event logs do or do not show any suspicious errors?

The PC "locks up" forever, for 30 seconds, for ___?

 

we are medium to large scale network about 400 to 600 we are in domain, DNS this problem just started in only one PC all other PC's are fine no error message in event log. the pcn is in LAN and it is lock up about 20 sec

 

Thanks for the information. That helps. I can't give you an instant answer but I think we can find and fix the problem.

A 20 second delay with the PC appearing to be locked up isn't unusual if the PC is having problems finding network resources. Annoying for sure and not to be tolerated if it can be fixed but not unusual behavior.

Since the problem is confined to the one PC, I think we can safely assume it isn't an issue with the network DNS or other global network pieces. Local of some sort. And very possibly hardware (nic, hub/switch port, cable).

A little troubleshooting is in order. All the below to be done from a DOS window unless otherwise noted. If one works OK, move on. Otherwise, stop and post back your results.

First, to make sure the NIC (or networking software) is working.
ping -t 127.0.0.1 and let it run for 100 or so reps. Use CTRL-C to stop it. You are interested in the time value which should be <1ms with no larger numbers and certainly no time outs.

- clean out your DNS cache and start fresh.
ipconfig /flushdns

- see about network speed in general.
ping -t servername (where servername is the name of any of your servers). Again, interested in time and the consistancy it's values. On a LAN, anything from <1ms to maybe 2ms is OK. Longer or variable or time outs are not OK.

- see if name vs. address is similar.
ipconfig /flushdns
ping -t serveraddr using the IP you got from the first ping by name. Results should be similar to the ping by name.

Second to see if the NIC and the hub/switch port are having trouble agreeing on an operating mode, go into properties for the NIC and make some speed/duplexing changes. If a particular combination isn't going to work, you will lose all network connectivity until you return to a previous setting. No harm - just a temporary loss. Try the speeds in descending order from fastest to the first one that will work for you. If you find a speed already set, this probably isn't the issue. If you find "auto" or "auto detect" it may well be.

100Mbs Full-Duplex
100Mbs Half-duplex
10Mbs Full-duplex
10Mbs Half-duplex

Third to see if you have a bad bit of cable. It can be good enough to work but bad enough to cause problems. You will be looking either at PC to wall plate or PC to hub/switch, depending on how your wiring is done. If PC to wall plate, you will also want to see the wiring from wall plate to hub/switch. If pre-made cable, probably OK at least to the wall plate. If made locally, can be problems.

Look for the section of cable right at the connectors. The usual CAT-5 cable is made of 8 strands. The distance from wire cover to connector should be very short - 1/4 inch maximum. If the small wires are exposed and the cable untwisted so they are straight, you got a problem with static that will cause just what you are seeing. If a tug on the connector pulls anything loose, you will have almost certainly found your problem.

**********************************

If all the above tests out fine, post back and we will try phase 2.

 

Thanks for the information I change the patch cable is not begaving as much as before.

 

Are you cabled to a wall plate, a patch panel, or directly to a hub/switch?

If wall plate or patch panel, check the connections there as well.

A sloppy installer will often untwist the wire a bit too far since it makes connecting lots easier. But Cat5 is UTP cable (unshielded twisted pair) and the twisting of the smaller wires around each other is its only means of reducing interference. Untwist a little too far and you will have made a small piece of the cable into Cat3 which works very poorly with 100Mbs traffic. Untwist even further and you make a useless piece of wire.

 

We use wall plate/patch pannel/HUB I check the connection using cable tester

 

I am still having problem any sugesstion cpu still locking up when use windows explorer

 

Xman

Couple of suggestions!

Come up in safe mode without network support do

Both ipconfig /flushdns & /release_all!

Then remove all internet/wan settings IP's Dns everything!

Check Lan settings on this page clear everything including automaticaly detect!

Clear all events!

Unplug nw cable!

Reboot to full mode and immediately check event logs! At this time they will only contain bootup entrys! Address these!

Then reconnect the cable!

Then resetup the network from scratch!

If you still have the problem, clear the logs again and reboot!

Immediately again recheck the logs for any bootup entrys, handle and clear once again but do not reboot! Do only 1 thing, try the browse again and immediately recheck the logs! Since you cleared the bootups only entrys about the last thing you did (the attempt to browse) is here!

Still problem, get bak to us with results!

Mike

 

Also - to completely rule out problems with the physical connection, move the PC to another wire that is working properly and see how it does.

Are you having problems with mapped drive or network neighborhood or just problems every time you open windows explorer? And after it opens, can you get to network resources in a timely fashion or does it have problems all the time?