Question Locked

Windows SBS DHCP with wireless access point

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running Windows Server 2003 SBS with normal clients getting IP's via the servers DHCP.
When adding a wireless access point (WP), wireless DHCP clients do not get an IP address unless I activate the WP's own DHCP service, even though the WP is on the same subnet. It appears not to pass on IP client requests to the SBS DHCP server. I have worked around that by activating the WP's DHCP service with a small scope range which does not overlap with the SBS DHCP's scope. But that does seem to cause its own problems.
Since I prefer using the SBS DHCP server how can I get dynamic IP addresses issigned to WP clients without resorting to two DHCP servers on the network?
Thanks for your help
OT

7 replies

by detailweb01

If you are using a consumer level cable modem router (the internal DHCP leads me to this conclusion), be sure that you aren't using the WAN port. Connect your LAN to one of the switch ports on the router.

I'm having a similar issue using Cisco 1200 series WAPs. The wireless clients connect to the network fine, but cannot get an IP address from the Server 2003 sp2 BDC on that particular network segment, if you wait 5 minutes and ipconfig /renew - repair the connection it works fine.

The APs, clients, and BDC all reside at the remote site on the same segment.

by dlh

If you're only using WEP encryption on your Access Points, and assuming you have configured the Access Point correctly you can pretty much just hang it off of your network and it will work just fine. If however you are using WPA or WPA2 encryption there are server side configuration prerequisites. This sounds like your issue.

This is going to require installation and configuration of the both Small Business Server 2003 Certification Authority (CA) service and Internet Authentication Service (IAS) as well as several other steps including creating a new group policy.

http://www.microsoft.com/technet/solutionaccelerators/smbiz/sitsol/DsgnNwrk_12.mspx?mfr=true

by sgt_shultz

don't configure your wap as a router, you need it just to 'hang on your network' like a wired connection, yes? that means 'bridge' mode. then all the dhcp, dns, ip address issues will go away. consult the mfg website of your wireless device for instructions.

by mdphoenix

I'd look in to the features of the router.

I have a Netgear Wireless Router that I tried to do the same thing with. The problem I ran into was the same thing. Wireless clients couldn't pull an IP from the server. The Netgear doesn't pass DHCP requests through it. They stop @ the router. I ended up buying a Linksys WAP54G to resolve the problem.

I hope this helps.

by sgt_shultz

you can create a dhcp forwarder but guys, that is not the problem. don't configure the thing as a router, in this case i do believe you just want it to be a wireless access point. Bridge mode.

This discussion is closed to new replies.