Multiple Wireless Access Points

I'm trying to configure multiple WAPs connected to an existing LAN. I want
to have all wireless clients get their IP config from the LAN's Windows 2000
Server (which provides DHCP and DNS server services). What is the best way
to configure the WAPs?

wap gateway = LAN ip
wap 1st dns = LAN ip
wap 2nd dns = win2000 Server real www 2nd dns ip

wap ip = fixed ip

"Joe DiGiovanni" <(E-Mail Removed)> wrote in message
news:uiRPe.2804$(E-Mail Removed) t...
> I'm trying to configure multiple WAPs connected to an existing LAN. I
> want to have all wireless clients get their IP config from the LAN's
> Windows 2000 Server (which provides DHCP and DNS server services). What
> is the best way to configure the WAPs?
>

> I'm trying to configure multiple WAPs connected to an existing LAN. I want
> to have all wireless clients get their IP config from the LAN's Windows 2000
> Server (which provides DHCP and DNS server services). What is the best way
> to configure the WAPs?

Just turn them on, they're a layer 2 bridge so don't care anything about
dhcp or dns.

You don't say how many you're trying to configure or whether you want
roaming or whether they're overlapping.

If you want to roam, configure the same SSID and use channels 1, 6, 11
in a non overlapping fashion.

If you don't want to roam or they don't overlap it doesn't matter.

The access points only need an address for management or communications
with say a RADIUS server but you didn't mention that either so i'll
presume you don't.

David.

> wap gateway = LAN ip
> wap 1st dns = LAN ip
> wap 2nd dns = win2000 Server real www 2nd dns ip

You've lost me there! Do what? Why? The OP mentions access point, not
router so there's no forwarding, no lookups, no routing, no NAT.

> wap ip = fixed ip

For management yes although he could do a DHCP reservation since DHCP is
already present but same effect.

David.

I take it by "LAN ip" you mean the Win2K Server's IP addr, since it is the
DNS server?

"bumtracks" <(E-Mail Removed)> wrote in message
news:CfUPe.1253$__1.850@trnddc07...
> wap gateway = LAN ip
> wap 1st dns = LAN ip
> wap 2nd dns = win2000 Server real www 2nd dns ip
>
> wap ip = fixed ip
>
> "Joe DiGiovanni" <(E-Mail Removed)> wrote in message
> news:uiRPe.2804$(E-Mail Removed) t...
>> I'm trying to configure multiple WAPs connected to an existing LAN. I
>> want to have all wireless clients get their IP config from the LAN's
>> Windows 2000 Server (which provides DHCP and DNS server services). What
>> is the best way to configure the WAPs?
>>
>
>

There are 3 WAPs, and they can provide DHCP services. The rooms are close
enough that they all overlap. I do want roaming.

So, it sounds like: same SSID, but unique channels, right?

"David Taylor" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) d.com...
>> I'm trying to configure multiple WAPs connected to an existing LAN. I
>> want
>> to have all wireless clients get their IP config from the LAN's Windows
>> 2000
>> Server (which provides DHCP and DNS server services). What is the best
>> way
>> to configure the WAPs?
>
> Just turn them on, they're a layer 2 bridge so don't care anything about
> dhcp or dns.
>
> You don't say how many you're trying to configure or whether you want
> roaming or whether they're overlapping.
>
> If you want to roam, configure the same SSID and use channels 1, 6, 11
> in a non overlapping fashion.
>
> If you don't want to roam or they don't overlap it doesn't matter.
>
> The access points only need an address for management or communications
> with say a RADIUS server but you didn't mention that either so i'll
> presume you don't.
>
> David.

"Joe DiGiovanni" <(E-Mail Removed)> wrote:
>There are 3 WAPs, and they can provide DHCP services. The rooms are close
>enough that they all overlap. I do want roaming.
>
>So, it sounds like: same SSID, but unique channels, right?

What WAPs do you have that provide DHCP services? I don't think you
are going to be able to provide seamless roaming(*) thru multiple DHCP
servers...

(*) Look for a recent thread on WAP54G roaming for discussions of
roaming, and why it might not work no matter what you do.

