Re: Multiple Wireless Access Points



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" <jeffl@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1lv1h192t3qg22tie2vb8qocuopll0l560@xxxxxxxxxx
> On Sat, 27 Aug 2005 14:46:02 GMT, "Joe DiGiovanni"
> <mrcpuhead@xxxxxxxxx> 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
> # jeffl@xxxxxxxxxxxxxxxxxxxxxx
> # jeffl@xxxxxxxxxx AE6KS


.



Relevant Pages

  • [RFC PATCH 2/2] dmaengine: move channel management to the client
    ... to a specific client. ... a channel at dma_event_callback time. ... struct dma_device *device; ... * When the number of DMA channel in the system changes, ...
    (Linux-Kernel)
  • RE: Problems with security requirements in Windows WorkGroups.
    ... "A remote side security requirement was not fulfilled during authentication. ... small chat application between a client and a server ... When I try to use the TCP channel I get the error (with NO inner exception ...
    (microsoft.public.dotnet.languages.csharp)
  • [md-accel PATCH 02/19] dmaengine: make clients responsible for managing channels
    ... The current implementation assumes that a channel will only be used by one ... Instead of tracking how many channels a client wants and how many it has ... struct dma_device *device; ... * When the number of DMA channel in the system changes, ...
    (Linux-Kernel)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: .Net Remoting TCP or HTTP?
    ... John's given a good description of why you would pick either the TCP or HTTP ... The reason is that, when the server needs to notify the client of the event, ... In the TCP case, this means using a bi-directional channel, so that requests ...
    (microsoft.public.dotnet.framework)