altric
asked on
Cannot ping a computer name...
Hi everyone,
I have a situation here where I could ping an IP of a computer but how come I couldn't ping with its computer name?
Thank you.
I have a situation here where I could ping an IP of a computer but how come I couldn't ping with its computer name?
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for everyone's response.
I have tried the Quick and dirty fix way mentioned by Thrasymachus and it works.
So, may I know what is actually happening here?
Does it mean that there are two computers having the same computer name on the network which caused this problem happened or there are other possibilities?
FYI, my network is using Class C IP address,
Please advise.
I have tried the Quick and dirty fix way mentioned by Thrasymachus and it works.
So, may I know what is actually happening here?
Does it mean that there are two computers having the same computer name on the network which caused this problem happened or there are other possibilities?
FYI, my network is using Class C IP address,
Please advise.
>>there are other possibilities
definately, what the hosts file does is resolve the host name to the ip, because windows could't do it any other way (dns, wins, etc)
definately, what the hosts file does is resolve the host name to the ip, because windows could't do it any other way (dns, wins, etc)
type: 'ipconfig /all'
at a command prompt and post the results. this will help
at a command prompt and post the results. this will help
I spent over a day trying to track down a solution for this problem, and couldn't figure out the solution until I considered some of what you guys had said here.
I notice this question has an accepted answer, but I think I have a more "permanent" solution beyond the "quick & dirty answer". See "Solution B" specifically below. This should apply for any standard networking setup, involving most windows networks unless there is a centralized authentication occuring on the network (such as a Win2K or WinXP box maintaining an user/password authentication on the network).
When you create a new network connection (or try to use the standard setup in most installations) you encounter two common issues in XP:
Problem Part 1)
Multiple connections (LAN, Wireless, 1394) may be setup as bridged connections, which may cause a variety of problems and security issues.
Problem Part 2)
You may not be able to properly see other computers on your LAN, even though you might be able to ping the other computer's IP address.
Solution Part 0)
Generally, it's a good idea to install NetBEUI, as this will maintain better connectivity across multiple a multi-version Windows network and will ensure a more secure Sharing environment. This must be installed from the Valueadd/MSFT/Net/NetBEUI directory (simplest location to find this is on your original XP CD). Be sure to:
a) unbind "Client for Microsoft Networks" and "File & Printer Sharing" from TCP/IP
b) WinS->NetBIOS : Set this to either Default, or Enable NetBIOS over TCP/IP if you need it to remain this way even if static DHCP is being used.
For more info see:
The NetBEUI Protocol Is Not Available in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;306059
How to install NetBEUI on Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;301041
Solution Part 1)
See:
Windows XP Setup Creates a Network Bridge Between Two or More Network Devices
http://support.microsoft.com/default.aspx?scid=kb;en-us;816486
How to prevent the Network Setup Wizard from creating a bridge in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;283429
(Though I wouldn't trust #283429, as it can cause other problems in network setup)
You Cannot Connect to Other Computers After Running Network Setup Wizard
http://support.microsoft.com/default.aspx?kbid=823305
Basically,
i) Click Start, right-click My Network Places, and then click Properties to open Network Connections.
ii) In Network Connections, right-click Network Bridge, and then click Disable.
iii)Right-click Network Bridge again, and then click Delete. Click Yes to confirm that you want to delete the network bridge.
Solution Part 2)
Go to TCP/IP->Properties->Advanc
Uncheck "Register this connections addresses in DNS"
This resolves the primary problem. When this is checked, an XP machine seems to separate itself from most common network connection systems as if it is intended to be providing itself as host of an Internet Connection Sharing situation. Yet, as most people avoid this configuration, the internal DNS is disparate from the existing network and the computer cannot see other computers on the network and vice versa.
Hope this helps. I've run into similar problems before, and couldn't rely on the "temp" solution as it's for a client, not my own. In fact, this was similar to the first problem I encountered the first time I had to troubleshoot an XP machine -- within 5 minutes I experienced bluescreened+reboot. I felt secure that I dominated XP at that point ;)
I notice this question has an accepted answer, but I think I have a more "permanent" solution beyond the "quick & dirty answer". See "Solution B" specifically below. This should apply for any standard networking setup, involving most windows networks unless there is a centralized authentication occuring on the network (such as a Win2K or WinXP box maintaining an user/password authentication on the network).
When you create a new network connection (or try to use the standard setup in most installations) you encounter two common issues in XP:
Problem Part 1)
Multiple connections (LAN, Wireless, 1394) may be setup as bridged connections, which may cause a variety of problems and security issues.
Problem Part 2)
You may not be able to properly see other computers on your LAN, even though you might be able to ping the other computer's IP address.
Solution Part 0)
Generally, it's a good idea to install NetBEUI, as this will maintain better connectivity across multiple a multi-version Windows network and will ensure a more secure Sharing environment. This must be installed from the Valueadd/MSFT/Net/NetBEUI directory (simplest location to find this is on your original XP CD). Be sure to:
a) unbind "Client for Microsoft Networks" and "File & Printer Sharing" from TCP/IP
b) WinS->NetBIOS : Set this to either Default, or Enable NetBIOS over TCP/IP if you need it to remain this way even if static DHCP is being used.
For more info see:
The NetBEUI Protocol Is Not Available in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;306059
How to install NetBEUI on Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;301041
Solution Part 1)
See:
Windows XP Setup Creates a Network Bridge Between Two or More Network Devices
http://support.microsoft.com/default.aspx?scid=kb;en-us;816486
How to prevent the Network Setup Wizard from creating a bridge in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;283429
(Though I wouldn't trust #283429, as it can cause other problems in network setup)
You Cannot Connect to Other Computers After Running Network Setup Wizard
http://support.microsoft.com/default.aspx?kbid=823305
Basically,
i) Click Start, right-click My Network Places, and then click Properties to open Network Connections.
ii) In Network Connections, right-click Network Bridge, and then click Disable.
iii)Right-click Network Bridge again, and then click Delete. Click Yes to confirm that you want to delete the network bridge.
Solution Part 2)
Go to TCP/IP->Properties->Advanc
Uncheck "Register this connections addresses in DNS"
This resolves the primary problem. When this is checked, an XP machine seems to separate itself from most common network connection systems as if it is intended to be providing itself as host of an Internet Connection Sharing situation. Yet, as most people avoid this configuration, the internal DNS is disparate from the existing network and the computer cannot see other computers on the network and vice versa.
Hope this helps. I've run into similar problems before, and couldn't rely on the "temp" solution as it's for a client, not my own. In fact, this was similar to the first problem I encountered the first time I had to troubleshoot an XP machine -- within 5 minutes I experienced bluescreened+reboot. I felt secure that I dominated XP at that point ;)
Of course, my suggestion in "Solution Part 2" played out to be practically completely wrong. I was able to communicate with some other PCs, but not all.... oh well.
But my other points are still valid.
But my other points are still valid.
Well I have this same problem but everything i have tried here has not worked so far. Every few hours my internet goes down. I called my isp and they said they couldnt help so i come here can anyone tell me is there anything else i can do to get my dns to work properly.
dns resolves host names to ip addresses