[sdw2003] Wierd Question about Wireless- new laptop not getting IPaddress

Tad Braun tbraun at compendiainc.com
Tue Apr 22 15:37:55 PDT 2008


If it were me...

* I would take one of the laptops and take it somewhere else that has
Wi-Fi access. See if the behavior continues when trying to access a
different WAP. 
* I would either update, or downdate(?) the drivers on the laptop to see
if a different version fixes it.
* I would either update, or downdate(?) the firmware on the WAP to see
if a different version fixes it.

But most of my probing would come from taking the laptop to a different
scenario and see how it behaves. At least you will know if it's the WAP
or the notebook.

-----Original Message-----
From: sdw2003-bounces at mattware.com [mailto:sdw2003-bounces at mattware.com]
On Behalf Of Crossan Hays
Sent: Tuesday, April 22, 2008 2:50 PM
To: San Diego Windows 2003 User Group
Subject: [sdw2003] Wierd Question about Wireless- new laptop not getting
IPaddress

What we have:

2 Linksys WAP 4400N Access Points
On a domain- with DC, DHCP, etc.

We have 15-18 laptops here of different age and time of use.  Lately we
have purchased 5 new ones and other than wireless- all is well.  What we
got here is that(when setup correctly like the other machines), the
wireless nics on the newest laptops are in a vicious cycle of acquiring
the IP address and stopping> acquiring IP( all day long).  I can tell
you that there are sufficient IPs in DHCP(50-60% free) and the gui for
the WAPs are accessible(and all looks fine there).  I am using all the
correct config into to grant access.  Nothing has changed from the stand
point of the WAPs.  

At home I have no trouble to connect to my WAP.  Our WAP is the only one
that seems to reject these machines.  Linksys is no help(because the
WAPs are responding as desired for others) and the WAPs have no logs to
really track the discussion between the NIC and WAP/DHCP(not that I am
aware of).  What is strange is the fact that the older machines continue
to be connected and not manifest the same behavior.  Only the new MACs
to the WAP or DHCP seems to have problems.   

This issue is really bothering me and I am confused.  Nothing I do seems
to make any difference at this point.  CJ  


More information about the sdw2003 mailing list