Hi everyone, I have a weird issue on my XP network. I have two xp boxes on a LAN with a switch ('cause other pc's are connected too.) but I can't ping my own pc from the other! (TimeOut) I even tried to ping it from another unix box same result. But I can ping myself on the loop IP (127.0.0.1). Here is my ipconfig /all : Windows IP configuration : Host name : bleh DNS : node type : unknown Ip routing enabled : No WINS Proxy enabled : No Ehternet adapter local Area connection : DNS Suffix : Description : Fast Ethernet Card Adresse physique : 00-00-00-00-00-00 DHCP enabled : no IP Address : 192.168.1.12 Subnet mask : 255.255.255.0 Default Gateway : 192.168.1.1 DNS Servers : 12.127.16.82 But one other weird thing is I still can share files from and to my box with other pc's xp or unix. I also have internet access through the Unix gateway... which is possible because the Unix box can identify my box as the 192.168.1.12 box. Does anybody know the problem? Thanks. Lancelot.

Is there a firewall installed on either machine? I am wondering if the Windows firewall is enabled, or you have a third-party firewall that blocks ping requests. I recall I had the Symantec Corporate firewall installed and wasn't able to ping local computers, as the network addresses weren't in my "trusted" zone. Just a thought.

Here is my info on the subject , maybe it's in here . Can't ping in XP . http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/proddocs/ping.asp http://support.microsoft.com/?kbid=314067 Maybe a firewall , is stopping it ! Turn it off . http://www.computer-forums.co.uk/forum/viewtopic.php?t=5158&start=0&postdays=0&postorder=asc&highlight=&sid=967547c7ea38828a8a83336132a9a22a http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/sag_DNS_tro_UsingIpconfigFlushdns.asp IPCONFIG /flushdns To flush and reset a client resolver cache using the ipconfig command The Host file may be the cause . http://discussions.virtualdr.com/showthread.php?s=&postid=613462#post613462 http://www.smartin-designs.com/ http://www.accs-net.com/hosts/faq.html#2 First of all, using 127.0.0.1 in your HOST file is not a great idea. It is a good idea, but not great. The reason, 127.0.0.1 is a real and valid IP. If you have a very large HOST file, your machine is going to be looking for the server on your machine. e.g. You have "adserver.com" listed as 127.0.0.1 in your HOST file. Every time you visit a page and "adserver.com" is in the html, your computer is going to actively look for that server on your computer. You do this with enough pages and your computer will spend resources looking for the server on your computer - every time. Another side effect of this, you will notice your "back" button doesn't work very well. Sometimes, your back button will stick on the same page, because, it is trying to connect to the last server process to time out: "adserver.com" - loopback. You may need to click "back" two or three times to get back one page. It is a big pain becasue it can really mess up being able to go back. And if your HOST file is located on a server accessed by many comps, you will notice the traffic slows other functions. THis site is a great example of the above. The solution is to use a valid IP format, but not a valid address. 0.0.0.0 is a valid IP format, but an invalid IP. Your computer will not search for the server on your computer and as a result, it will not slow the computer or cause your "back" button to operate incorrectly. Try pinging "adserver.com" when HOST is 127.0.0.1, you notice, you will get a return, it is a valid and working IP. Now, try pinging "adserver.com" when HOST is 0.0.0.0, you notice an immediate timeout. Save your computer from working needlessly. Change your HOST file lockout IPs to 0.0.0.0 If you would like to completely disable your Hosts file, rename it to "Hosts.txt". When you want to use it again, change it back to "Hosts". http://www.accs-net.com/hosts/how_to_use_hosts.html http://www.sover.net/~wysiwygx/Security1.html http://members.rogers.com/hfc/HostFileChecker.zip Host File Checker Searches through your System's Host file and removes duplicate entries from the Host file. Your Host file allows you to block sites of your choice by IP or name. Ensure that comments have been taken out of the Host File since it will most likely include that as part of the duplication check. Q: Can ping IP but not computer name http://www.chicagotech.net/netfaqs.htm I have two machines, one running win2k and one running win98,.These machines are already happily sharing an internet connection through a Netgear RP614 Cable/DSL router. I can ping each machine from the other. When I'm on one machine, I can't see the other in Network Neighborhood. How do I troubleshoot this? A: If you use net view \\computer and get System error 53, you have name resolution problem. Try to be able access the computer by using net use H: \\IP\sharename . If you get error 5 and access is denied. You may have permission issue and can't access the computer using net use \\IP|sharename. Now, if it is name resolution problem and, you may need to 1) check enable NetBIOS over TCP/IP in the network settings; 2) make sure browse service is enabled. If it is permission issue, you may want to make sure 1) enable file and printer sharing in the accessed computer; 2) setup the same workgroup, logon the same user account; 3) you may try to enable guest account if it is W2K or XP; 4) enable simple file sharing if it is XP. Q: I can ping, connect to other pc shared folders using UNC, but not browse the PC I have a mixed workgroup network. I can ping, connect to other pc shared folders using UNC format. But I can not browse the other PC... The error is... \\Computer name is not accessible. you might not have permission to use this network resources. A: In a Win9x, WinME, NT, 2000 and XP mixed-mode workgroup network, you can access shares using UNC (\\computername\sharename), but can't browse the computers in My Network Places or Network Neighborhood. This most common problems in a mixed-mode network are due to TCP/NetBEUI/IPX mismatches and Master Browser election problems. Resolution: 1) Enable NetBIOS over TCP/IP on 2000/XP. 2) Disable the Computer Browser service on the XP machine. 3) make sure no firewall running.