win xp networking is slow !

[bushwakko]

i have a problem. when i try to connect to people on a lan, i get as far as the first directory the "\\computername". but when i go a step further, it says "not responding". If i wait an insane amount of time, it eventually gets there, and sometimes i can copy stuff. if i end the task, explorer shuts down and i have no start-bar, but i can start it again from the task manager. then i can't access the first directory of a computer either... help anyone?

 

[c0rv1d43]

Could you be persuaded to part with a little more information about that LAN? You know, stuff like:

What type of LAN is it, peer-to-peer or client-server/domain?

What other OSes are running / communicating on the LAN? (Win9X, Linux, BSD, etc.)

What is the physical makeup of the LAN? (Ethernet, Token Ring, 802.11x, etc.)

What protocols, clients, bindings are you using on each of the adapters on the network? (Is File and Printer Sharing Enabled on the WinXP machine, on other machines? Is NetBIOS bound to TCP/IP. Is TCP/IP being used? Any other protocols being used?)

What, if any, troubleshooting steps have you taken? (Swapped NICs / cables / hubs /etc.? Pinged 127.0.0.1, remote machine by IP, remote machine by name?)

Throw the people here a little meat, and they'll chew on it for ya! 😀

- Collin

 

[bushwakko]

ok, here goes.

It's Ethernet, we're all connected to a switch. I've tried multiple OS's: XP, 2k, ME. Same problem. I get the first directory listing very quickly, but when i then click something it hangs. I haven't timed the "hang" yet, but it's very long. dunno if it's the same time every time either.

Everything else works, ping, ftp, games. File printer sharing is of course enabled, since i get the first listing. I don't think NetBIOS is bound to tcp/ip, because i have Nwlink NetBIOS and IPX driver protocol driver. Tried the switching cables, though not the NICs.

I would like to try and reinstall all my network drivers from scratch, but i don't know how. it was so easy in windows 98/me. Just delete EVERYTHING, reboot, and it would ask for the cd and reinstall all drivers. 🙂

well, anyway... does this help a little? 🙂

 

[bushwakko]

ok, a little update. when the timeout is over and the dir is loaded, i can easily browse everything inside that folder i think. but if i go back to the top folder and try to access a new one it hangs, AGAIN! 🙁

 

[Gooberlx2]

Id recommend hacing all the computers be on the same subnet. That seemed to increase speed quite a bit for me on my lan. (8 computers between me and roomies) If you can't specify the IPs, subnet mask, gateway, etc for all your computers try a router, they'll all be on the same subnet by default then.

Or maybe use samba? I dunno if samba works between windows computers or not.

 

[c0rv1d43]

It's Ethernet, we're all connected to a switch. I've tried multiple OS's: XP, 2k, ME. Same problem. I get the first directory listing very quickly, but when i then click something it hangs. I haven't timed the "hang" yet, but it's very long. dunno if it's the same time every time either.

Everything else works, ping, ftp, games. File printer sharing is of course enabled, since i get the first listing. I don't think NetBIOS is bound to tcp/ip, because i have Nwlink NetBIOS and IPX driver protocol driver. Tried the switching cables, though not the NICs.

I would like to try and reinstall all my network drivers from scratch, but i don't know how. it was so easy in windows 98/me. Just delete EVERYTHING, reboot, and it would ask for the cd and reinstall all drivers.

WinXP and Win2K have been noted to have slow connections with the DOS-based Windows versions. I still don't have a clear idea of what you have observed connection-wise from one OS to another -- for instance, where have you tried the multiple OSes? It's the mix of machines on the network at one time that matters, and what connectivity is like in each direction between the different OSes. It sounds as though you need to scrap everything and start over, uninstalling networking and removing the NIC drivers and then reinstalling the NICs and setting up networking from scratch. Is there some reason why you are using Novell protocols? Have you made certain that the version you are using is compatible with Win2K / WinXP? Frankly, unless it was impossible to do without it, I'd stick with TCP/IP. It's what Win2K and WinXP were designed (from the ground up) to work with. And they work quite well with it. When you start mixing in other protocols, especially third party stuff, you have to be careful about things like version compatibility, and multiple protocols also require you to pay attention to protocol binding order (and the default protocol) on each of the NICs.

It sounds as though you don't have a solid idea of how you have the network set up since you say that you "don't think NetBIOS is bound" to TCP/IP. It's fairly easy to find out by examining the network connection's properties. I'd strongly suggest that you go to one of the online sites that actually has step-by-step tutorials so that you can work your way past all of the obvious steps in setting up the network properly. I don't feel we have enough information yet to enable us to do more than take some pot-shots at your issues, and you should be able to give us a precise description of the way you have your network and adapters set up by the time you've gone through the whole procedure carefully. Right now it sounds as though your network configuration may be more complex than it needs to be, and it's certainly doing more than the average home LAN if you're running an FTP server and doing multi-user gaming on it. You'll be better able to support and protect the LAN (security-wise as well as maintenance-wise) if you develop a solid sense of how it's put together and configured.

Some basic networking FAQs here at AnandTech could be helpful to you, but you may want to go to an even more basic source of info like those found at Practically Networked or like the really excellent tutorials and step-through procedures at Site Helmig.

Insofar as NIC drivers are concerned, Windows XP Plug 'n Play is MUCH better than that which existed in the DOS-based Windows versions. But that does bring up the point that it's also important to be sure all of the hardware on the Win2K and WinXP machines is compatible with those operating systems. The vast majority of common NICs are going to be found in WinXP's native driver database.

If I'm misunderstanding your situation and you don't need the basic help I suggested, then I'm sorry. But I'm getting the feeling that the help you need is a full network setup instead of an attempt to troubleshoot a network whose characteristics are not fully known. That's a common issue because a lot of home networks (and even corporate ones) just grow by accumulation, with a piece of equipment, a protocol, whatever just being added a piece-at-a-time. Sometimes a basic principle can be overlooked in the midst of all of the tinkering.

- Collin