• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 171
  • Last Modified:

Slow TCP/IP

We have TCP/IP set up on all our NT PC's: PDC,BDC and 5 workstations.

I can ping any other computer by its name from the PDC and I get a reply quickly.  However when I ping by name from any computer other than the PDC the reply is very slow.  It is fast only if I ping by the IP address.  I copied the updated version of LMHOSTS.SAM and ran NBTSTAT on each computer from where I tried pinging.  What could be the problem?
0
lenap
Asked:
lenap
1 Solution
 
joeljpCommented:
The reason why it's fast when you ping from your PDC is because it is the master browser and has resolved all other computer names to its IP address. So when you ping by name, it knows immediately which IP address to use.

On your other systems, LMHOSTS.SAM is a sample file hence it's not being used to resolve the IP address. Make a copy of it and called it LMHOSTS. Use NOTEPAD to edit it (if you use WORD it will add a .DOC attachment or .TXT if using WRITE, this may not be obvious and it will not work with an extension of any kind). Once editing is done, you will need to refresh the cache table. From a dos prompt enter  NBTSTAT -R , you then should be able to ping without any problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now