Archived from groups: alt.internet.wireless (
More info?)
On Fri, 29 Oct 2004 11:53:44 -0700, Jeff Liebermann
<jeffl@comix.santa-cruz.ca.us> wrote:
>On Fri, 29 Oct 2004 16:21:57 GMT, johnk@pceffect.co.uk (John F
>Kappler) wrote:
>
>>We have small WLAN with a D-Link DWL 2100AP and up to 9 clients with
>>DWL-G120 Adaptors.
>>
>>It all works fine during the day, but first thing in the morning, as
>>the clients come up, one of them wont be able to see the AP.
>>
>>The AP is powered on all the time, so as soon as the last person is
>>in, we power off and on the AP and then its all fine, and will run
>>happily all day, until the next morning (or someone comes in very
>>late!).
>>
>>There appears to be no pattern to which client will not find/be found
>>by the AP (Everyone gets a turn!). Its not even the same number of
>>clients each time.
>
>When you say "won't be able to see the AP", does that mean:
>1. The SSID is invisible in "scan for networks" or similar SSID
>display?
>2. The SSID is found, but the client cannot get a DHCP address?
>3. The SSID is found, the client has an existing DHCP address, but
>cannot see the rest of the router, rest of LAN, or internet?
>4. The AP has gone invisible and you can see right through it.
>
>If #4, there's a Nobel Prize waiting for you.
>
>>The AP is set with SSID not hidden, and a WEP key.
>>
>>D-Link support seem to think there's some sort of problem with the
>>2100, but cant pin it down,
>
>Please don't use pins. Voodoo is not supported by most access points.
>
>>and there's no firmware upgrade for this
>>device (as yet!).
>>
>>Anyone any suggestions as to possible other causes that are fixable?
>
>Yep. What's your DHCP lease time? See Advanced -> DHCP as in:
>http://support.dlink.com/techtool/dwl2100ap/emulator/html/dhcpdyna.html
>I'm not sure exactly what's happening with DHCP but my guess(tm) is
>that you either:
>1. Don't have enough DHCP assignable addresses for the 9 clients.
>2. Have too short a lease time so that the router expires the lease
>overnight. When the laptop arrives in the morning, it tries to get a
>new DHCP assigned IP address, and either fails, or keeps trying to use
>the old IP address.
>3. If the clients are laptops that were taken home and used on a
>different wireless access point, it may have the home configuration
>saved. I've dealt with belligerent XP SP1 machines that will not
>automatically release the old IP address. I have to resort to:
> ipconfig /release
> ipconfig /renew
>to force the client to let go of the old IP and ask for a new one.
>This is especially a problem if you put the laptop in standby (power
>save, hibernate, whatever) instead of doing a full shutdown.
>
>As I indicated, I'm not sure of the exact problem, but methinks it has
>to do with DHCP. I suggest a much longer lease time of 86,400 (one
>day) or larger.
>
>If that doesn't work, I suggest taking advantage of the static DHCP
>assignment feature, where you pre-assign an IP address to each client,
>without resorting to static IP's.
>http://support.dlink.com/techtool/dwl2100ap/emulator/html/dhcpstat.html?0,0,0,0,0,0,0
>This way the clients always get the same IP address. If they want to
>hold onto the old one, that's fine because it's the same as the new
>one.
>
>
>
>--
>Jeff Liebermann jeffl@comix.santa-cruz.ca.us
>150 Felker St #D
http://www.LearnByDestroying.com
>Santa Cruz CA 95060 AE6KS 831-336-2558
Aaaah, a Nobel prize...... (sorry,.a Homer moment!)
No. 1. Scan for Networks find nothing (despite other systems (e.g. on
the next desk) being happily connected). As I said, re-booting the AP
immediately solves the problem (does annoy the other users though!)
All clients have static IPs
Whilst it sometimes happens to Notebooks, it more regularly happens to
Desktops.
JohnK
Facebook
Twitter
Instagram