Can't resolve pc's name in small local network

  • Thread starter Thread starter exy.lin
  • Start date Start date
E

exy.lin

Hi,
In a small office of several computers running winxp, when I do a ping
at pc1 to pc8, the name can't be resolved.
However, it can be pinged using the IP address of pc8.

Is it the issue related to master browser? How can I resolve it?
Thanks.
 
Hi,
In a small office of several computers running winxp, when I do a ping
at pc1 to pc8, the name can't be resolved.
However, it can be pinged using the IP address of pc8.

Is it the issue related to master browser? How can I resolve it?
Thanks.
Click to expand...

Make sure that NetBIOS over TCP/IP is enabled on pc8:

1. Open the Network Connections folder.
2. Right click the local area network connection.
3. Click Properties.
4. Click Internet Protocol (TCP/IP).
5. Click Properties.
6. Click Advanced.
7. Click WINS.
8. Click the Enable NetBIOS Over TCP/IP button.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
(e-mail address removed) wrote in
Hi,
In a small office of several computers running winxp, when I do a
ping at pc1 to pc8, the name can't be resolved.
However, it can be pinged using the IP address of pc8.

Is it the issue related to master browser? How can I resolve it?
Thanks.
Click to expand...

The problem is that "ping" is not a NetBios function, it is a TCP/IP
command. TCP/IP commands use a combination of the "hosts" file and DNS
servers to resolve names. Unless your office has a Dynamic DNS server
that auto-registers machines as they connect, you will not be able to
resolve a NetBios names/address with TCP/IP commands like "ping".

If you need to "ping" using NetBios names, you might try the "nbtstat"
command:
nbtstat -a computername
which uses normal NetBios methods of resolving local computer names.

Another solution might be to put entries in the "hosts" and/or
"lmhosts" file for all computers in your small office. These files are
normally found in the C:\windows\system32\drivers\etc\ directory. This
would assume that the IP addresses of your office computers don't
change.

HTH,
John
 
(e-mail address removed) wrote in


The problem is that "ping" is not a NetBios function, it is a TCP/IP
command. TCP/IP commands use a combination of the "hosts" file and DNS
servers to resolve names. Unless your office has a Dynamic DNS server
that auto-registers machines as they connect, you will not be able to
resolve a NetBios names/address with TCP/IP commands like "ping".

If you need to "ping" using NetBios names, you might try the "nbtstat"
command:
nbtstat -a computername
which uses normal NetBios methods of resolving local computer names.

Another solution might be to put entries in the "hosts" and/or
"lmhosts" file for all computers in your small office. These files are
normally found in the C:\windows\system32\drivers\etc\ directory. This
would assume that the IP addresses of your office computers don't
change.

HTH,
John
Click to expand...

Last time, the shared folder from pc8 can be accessed from pc1 using \
\pc8\data.
However, for what unknown reason, I can now only access the shared
folder using \\192.168.1.8\data (the ip address of pc8) and it is very
slow.

Can some enlighten me what went wrong? Could it be due the firewall
component of the anti-virus software running on the pc? Thanks.
 
Last time, the shared folder from pc8 can be accessed from pc1 using \
\pc8\data.
However, for what unknown reason, I can now only access the shared
folder using \\192.168.1.8\data (the ip address of pc8) and it is very
slow.

Can some enlighten me what went wrong? Could it be due the firewall
component of the anti-virus software running on the pc? Thanks.
Click to expand...

There should be no need for a hosts file or an Lmhosts computer on any
computer. Make sure that such a file isn't specifying the wrong IP
address for pc8.

Make sure that NetBIOS over TCP/IP is enabled (not default) on all
computers:

1. Open the Network Connections folder.
2. Right click the local area network connection.
3. Click Properties.
4. Click Internet Protocol (TCP/IP).
5. Click Properties.
6. Click Advanced.
7. Click WINS.
8. Click the Enable NetBIOS Over TCP/IP button.

To see if a firewall is causing problems, start pc1 and pc8 in "Safe
mode with networking" and try accessing pc8.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Back
Top