SP2 XP Pro & TCP/IP not working

  • Thread starter Thread starter Jackson Smith
  • Start date Start date
J

Jackson Smith

Recently installed SP2 on XP Pro. Earlier, I could
connect with my wired LAN card (but the connection would
not renew without reboot -- get "socket operation ... on
dead network error). Based on feedback from Lance, I
checked the corrupt winsock keys, deleted them and
reinstalled TCP/IP.

Now, XP indicates the wired LAN card is "connected" to
the wireless router with automatically assigned IP
address, etc.; however, IE does not work (can't access my
home page) and I'm unable to ping the wireless router.

Please help.
 
Good, this is progress. Can you ping anything else (127.0.0.1, your own
IP address, your homepage, yahoo.com)? Where is your homepage? Were you
able to do these things before?

Check your IP address (ipconfig /all at the cmd prompt), post it back here.

Check your TCP/IP settings (including the "Advanced" sections - "Enable
TCP/IP filtering..." should not be checked).

Lance
*****

Jackson Smith thought carefully and wrote on 9/6/2004 11:03 AM:
 
No, I am unable to ping anything else (homepage is
yahoo.com) or connect to anything else (google, etc.).
The IP address automatically assigned to the LAN card by
the wireless router was 192.168.2.2.

Since I was unable to access the Internet after
reinstalling TCP/IP, I restored to the last system
checkpoint and am now responding to this post on the
prior wired LAN connection with the same errors
previously noted.
 
Lance said:
Good, this is progress. Can you ping anything else (127.0.0.1, your
own IP address, your homepage, yahoo.com)? Where is your homepage?
Were you able to do these things before?

Check your IP address (ipconfig /all at the cmd prompt), post it back
here.

Check your TCP/IP settings (including the "Advanced" sections -
"Enable TCP/IP filtering..." should not be checked).

Lance
*****

Jackson Smith thought carefully and wrote on 9/6/2004 11:03 AM:
Click to expand...

FWIW, I have found that if TCP/IP filtering is disabled but Permit Only
had been selected (Windows Firewall?), just this problem occurs. Enable
TCP/IP filtering, then select Permit All. See if the connection can be
made. If it can, then try disabling TCP/IP filtering in the Permit All
state. Sometimes that works, sometimes it does not. I leave filtering
enabled.

Q
 
Back
Top