Netgear ME102 problem

Hi,
I'm having trouble with the DHCP server of this access point. I've
only one machine to test the connection. It's running W98 SE with a
Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
physical connection establishes fine, but the windows box cannot get
its configuration by DHCP, and ends up with an IP of 169.254.131.154,
netmask 255.255.0.0, and no gateway. Quite embarassing...
Unfortunately, the AP configuration tools have no item about
activating/deactivating the DHCP server ; it remains always on.
Have someone ever experienced something similar ? Thanks in advance
for helping.

Olivier

I haven't used my ME102 in almost a year (just bought an ME103) but I
seem to recall a similar problem with it involving DHCP from the WAP's
perspective. I *believe* the issue was fixed in a firmware/software
upgrade. I think I ended up disabling this feature and assigning a
static IP adx on my lappy. Are you using the latest firmware AND
software? Check Netgear's website:
http://www.netgear.com/support/suppo...asp?dnldID=323

The one pet peeve I have about the ME102 is the funky/clunky user
interface (part web-based and part USB) for configuration. I believe you
have to access the AP via USB in order to gain access to all of the
configuration features (if accessing over ethernet, you're not able to
access some of the configuration features, if I remember correctly).
Make sure that you are accessing your AP via USB for any
setup/configurations tasks...

They've really come a long way with the ME103 as far as
configuration/setup access (all web-based and slick as ever!!!). Can't
wait to actually test it out!

Larry

Olivier wrote:
> Hi,
> I'm having trouble with the DHCP server of this access point. I've
> only one machine to test the connection. It's running W98 SE with a
> Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
> physical connection establishes fine, but the windows box cannot get
> its configuration by DHCP, and ends up with an IP of 169.254.131.154,
> netmask 255.255.0.0, and no gateway. Quite embarassing...
> Unfortunately, the AP configuration tools have no item about
> activating/deactivating the DHCP server ; it remains always on.
> Have someone ever experienced something similar ? Thanks in advance
> for helping.
>
> Olivier

Olivier wrote:
> Hi,
> I'm having trouble with the DHCP server of this access point. I've
> only one machine to test the connection. It's running W98 SE with a
> Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
> physical connection establishes fine, but the windows box cannot get
> its configuration by DHCP, and ends up with an IP of 169.254.131.154,
> netmask 255.255.0.0, and no gateway. Quite embarassing...
> Unfortunately, the AP configuration tools have no item about
> activating/deactivating the DHCP server ; it remains always on.
> Have someone ever experienced something similar ? Thanks in advance
> for helping.
>
> Olivier
Are you sure the ME102 has a DHCP server? Mine gets its own IP from the
router and passes DHCP requests to/from the router to the client.

Larry <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> I haven't used my ME102 in almost a year (just bought an ME103) but I
> seem to recall a similar problem with it involving DHCP from the WAP's
> perspective. I *believe* the issue was fixed in a firmware/software
> upgrade. I think I ended up disabling this feature and assigning a
> static IP adx on my lappy.
How can you do that ? I'd have done it already, if I knew how...
There's
>Are you using the latest firmware AND
> software? Check Netgear's website:
> http://www.netgear.com/support/suppo...asp?dnldID=323

My ME102 is a revision B one, so there's no upgrading firmware
avalaible.
(My version : 2.0.1.16)

> The one pet peeve I have about the ME102 is the funky/clunky user
> interface (part web-based and part USB) for configuration. I believe you
> have to access the AP via USB in order to gain access to all of the
> configuration features (if accessing over ethernet, you're not able to
> access some of the configuration features, if I remember correctly).

Actually, there are two configuration interfaces, one by the USB cord,
and another via SNMP. And the MAC address restricting feature is
missing in the USB config tool. But I can't find any DHCP-related item
in any of the two.

> They've really come a long way with the ME103 as far as
> configuration/setup access (all web-based and slick as ever!!!). Can't
> wait to actually test it out!

Don't make me cry I juste purchased my ME102 used !
Olivier

On 1/8/2004 6:54 PM, Olivier wrote:

> Hi,
> I'm having trouble with the DHCP server of this access point. I've
> only one machine to test the connection. It's running W98 SE with a
> Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
> physical connection establishes fine, but the windows box cannot get
> its configuration by DHCP, and ends up with an IP of 169.254.131.154,
> netmask 255.255.0.0, and no gateway. Quite embarassing...
> Unfortunately, the AP configuration tools have no item about
> activating/deactivating the DHCP server ; it remains always on.
> Have someone ever experienced something similar ? Thanks in advance
> for helping.
>
> Olivier

It is getting the Internet address of your broadband modem. APs don't
DHCP servers. That's the function of a router/switch.

Jerry Park <(E-Mail Removed)> wrote in message news:<YjALb.6411$(E-Mail Removed)>. ..
> Olivier wrote:
> > Hi,
> > I'm having trouble with the DHCP server of this access point. I've
> > only one machine to test the connection. It's running W98 SE with a
> > Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
> > physical connection establishes fine, but the windows box cannot get
> > its configuration by DHCP, and ends up with an IP of 169.254.131.154,
> > netmask 255.255.0.0, and no gateway. Quite embarassing...
> > Unfortunately, the AP configuration tools have no item about
> > activating/deactivating the DHCP server ; it remains always on.
> > Have someone ever experienced something similar ? Thanks in advance
> > for helping.
> >
> > Olivier
> Are you sure the ME102 has a DHCP server? Mine gets its own IP from the
> router and passes DHCP requests to/from the router to the client.

It seems so because :
1. The doc says it has. (Although the revision A of the ME102 seems
not to have one.)
2. The doc says that the AP does NAT on the wireless stations.
2. A tcpdump of my router's interface connected to the AP dumps no
packet when the wireless client comes up.

Olivier

Dan <(E-Mail Removed)> wrote in message news:<jhMLb.30769$(E-Mail Removed)>...
> On 1/8/2004 6:54 PM, Olivier wrote:
>
> > Hi,
> > I'm having trouble with the DHCP server of this access point. I've
> > only one machine to test the connection. It's running W98 SE with a
> > Peabird WL-PCI adapter (chipset RalinkTech RT2400, 802.11b). So the
> > physical connection establishes fine, but the windows box cannot get
> > its configuration by DHCP, and ends up with an IP of 169.254.131.154,
> > netmask 255.255.0.0, and no gateway. Quite embarassing...
> > Unfortunately, the AP configuration tools have no item about
> > activating/deactivating the DHCP server ; it remains always on.
> > Have someone ever experienced something similar ? Thanks in advance
> > for helping.
> >
> > Olivier
>
> It is getting the Internet address of your broadband modem. APs don't
> DHCP servers. That's the function of a router/switch.

Mine does, and does NAT too. At least in the doc...
Olivier