Can't connect to the internet on WinXP using a wireless connection

[amit.arora.nd]

My laptop almost learnt to fly 15 minutes back :-8

I am trying to connect my sony vaio laptop [winxp sp2, Intel(R)
PRO/Wireless 2200BG] to a DSL based broadband internet connection using
a wireless lan. The system is configured to pick up an IP address and
DNS server address using DHCP.

My problem is that the laptop does connect to the wireless router
[Microtek] but is not able to establish an internet connection [opening
a webpage in IE does not work]. I called up the service provider's
helpdesk and this guy concluded that the windows is not picking up the
correct IP address. The IP address should be in the 192.168.1.xxx
range, but windows assigns an IP address in the 168.xxx.xxx.xxx range.
When I connect my laptop to the wireles router using a ethernet cable,
an IP address in the 192.168.1.xxx range gets assigned and I am able to
log on to windows. Assigning an IP address manually on the wireless
connection didnt help.

I read on some internet post that some windows security updates cause
a similar problem where windows can connect to the wireless router, but
fails to receive any packets from it. My windows installation is upto
date with the most recent updates installed.

Please help!!

Thanks,
Amit

 

[Chuck]

My laptop almost learnt to fly 15 minutes back :-8

I am trying to connect my sony vaio laptop [winxp sp2, Intel(R)
PRO/Wireless 2200BG] to a DSL based broadband internet connection using
a wireless lan. The system is configured to pick up an IP address and
DNS server address using DHCP.

My problem is that the laptop does connect to the wireless router
[Microtek] but is not able to establish an internet connection [opening
a webpage in IE does not work]. I called up the service provider's
helpdesk and this guy concluded that the windows is not picking up the
correct IP address. The IP address should be in the 192.168.1.xxx
range, but windows assigns an IP address in the 168.xxx.xxx.xxx range.
When I connect my laptop to the wireles router using a ethernet cable,
an IP address in the 192.168.1.xxx range gets assigned and I am able to
log on to windows. Assigning an IP address manually on the wireless
connection didnt help.

I read on some internet post that some windows security updates cause
a similar problem where windows can connect to the wireless router, but
fails to receive any packets from it. My windows installation is upto
date with the most recent updates installed.

Please help!!

Thanks,
Amit

Amit,

Is that 168.xxx.xxx.xxx, or 169.xxx.xxx.xxx? 169.xxx.xxx.xxx is APIPA.
<http://nitecruzr.blogspot.com/2005/07/limited-or-no-connectivity.html>

If you have an APIPA address, unless the problem is with the DHCP server itself
(a rare scenario), manually assigning an address is useless. You have to fix
the problem.

When did this problem start happening? What changes were made just prior to its
being observed? Yes, Windows Updates security updates have been known to have
numerous consequences. What is in the WU log just before the problem was
observed?

 

[amit.arora.nd]

Hi Chuck,

I think I made a mistake: the address that is getting assigned is
indeed in the 169.x.x.x series.

I had never used a wireless connection on this laptop before so there
were was no particular "incident" which caused this problem.

As far as the window update is concerned, "Automatic updates" is turned
on my computer so windows keeps itself up to date.

Thanks,
Amit

 

[Chuck]

Hi Chuck,

I think I made a mistake: the address that is getting assigned is
indeed in the 169.x.x.x series.

I had never used a wireless connection on this laptop before so there
were was no particular "incident" which caused this problem.

As far as the window update is concerned, "Automatic updates" is turned
on my computer so windows keeps itself up to date.

Thanks,
Amit

Amit,

OK, so you are getting the APIPA address. Now you have to figure out why. That
will be the fun part. Maybe my main article will be relevant:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>

And remember "Automatic Updates" is a 2 way sword. Like "Intel Inside", it may
be an advertisement, or a warning. Always be aware of when "Automatic Updates"
are applied, and when problems start.