orinoco ap2000 dhcp server configuration

Here's a puzzle that I'd really appreciate some help with.

The following configuration from an AP-2000W web interface (latest
image file) allows a link to be established to a XP laptop with an
orinoco 802.11a/b/g card. However, the laptop cannot get a valid IP
address. Running XP Network Diagnostics gives a message of "DHCP
Server = 255.255.255.255(Invalid IP Address)".

"IP Configuation" tab:
IP Address Assignment Type Static
IP Address 166.122.72.2
Subnet Mask 255.255.255.192
Gateway IP Address 166.122.72.62

"DHCP Server" tab:
Enable DHCP Server checked
Subnet Mask 255.255.255.192 (software generated)
Gateway IP Address 10.0.1.1 (also tried 166.122.72.2)
Primary DNS IP Address 128.171.2.5
Secondary DNS IP Address 128.171.2.6
Number of IP Pool Table Entries 1 (software generated)

IP Pool Table
Start IP 10.0.1.2
End IP 10.0.1.100
Default Lease 86400
Maximum Lease 86400

The puzzle:
If the Gateway IP address is changed to 166.122.72.2 and the IP Pool
Talbe is changed to: Start IP 166.122.72.57 and End IP 166.122.72.61
the laptop happily picks up an address.

(E-Mail Removed) (Bill G) wrote:
> Here's a puzzle that I'd really appreciate some help with.
>
> The following configuration from an AP-2000W web interface (latest
> image file) allows a link to be established to a XP laptop with an
> orinoco 802.11a/b/g card. However, the laptop cannot get a valid IP
> address. Running XP Network Diagnostics gives a message of "DHCP
> Server = 255.255.255.255(Invalid IP Address)".
>
> "IP Configuation" tab:
> IP Address Assignment Type Static
> IP Address 166.122.72.2
> Subnet Mask 255.255.255.192
> Gateway IP Address 166.122.72.62
>
> "DHCP Server" tab:
> Enable DHCP Server checked
> Subnet Mask 255.255.255.192 (software generated)
> Gateway IP Address 10.0.1.1 (also tried 166.122.72.2)
> Primary DNS IP Address 128.171.2.5
> Secondary DNS IP Address 128.171.2.6
> Number of IP Pool Table Entries 1 (software generated)
>
> IP Pool Table
> Start IP 10.0.1.2
> End IP 10.0.1.100
> Default Lease 86400
> Maximum Lease 86400
>
> The puzzle:
> If the Gateway IP address is changed to 166.122.72.2 and the IP Pool
> Talbe is changed to: Start IP 166.122.72.57 and End IP 166.122.72.61
> the laptop happily picks up an address.

There are a number of things that could cause the problem.

The first thing is that your IP range and the subnetmask do not match.
With an subnetmask of 255.255.255.192 you can have a maximum of 64 IP
addresses minus the first and last. With this subnetmask your IP range
should look like 10.0.1.2 .. 10.0.1.62.
The other problem could be that the DHCP server wants to be in the same
subnet as the IP pool. So you should assign 10.0.1.2 to the AP and set
the range to 10.0.1.3 .. 10.0.1.62.

Hope this helps.

Kind regards,
Johan

Johan Willems <(E-Mail Removed)> wrote in message news:<Xns93ED57CECFFB4willemsprivate@194.109.133.2 9>...
> (E-Mail Removed) (Bill G) wrote:
> > Here's a puzzle that I'd really appreciate some help with.
> >
> > The following configuration from an AP-2000W web interface (latest
> > image file) allows a link to be established to a XP laptop with an
> > orinoco 802.11a/b/g card. However, the laptop cannot get a valid IP
> > address. Running XP Network Diagnostics gives a message of "DHCP
> > Server = 255.255.255.255(Invalid IP Address)".
> >
> > "IP Configuation" tab:
> > IP Address Assignment Type Static
> > IP Address 166.122.72.2
> > Subnet Mask 255.255.255.192
> > Gateway IP Address 166.122.72.62
> >
> > "DHCP Server" tab:
> > Enable DHCP Server checked
> > Subnet Mask 255.255.255.192 (software generated)
> > Gateway IP Address 10.0.1.1 (also tried 166.122.72.2)
> > Primary DNS IP Address 128.171.2.5
> > Secondary DNS IP Address 128.171.2.6
> > Number of IP Pool Table Entries 1 (software generated)
> >
> > IP Pool Table
> > Start IP 10.0.1.2
> > End IP 10.0.1.100
> > Default Lease 86400
> > Maximum Lease 86400
> >
> > The puzzle:
> > If the Gateway IP address is changed to 166.122.72.2 and the IP Pool
> > Talbe is changed to: Start IP 166.122.72.57 and End IP 166.122.72.61
> > the laptop happily picks up an address.
>
> There are a number of things that could cause the problem.
>
> The first thing is that your IP range and the subnetmask do not match.
> With an subnetmask of 255.255.255.192 you can have a maximum of 64 IP
> addresses minus the first and last. With this subnetmask your IP range
> should look like 10.0.1.2 .. 10.0.1.62.
> The other problem could be that the DHCP server wants to be in the same
> subnet as the IP pool. So you should assign 10.0.1.2 to the AP and set
> the range to 10.0.1.3 .. 10.0.1.62.
>
> Hope this helps.
>
> Kind regards,
> Johan

Thanks for the advice, but neither solution worked. Another piece to
the puzzle is that /var/log/messages says:
dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
dhclient: No DHCPOFFERS received.
(Redhat 9 with wlan module.) Any other ideas?