mikethacker
asked on
No Internet, good tcp/ip, good winsock, and on the network...
I have a XP Pro w/SP2 pc on the network. I reinstalled tcp/ip, winsock, and it is seeing other pc's. When I do ipconfig, all seems as should be there. The other pc's on the network get online fine. I don't know what to do next.
How are you connecting to the internet?
First, lets test using Ping..
Step-1: Ping Loopback IP address (127.0.0.1). Success shows that TCP/IP is properly installed.
Step-2: Ping local NIC's IP address. Success shows that NIC is working properly.
Step-3: Ping Default Gateway. Success shows that local physical layer connections are ok.
Step-4: Ping Remote IP address. Success shows that remote physical layer connections are ok.
http://65.24.134.81/KipSolutions/P2PNetworks/PingUtility.htm
Also, this is primarily for P2P Lans, but may provide you with some useful steps..
http://65.24.134.81/KipSolutions/P2PNetworks/TroubleshootingP2P.htm
Step-1: Ping Loopback IP address (127.0.0.1). Success shows that TCP/IP is properly installed.
Step-2: Ping local NIC's IP address. Success shows that NIC is working properly.
Step-3: Ping Default Gateway. Success shows that local physical layer connections are ok.
Step-4: Ping Remote IP address. Success shows that remote physical layer connections are ok.
http://65.24.134.81/KipSolutions/P2PNetworks/PingUtility.htm
Also, this is primarily for P2P Lans, but may provide you with some useful steps..
http://65.24.134.81/KipSolutions/P2PNetworks/TroubleshootingP2P.htm
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What other protocols are you running? Is is straight TCP/IP, or do you have NWlink and/or NETBUEI running as well? can you post a copy of your "ipconfig /all" results? Have you tried accessing web sites based on IP as opposed to be hostname? DNS problems can frequently masquerade as TCP/IP connectivity problems... Have you tried a tracert to any distant sites? Try pinging 66.102.7.99 (google.com). If you can't ping it, try a tracert to it. If the tracert doesn't work, post the results up...
V/R,
Ian Tarasevitsch
V/R,
Ian Tarasevitsch
ASKER
I found the answer. I rebooted the firebox and now that the arp table is clear, NOW I get online. THANKS FOR YOUR HELP EVERYBODY. Mike
Thanks! Next time, try clearing the ARP Cache with the following command:
arp -d *
FE
arp -d *
FE