upgrade to xp he can't see network

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Upgraded from ME to XP HE. With Linksys NC100 network card, now I cannot ping my local router (or connect through the router to my cable modem). Failing ping test to network, from cmd line and from network troubleshooting scan. Updated NIC drivers loaded from Linksys site, then from another third party site. No luck with either. With ipconfig/all, ip address has been assigned and other settings seem ok. Everything still works fine to the inet from two other home PC's, one on 98 and one on W2000

Any suggestions? May buy another NIC, but I am concerned I am missing something basic with XP that is not card related.
 
johng said:
Upgraded from ME to XP HE. With Linksys NC100 network card, now I cannot
ping my local router (or connect through the router to my cable modem).
Failing ping test to network, from cmd line and from network troubleshooting
scan. Updated NIC drivers loaded from Linksys site, then from another third
party site. No luck with either. With ipconfig/all, ip address has been
assigned and other settings seem ok. Everything still works fine to the
inet from two other home PC's, one on 98 and one on W2000
Any suggestions? May buy another NIC, but I am concerned I am missing
something basic with XP that is not card related.

You don't say which IP address it gave you. If it's 169.254..x.x then that
means dhcp failed.
 
The assigned ip address is in the 192 range, although I have seen a 169. address a few times after I have tried various network settings.
 
johng said:
The assigned ip address is in the 192 range, although I have seen a 169.
address a few times after I have tried various network settings.
If your ip is set up for autodiscovery and your address is in the 192 range,
it proves that your pc managed to communicate with the router in order to
get an ip address at that time.

When you get an ok IP address in the 192 range, and you ping router/wan with
no result, did you try releasing then renewing the IP address? (always
release before trying renew)

Have you tried changing your cable and swapping it to another port on the
router?
 
Thanks for your time. The culprit turned out to be Zone Alarm. I deinstalled zone alarm and it now works fine. Since Zone Alarm was not in the tool bar, as it had been in ME, I had thought it was not running.

----- CheshireCat wrote: -----


johng said:
The assigned ip address is in the 192 range, although I have seen a 169.
address a few times after I have tried various network settings.
If your ip is set up for autodiscovery and your address is in the 192 range,
it proves that your pc managed to communicate with the router in order to
get an ip address at that time.

When you get an ok IP address in the 192 range, and you ping router/wan with
no result, did you try releasing then renewing the IP address? (always
release before trying renew)

Have you tried changing your cable and swapping it to another port on the
router?
 
Back
Top