[sdw2003] Weird Question about Wireless- new laptop not gettingIPaddress

[SDtechguy]

Tom,
Probably a good idea for Crossan to use try "G". This link shows how "N"
stomps over half the usable frequencies.
http://www.metageek.net/image/80211n-wi-spy (see bottom graphs)
http://www.metageek.net/docs-device-signatures/80211g Ordinarily, with "b",
one would be looking at a peak with a normal distribution. 

I use this spectrum analyzer/device. Makes for hi impact communication, eh?
GK
PS I've been getting more requests for (1 gig) cat 6 cabling...are you
fellows sure those d*sk j*ck*ys can't take the extra 4.5 seconds it take to
plug in an RJ 45? (-:
 

-----Original Message-----
From: sdw2003-bounces at mattware.com [mailto:sdw2003-bounces at mattware.com] On
Behalf Of Tom Lively
Sent: Tuesday, April 22, 2008 9:19 PM
To: San Diego Windows 2003 User Group
Subject: RE: [sdw2003] Weird Question about Wireless- new laptop not
gettingIPaddress

Two thoughts:
Are the new laptops set to attempt to set up 802.11n connections if
available? Are they set for a specific channel or do they auto  roam?

Is there any other significant 2.4Ghz source in the neighborhood?  That
would include cell towers, microwaves, cordless phones, wireless access
relay points etc.  I had a nightmare and a half with 802.11n equipment in a
building that had two major wireless network  access points on the roof.

If any of the above is true, try forcing all your clients and access points
to 802.11g and try forcing to a specific channel (like 3).  Remember these
channels over lap so keep at least 2 or 3 channels between channels that are
in use.

Tom

-----Original Message-----
From: sdw2003-bounces at mattware.com
[mailto:sdw2003-bounces at mattware.com]On Behalf Of James Eitzen
Sent: Tuesday, April 22, 2008 7:32 PM
To: San Diego Windows 2003 User Group
Subject: Re: [sdw2003] Wierd Question about Wireless- new laptop not
gettingIPaddress


Is there a mac filter list on the AP?
On Tue, Apr 22, 2008 at 3:37 PM, Tad Braun <tbraun at compendiainc.com> wrote:

> 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
> _______________________________________________
> sdw2003 mailing list
> sdw2003 at mattware.com
> http://lists.mattware.com/mailman/listinfo/sdw2003
>



--
James Eitzen
_______________________________________________
sdw2003 mailing list
sdw2003 at mattware.com
http://lists.mattware.com/mailman/listinfo/sdw2003

_______________________________________________
sdw2003 mailing list
sdw2003 at mattware.com
http://lists.mattware.com/mailman/listinfo/sdw2003