Windows Forum

Ask something
Discussion Locked

Slow network response /non TCP/IP

0 helpful
15 replies

by wayne b 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a few NT 4.0 workstations that experience slow network response when receiving non TCP/IP packets. These PCs are the same manufacture and model as other PCs that do not exibit this same problem. Here is an example:
From one PC, I can access a directory on a server across a T1 connection and modify the security permissions without any hesitations or delays. From one of the troublesome PCs, this same action will all but lock up the PC.
Both systems can access tcp/ip (FTP, HTTP) servies with no delays and adequate response times. I know that these two separate protocalls utilize different search directives (netbios, host, lmhost, cache, DNS) but all services and are configured the same on the two PCs.
Any comments of answers wouldbe appreciated.

15 replies

by astute

Check the binding order for the protocols.

Also are u trying to access the other resource by IP or by name ? some time it can be a name resolution problem.

Hope this helps

by wayne b

I had the WINS Client (TIC/IP) as the first binding for NetBIOS, Server, and Workstation. I moved NWLink NetBios up as the first binding in all three and if anything, the PC locked up even faster.

by joe_whitley

Try pinging a remote machine by name, then by IP address. Sounds very much like timeouts are the problem. If the IP ping is fine, but the name takes longer, name resolution is where you need to look.

Hope this narrows it down a bit:)

by Member 35772270

If everything was working fine and the slow machines just got slow over a period of time. Format the hard drive and reload the OS. I had the same problem awhile back.

by netwill

sounds like TCP/IP protocol problem:

run Sniffer at it and see if you are getting a lot of time outs or fragmentation.

search for 'Q158474' on microsoft technet for editing registry

by maxwell edison

Greetings,

I believe that if you have different protocols installed, one of your property options will allow you to set a "default" protocol. Make TCP/IP your default.

Maxwell

by pan 13 x

remove all protocol information and install just tcp/ip and configure it to use the correct dns and wins serevers. Test you connections. There maybe a problem with the nic inside the computer, you could be overflowing the buffer and causeing the computer to lockup. if the direct tcp/ip fails to work I would move the computer to a know working location (net work port) this is verify that it isn't the network drop or the hud/switch port being bad. if fails still replace the nic with a known good nic.
I think these steps will revel your problem,.

This discussion is closed to new replies.