XP local ping fail

  • Thread starter Thread starter Alan Yankowski
  • Start date Start date
A

Alan Yankowski

I just upgraded my 98 machine to XP PRO. I have it
connected to a DSL modem through a Linksys router. All of
this worked fine before the upgrade. The router
automatically assigns IP addresses. When I run ipconfig,
I see correct addresses for the router and computer. When
I ping localhost 127.0.0.1, I get a proper response. When
I ping my IP address 196.169.1.100, I get "transmit
failed, error code 65". I have tried reinstalling the
TCP/IP driver as recommended yesterday by removing both
winsock entries from the registry and reinstalling from
\windows\inf. No help. If I try to renew the IP address,
I get "". If I look at the status window, it seems that I
send packets, but very, very few are returned. The router
DHCP table finds the mac address of the network card.

I am at a loss for things to try.
 
Alan Yankowski said:
I just upgraded my 98 machine to XP PRO. I have it
connected to a DSL modem through a Linksys router. All of
this worked fine before the upgrade. The router
automatically assigns IP addresses. When I run ipconfig,
I see correct addresses for the router and computer. When
I ping localhost 127.0.0.1, I get a proper response. When
I ping my IP address 196.169.1.100, I get "transmit
failed, error code 65". I have tried reinstalling the
TCP/IP driver as recommended yesterday by removing both
winsock entries from the registry and reinstalling from
\windows\inf. No help. If I try to renew the IP address,
I get "". If I look at the status window, it seems that I
send packets, but very, very few are returned. The router
DHCP table finds the mac address of the network card.

I am at a loss for things to try.
Click to expand...


Error 65 usually indicates a firewall problem.
It is either misconfigured or has been incorrectly un-installed.

Un-install any firewall as per the manufacturer's
instructions during troubleshooting.

This can also be caused by the incorrect and
incomplete removal of a firewall.

If you un-install a firewall from add / remove programs,
it can often leave debris behind like rogue services.

For example, if you un-install zonealarm like this,
the TrueVector service may continue to run.

The fix for this is to re-install the firewall and then un-install
it correctly. Consult the manufacturer's website for details.

For example, with ZoneAlarm, you need to go to the
ZA control panel, and un-check 'run at startup'.
Then re-boot, so ZA is no longer running, then un-install it.
 
bromis

Dear Ron

I am in the middle of the same Error code 65 problem and have recently uninstalled my Zonelab firewall.

This may be a silly question, but how do I reinstall Zonelab if I cannot access the internet at home ?

Regards, Bromis


Ron Lowe said:
"Alan Yankowski" wrote in message
news:[email protected]...
> I just upgraded my 98 machine to XP PRO. I have it
> connected to a DSL modem through a Linksys router. All of
> this worked fine before the upgrade. The router
> automatically assigns IP addresses. When I run ipconfig,
> I see correct addresses for the router and computer. When
> I ping localhost 127.0.0.1, I get a proper response. When
> I ping my IP address 196.169.1.100, I get "transmit
> failed, error code 65". I have tried reinstalling the
> TCP/IP driver as recommended yesterday by removing both
> winsock entries from the registry and reinstalling from
> \windows\inf. No help. If I try to renew the IP address,
> I get "". If I look at the status window, it seems that I
> send packets, but very, very few are returned. The router
> DHCP table finds the mac address of the network card.
>
> I am at a loss for things to try.


Error 65 usually indicates a firewall problem.
It is either misconfigured or has been incorrectly un-installed.

Un-install any firewall as per the manufacturer's
instructions during troubleshooting.

This can also be caused by the incorrect and
incomplete removal of a firewall.

If you un-install a firewall from add / remove programs,
it can often leave debris behind like rogue services.

For example, if you un-install zonealarm like this,
the TrueVector service may continue to run.

The fix for this is to re-install the firewall and then un-install
it correctly. Consult the manufacturer's website for details.

For example, with ZoneAlarm, you need to go to the
ZA control panel, and un-check 'run at startup'.
Then re-boot, so ZA is no longer running, then un-install it.



--
Best Regards,
Ron Lowe
MS-MVP Windows Networking
Click to expand...
 
Back
Top