|
|
|||
Home | Troubleshooting | Quick Setup | Cisco How to | Data Recovery | Forums | Blog | IT Exam Practice | Services | About Us | Chicagotech MVP | Search | Contact Us | |
|
Troubleshooting Ping
Can't ping another
computer because of the ICF Post your questions, comments, feedbacks and suggestions
Can't ping another computer because of the ICFSometimes, XP's built-in Firewall may enable after running network setup wizard on LAN connections. You can't ping or access the XP computer. To disable the XP firewall on the connection, go to the properties of the Connections, select Advanced, and deselect the firewall. If you can't ping outside IP, make sure you have correct gateway. If you can't ping outside computer name or web name, check the DNS settings. If you cannot use ping successfully at any point, confirm that: 1)The computer was restarted after TCP/IP was configured. Error code 65, 10043 and 10050, transmit failed Symptoms: When using ping command, you may receive either of the following: "Transmit failed, error code 65" or "Transmit failed, error code 10050" Resolutions: make sure your firewall, NAT or router doesn't disable ping and to allow ICMP Echo and Echo Reply packets. Symptom: when you try to ping an IP, you may receive "hardware error" reply.
Causes: 1. Bad NIC. Q: When I ping the server using one of the clients it says the host is
unreachable. Why? Ping lists a public IP instead of private IP Symptom: when you ping a LAN computer like ping chicagotechpc1, you may receive a public ip 64.176.153.103 instead of the computer private IP 192.168.1.100. Cause: Incorrect DNS settings. For consultants, refer to case 060104RL Receiving a reply from a different IP Symptoms: when you ping a public IP, you may
receive reply from a different IP, for example, Causes: If you have incorrect IPSec settings, you may have above mentioned symptom.
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2018
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.