HELP: XP machine can't run TCP apps, DHCP works ok

[Al Dykes]

Is there a way to reset my TCP stack? It seems to have been hosed,
somehow. Help, please.

I have an XP/sp2 laptop that has ceased to be able to do anything via
TCP. It gets good DHCP info but browser, email, telnet, etc go
nowhere. See below for examples.

Right now I have the laptop connected to a Linksys DSL router and a
w2k desktop also. The w2k machine works fine on the internet. It CAN
hit http://192.168.1.1 and get into the linksys admin page and it sees
the Internet.

The desktop and the laptop can't ping each other.

There is no firewall installed on the w2k machine

The laptop has Trend FW, turned off.

There is no other equipment connected to the gateway. I've swapped
cables and done all the small things.


Case 1
The desktop gets an IP of 192.168.1.100

The XP machine gets 192.168.1.101.
(other DHCP-assigned info matches. )

The XP machine can't ping the gateway or open the
admin page or access the Internet, etc.

The XP machine CAN ping 127.0.0.1

Case 2
Connect the XP machine directly to the Verizon modem
and reboot.

XP gets appropriate PPPoE info and logs into
the network and a message says ....registered on network...
(paraphrassing) when completed.

I've been on the phone with Verison support. They ran a line
test and say they've confirmed my account provisioning.
They confirmed that all my IPCONFIG/ALL numbers were
valid and appropriate.

I regularly use my XP machine directly to my Verizon modem.
It should work.

Case 3
WiFi. I visited a couple hotspot locations that I've used
before. They registered and gave reasonable DHCP info
but couldn't run TCP apps.

Case 4
PPP Dial. Same thing. I didn't take this to far
as I've never tried before to use the modem on this machine.

 

[Chuck]

Is there a way to reset my TCP stack? It seems to have been hosed,
somehow. Help, please.

I have an XP/sp2 laptop that has ceased to be able to do anything via
TCP. It gets good DHCP info but browser, email, telnet, etc go
nowhere. See below for examples.

Right now I have the laptop connected to a Linksys DSL router and a
w2k desktop also. The w2k machine works fine on the internet. It CAN
hit http://192.168.1.1 and get into the linksys admin page and it sees
the Internet.

The desktop and the laptop can't ping each other.

There is no firewall installed on the w2k machine

The laptop has Trend FW, turned off.

There is no other equipment connected to the gateway. I've swapped
cables and done all the small things.


Case 1
The desktop gets an IP of 192.168.1.100

The XP machine gets 192.168.1.101.
(other DHCP-assigned info matches. )

The XP machine can't ping the gateway or open the
admin page or access the Internet, etc.

The XP machine CAN ping 127.0.0.1

Case 2
Connect the XP machine directly to the Verizon modem
and reboot.

XP gets appropriate PPPoE info and logs into
the network and a message says ....registered on network...
(paraphrassing) when completed.

I've been on the phone with Verison support. They ran a line
test and say they've confirmed my account provisioning.
They confirmed that all my IPCONFIG/ALL numbers were
valid and appropriate.

I regularly use my XP machine directly to my Verizon modem.
It should work.

Case 3
WiFi. I visited a couple hotspot locations that I've used
before. They registered and gave reasonable DHCP info
but couldn't run TCP apps.

Case 4
PPP Dial. Same thing. I didn't take this to far
as I've never tried before to use the modem on this machine.

I'd start by looking for LSP / Winsock corruption. TCP/IP reset is part of the
procedure too. Be persistent here.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

 

[Al Dykes]

I'd start by looking for LSP / Winsock corruption. TCP/IP reset is part of the
procedure too. Be persistent here.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

TNX.