Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
- From: "NeoMagick" <neomagick@xxxxxxxxx>
- Date: 30 May 2006 12:00:00 -0700
Thanks for the responses everyone. Here's the answer to some
questions:
- Are you using WPA-PSK or WPA2-PSK?
WPA-PSK atm. WPA2-PSK gave us the same grief.
- Are there any MAC or IP filters running in the WAP54G?
None whatsoever.
- SBS2003 Standard or Premium edition?
SBS2k3 Std.
- Do you have enough IP addresses in the DHCP pool on the DHCP server?
Yes. There's not even 50 machines total on the network.
- Is the SBS2003 DHCP server pre-filtering the clients by MAC address?
No. The 2k3 DHCP server will hand an IP out to any machine that
connects to the network, on the domain or not, by WiFi or wire.
- Do you have some other form of security enabled on the SBS2003
server?
No.
- Do you have the SBS2003 server setup with NAT using one or two
ethernet cards?
No. NAT is running on a hardware firewall appliance. The SBS2k3
server is on a static IP on the private network behind the NAT router,
and has only one active ethernet line.
- I'll assume you're running Windoze XP Home using Wireless Zero Config
and the latest WAP54G v3 hardware.
All the machines are XP Pro, except for one employee's personal laptop
under XP Home (which successfully connects), and an older company
laptop that's running 2k Pro, which also successfully connects. Some
are set up using WZC, others using the mfgr's software (Intel and Dell
Wireless software). On machines that can't connect, both pieces of
software produce the same results (my first thought as well). Only
difference is the Intel and Dell software each report (and I quote)
"Encryption: TKIP; Key Absent" - DESPITE having entered the key
repeatedly, and the WZC showing a successful connection, passing
traffic, but no IP address.
- Yeah, but are you using Windoze Wireless Zero Config to do the
wireless connection or are you using whatever came with your PCMCIA
card? Uncheck "Let Windoze manage this device" to let the
manufacturers driver take control.
With the PCMCIA card, it's the WZC software. The Netgear app that the
driver package installed for it SUCKS. I'll post screenshots of
exactly how useless it is if you're interested.
- Can you find another DHCP server other than the SBS2003 server?
Can i find, as in is there a rogue DHCP server on the network? No,
there isn't. 2k3 SBS will shut down its internal DHCP server if it
finds another on the network. DHCP services have not dropped, and no
other devices were put on the network that would be a DHCP server (the
AP's are WAPs only), and there's no routers, only switches.
Can i find, as in can I set one up? It's a good thought. I'll take a
second router with me, and set up a private network with one of the
APs, as I'd rather not do anything to fsck with the SBS.
- OK. 3.04 is the latest for WAP54G v3 hardware. Did you try a hard
reset after upgrading the WAP54G firmware?
That's a good question - whats a hard reset defined as on these things?
With my BEFSR11, a hard reset was unplugging, holding down the reset
switch for 5 seconds, and plugging it back in, which would wipe out the
settings. With a WRT54G (v5) i discovered a hard reset was holding
down the reset switch for 30 seconds, and needed to be done after
upgrading the firmware (something I discovered only after an hours
worth of beating my head against a desk because the little cisco logo
kept lighting white, and it would ask for a firmware file when I opened
the admin page).
After I upgraded the firmware, I unplugged the device for 30 seconds,
and plugged it back in. Must confess, I didn't follow the mfgr's specs
for firmware upgrades. Are they different? I'll look into that today.
- You did say something that's stuck in my mind but I can't think
exactly why
at the moment..., But, Basically it had to do with one machine didn't
start
network services at all, and the other couldn't find a wireless card
(but
the fact it started the service, and then couldn't find a card - makes
me
think that the internal dell/windows stuff is starting no matter what,
and
then wigging out cuz a driver or something it needs isn't starting cuz
of
the safe boot). Got a USB dongle hanging around? You may want to give
that a try, cuz even
in safe mode it should look for USB devices.. Or even easier, does it
have a
switch for internal wlan stuff? You can just turn te internal off and
let it
use the dongle (so the built in and dongle don't conflict)
No, no USB wifi cards around. Only that PCMCIA card. Even in safe
mode tho, I think i'd have the problem I had. The 'network service'
didn't start, and wouldn't start. It wouldn't give me any network
devices in the network connections control panel (wired or wireless),
and the mfgr's wireless software would report 'no wireless card found'.
- You never mentioned the model number of the dell wireless cards that
don't work with WPA.... Could it be one that doesn't support it?
I've got them jotted down on notes onsite - I'll be able to pull them
up in a couple of hours. It's not just dell wireless tho, it's also
intel internal wireless. All the cards are listed as supporting WPA,
and I believe they do (my experience is that cards that don't support
WPA see the network, and when you try to join it says its out of range
- these aren't doing that). Dell sent out a replacement internal
Mini-PCI card that I installed, and am having the same trouble with.
I'll get model numbers out today.
Hope this helps - really appreciate any insight! Thanks,
NM
.
- References:
- WAP54Gs with WPA not handing out IPs from SBS2003 server
- From: NeoMagick
- Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
- From: Peter Pan
- WAP54Gs with WPA not handing out IPs from SBS2003 server
- Prev by Date: Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
- Next by Date: WAP + PCI Comparison?
- Previous by thread: Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
- Next by thread: D-LINK DWL - 520 PCI connection issue
- Index(es):
Relevant Pages
|
