General discussion

Locked

Slow network response /non TCP/IP

By Wayne B ·
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.

This conversation is currently closed to new comments.

15 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Slow network response /non TCP/IP

by Astute In reply to Slow network response /no ...

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

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

Poster rated this answer

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

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.

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

I am accessing the resources by name.

Collapse -

Slow network response /non TCP/IP

by joe_whitley In reply to Slow network response /no ...

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:)

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

Poster rated this answer

Collapse -

Slow network response /non TCP/IP

by Dennis@l In reply to Slow network response /no ...

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.

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

Poster rated this answer

Collapse -

Slow network response /non TCP/IP

by NetWill In reply to Slow network response /no ...

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

Collapse -

Slow network response /non TCP/IP

by Wayne B In reply to Slow network response /no ...

Poster rated this answer

Back to Windows Forum
15 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums