LAN problems after update to XP2

[Red Kite]

I have just updated a Windows XP1 (Home Edition) to XP2 and downloaded and
installed all of the recommended fixes. On restart I cannot access either of
two LANs which worked before updating.

1 A wireless LAN - this shows "limited or no connectivity" When I try to
connect it fails.
When I try "repair" Windows Disconnects/reconnects to the Wireless network
and fails to connect
"for assistance contact the person who manages your network" - that's me.


2.An Ethernet 100 LAN - the taskbar indicates that the connection is OK, and
shows correctly if I unplug and replug the cable - however IE cannot access
the internet via my ADSL/LAN router.
If I ping the router I get "Destination Host unreachable".
Pinging the router from another PC on the same router goes OK - indeed I am
using the working PC to post this.


I have been through the Network setup wizard many times, and the wireless
set up wizard.

SP2 firewall is OFF and it makes no difference whether ZoneAlarm is on or
off.

Am now at wit's end, and backing up the system again prior to Restoring back
to pre SP2 which I don't want to do.

Any suggestions ?

Network properties for both look normal - have checked the LAN settings
against the machine I am using now.

 

[neil]

This may not help. I have read that problems can occur after installing SP2
if there is spyware running on the PC. With that in mind have you run any
adware/spyware check either before or since installing SP2.
I would suggest Ad-Aware (personal) from
http://www.lavasoftusa.com/software/adaware/
and Spybot from http://www.safer-networking.org/en/download/index.html

best of luck
Neil

 

[Red Kite]

Neil
Have run full scans with Microsoft AntiSpyware - only one minor hit
Thanks for the suggestion will eliminate even that hit - but doubt that's
it - if it is I'll post here
Red

 

[Red Kite]

Neil - Just eliminated the one spyware - still in trouble - Red

 

[neil]

If you haven't done it already I think I would still use Ad-Aware & Spybot
just to be sure, I haven't found one scanner that finds all instances of
spyware. I'll have a think about your original description of the problem &
see if I can think of anything else.
Neil

 

[neil]

Hi,
Just to run through some things:
1. Have you tried re-starting the router.
2. What security do you have set-up on the router. Is there restricted
access for wireless, LAN or WAN.
3. Does the wireless connection use a WPA key or similar, if so have you
deleted those settings and created a new one inputting the pass key again.
4. Is the PC you are using wireless or wired.

Neil

 

[Red Kite]

Neil,

Sorry for the delay - Murphy's law - the Ethernet cable to the failing PC
just "disconnected" - so have rejigged my cabling and the Problem PC is now
connected via the cable that the good PC was using, and the GOOD PC is using
a spare cable.

Have restarted the router -

Situation now is that both PCs are showing up on the router, but the failing
PC cannot PING it, but the PING works OK from the good PC.

The router predated hardware firewalls and has only NAT - which has been
very effective over the last few years.

I am concentrating on getting the Problem PC to work on the wired network to
which it is connected along with this Good PC. Its wireless connection is on
another network where it is the only wireless PC, so I have no comparator. I
think that if I can solve the wired problem, then the wireless problem may
also get fixed - if not I can at least run the PC on a long cable
temporarily.


Problem is I need to download Ad-Aware onto this machine and transfer it the
old way to the other machine since it has no working network access. I'll
have a go at that in a minute or so.

John

 

[Red Kite]

Neil,
Now have LAN connection working - after hunting on Google, found an article
referring to the PING problem - then realised that one of the Microsoft
fixes had forced the LAN connection to use a specific IP address and
subnet - one I changed it to automatic - PING worked and I now have a
working Internet Explorer over the hard wired LAN. Whew!!!! what a relief as
the user wants this system back on line on Tuesday !

Thanks for sticking with me

Now I can chase the wireless LAN problem - have just checked it is not due
to forcing the IP address - these are set to automatic - so it looks to be a
different problem.

In we go.................

Red