Adding Wireless to a Win 2003 AD DSL home network

Hi,

I need some advice. I currently have a network in my home. Here is a
simplified version of my setup (for ease of explaining my problem). I
have dsl with a static IP running into a DSL router/switch. In that
switch I have 3 computers. The first one is a Windows 2003 Server
running AD with DNS and DHCP. The second is WinXP Pro (CAT5 to the
same switch). Last one is my laptop (with wireless connection).

I have replaced the router/switch recently with a wireless DSL router
(Linksys WRT54G). I turned off DHCP on the router and set it up as a
gateway.

WHAT WORKS:
All of the workstations work correctly if plugged into the switch on
the Linksys, they get assigned the correct ip/dns form the DHCP server
running on the Win 2K3 box and can navigate the local network and the
internet.

PROBLEM:
When I connect wirelessly with the laptop, I get a connection to the
linksys (says strength Excellent), everything looks good, BUT ipconfig
shows 0.0.0.0. I realize that I can only run 1 DHCP server on the
network (at least I think that is the case), but why cant my laptop
see the dhcp server?

SIDE NOTE:
I had this setup before without AD running dhcp and I was running DHCP
on the Linksys router. The laptop worked perfectly then (actually
everything worked correctly). Since I moved the DHCP service to the AD
machine instead of running it on the router I have been out of luck
wirelessly( as described above). I need DHCP running on the server
because I want to mess with VPN on the Win 2K3 box and it will have to
run DHCP so it can assign in comming clients an IP.

Any suggestions would be great, I know this is not a new problem but I
am not a network engineer, just a programmer who likes to tinker with
networking.

Thanks!

Jeff

Have you set up your 2003 server as a RADIUS server? What you're
effectively doing with the wireless laptio is logging onto the 2003 domain
as a remote access client, so you'll need to configure the 2003 server to
handle incoming "remote" connections. (Even if the "remote" connection is
only 20 feet away! :-) )

Check out this reference guide -
http://www.microsoft.com/windowsxp/p.../80211corp.doc,
it has some good step-by-steps to do what you're trying to do.

Hope this helps,

Laura


--
************************************
Laura E. Hunter - MCSE, MVP
Replies to newsgroup only



"Jeff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I need some advice. I currently have a network in my home. Here is a
> simplified version of my setup (for ease of explaining my problem). I
> have dsl with a static IP running into a DSL router/switch. In that
> switch I have 3 computers. The first one is a Windows 2003 Server
> running AD with DNS and DHCP. The second is WinXP Pro (CAT5 to the
> same switch). Last one is my laptop (with wireless connection).
>
> I have replaced the router/switch recently with a wireless DSL router
> (Linksys WRT54G). I turned off DHCP on the router and set it up as a
> gateway.
>
> WHAT WORKS:
> All of the workstations work correctly if plugged into the switch on
> the Linksys, they get assigned the correct ip/dns form the DHCP server
> running on the Win 2K3 box and can navigate the local network and the
> internet.
>
> PROBLEM:
> When I connect wirelessly with the laptop, I get a connection to the
> linksys (says strength Excellent), everything looks good, BUT ipconfig
> shows 0.0.0.0. I realize that I can only run 1 DHCP server on the
> network (at least I think that is the case), but why cant my laptop
> see the dhcp server?
>
> SIDE NOTE:
> I had this setup before without AD running dhcp and I was running DHCP
> on the Linksys router. The laptop worked perfectly then (actually
> everything worked correctly). Since I moved the DHCP service to the AD
> machine instead of running it on the router I have been out of luck
> wirelessly( as described above). I need DHCP running on the server
> because I want to mess with VPN on the Win 2K3 box and it will have to
> run DHCP so it can assign in comming clients an IP.
>
> Any suggestions would be great, I know this is not a new problem but I
> am not a network engineer, just a programmer who likes to tinker with
> networking.
>
> Thanks!
>
> Jeff