Thanks - indeed I don't want to use the WAP/routers' DHCP services at all.
From your other post, looks like I need to use same channel on all 3 to have
seamless roaming, right? The WEP keys already match (don't think the
devices support WPA - I'm not in front of them to check).


<William P. N. Smith> wrote in message
news:(E-Mail Removed)...
> "Joe DiGiovanni" <(E-Mail Removed)> wrote:
>>There are 3 WAPs, and they can provide DHCP services. The rooms are close
>>enough that they all overlap. I do want roaming.
>>
>>So, it sounds like: same SSID, but unique channels, right?
>
> What WAPs do you have that provide DHCP services? I don't think you
> are going to be able to provide seamless roaming(*) thru multiple DHCP
> servers...
>
> (*) Look for a recent thread on WAP54G roaming for discussions of
> roaming, and why it might not work no matter what you do.

On Sat, 27 Aug 2005 14:46:02 GMT, "Joe DiGiovanni"
<(E-Mail Removed)> wrote:

>Thanks - indeed I don't want to use the WAP/routers' DHCP services at all.
>From your other post, looks like I need to use same channel on all 3 to have
>seamless roaming, right? The WEP keys already match (don't think the
>devices support WPA - I'm not in front of them to check).

No. They can and should be on different non-overlapping channels (1,
6, and 11) but all the same SSID. If they were on the same channel,
and they had overlapping coverage, then they will interfere with each
other. The way it works is that a client radio holds onto a give
access point and channel until it loses signal. It then scans all the
channels (1->11) looking for the same SSID. Some clients are smart
enough to take the strongest (or lowest S/N ratio) channel. Others
are stupid and just take the first channel they blunder across. If
you have overlapping coverage areas, you can see where there might be
a problem.

Otherwise, wait for the IEEE to release 802.11r (fast roaming) which
should work much better.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice http://www.LearnByDestroying.com
# http://802.11junk.com
# (E-Mail Removed)
# (E-Mail Removed) AE6KS

Thanks! I found the WAP can be either configured strictly as an access
point, or as a router. Either way, when I configure it w/ an IP address in
the same subnet as the LAN wired computers, including the Win2K server, I
can connect to the WAP from a wireless client, but the client doesn't get
it's IP from the Win2K DHCP server. Instead, it gets an autoconfig-type
address.

The WAP, when just an access point, only allows me to specify the IP and
subnet mask. When router functions are enabled, I can set WAN IP settings,
including IP addr, subnet mask, DNS server addr.

The Win2K server is 192.168.0.3. The default gateway is 192.168.0.1. The
WAP is 192.168.0.5, and it's DHCP server capability is disabled. The WAP's
DNS is set to 192.168.0.3.

Any ideas why the client isn't getting through to the Win2K DHCP server?

"Jeff Liebermann" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Sat, 27 Aug 2005 14:46:02 GMT, "Joe DiGiovanni"
> <(E-Mail Removed)> wrote:
>
>>Thanks - indeed I don't want to use the WAP/routers' DHCP services at all.
>>From your other post, looks like I need to use same channel on all 3 to
>>have
>>seamless roaming, right? The WEP keys already match (don't think the
>>devices support WPA - I'm not in front of them to check).
>
> No. They can and should be on different non-overlapping channels (1,
> 6, and 11) but all the same SSID. If they were on the same channel,
> and they had overlapping coverage, then they will interfere with each
> other. The way it works is that a client radio holds onto a give
> access point and channel until it loses signal. It then scans all the
> channels (1->11) looking for the same SSID. Some clients are smart
> enough to take the strongest (or lowest S/N ratio) channel. Others
> are stupid and just take the first channel they blunder across. If
> you have overlapping coverage areas, you can see where there might be
> a problem.
>
> Otherwise, wait for the IEEE to release 802.11r (fast roaming) which
> should work much better.
>
>
> --
> # Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
> # 831.336.2558 voice http://www.LearnByDestroying.com
> # http://802.11junk.com
> # (E-Mail Removed)
> # (E-Mail Removed) AE6KS