Help: NTL cable modem + Netgear WAP.

Hi,

Another seasonal cry for help! I've got:

NTL broadband cable modem
ethernetted to
Netgear ME102 WAP
WLAN to
PC running XP. (Less than a metre from the WAP.)

Won't work - times out during "acquiring IP address" which I believe means
it hasn't got past the DHCP stage. I've tried turning the 3 boxes off and
on, with delays, in all possible different orders. Occasionally, it
connects for a few minutes then destabilises and goes back to "acquiring IP
address", then failure. Just once it connected perfectly and stayed
stable for hours but I've never been able to repeat that single success.

Anybody got any suggestions? The same PC and Netgear WAP works in a
different setup with a DSL broadband modem. And the NTL broadband modem
works perfectly when Ethernetted directly to my PC - but not with my Netgear
WAP in between!

Tx,

"news outlook" <(E-Mail Removed)> wrote in message
news:mDckh.23593$(E-Mail Removed)...
> Hi,
>
> Another seasonal cry for help! I've got:
>
> NTL broadband cable modem
> ethernetted to
> Netgear ME102 WAP
> WLAN to
> PC running XP. (Less than a metre from the WAP.)
>
> Won't work - times out during "acquiring IP address" which I believe means
> it hasn't got past the DHCP stage. I've tried turning the 3 boxes off and
> on, with delays, in all possible different orders. Occasionally, it
> connects for a few minutes then destabilises and goes back to "acquiring
> IP address", then failure. Just once it connected perfectly and stayed
> stable for hours but I've never been able to repeat that single success.
>
> Anybody got any suggestions? The same PC and Netgear WAP works in a
> different setup with a DSL broadband modem. And the NTL broadband modem
> works perfectly when Ethernetted directly to my PC - but not with my
> Netgear WAP in between!
>
> Tx,
>
>
>
>
go to www.chetnet.co.uk and select forum, the people that run it work for
NTL.

"news outlook" <(E-Mail Removed)> wrote in message
news:mDckh.23593$(E-Mail Removed)...
> Hi,
>
> Another seasonal cry for help! I've got:
>
> NTL broadband cable modem
> ethernetted to
> Netgear ME102 WAP
> WLAN to
> PC running XP. (Less than a metre from the WAP.)
>
> Won't work - times out during "acquiring IP address" which I believe means
> it hasn't got past the DHCP stage. I've tried turning the 3 boxes off and
> on, with delays, in all possible different orders. Occasionally, it
> connects for a few minutes then destabilises and goes back to "acquiring
> IP address", then failure. Just once it connected perfectly and stayed
> stable for hours but I've never been able to repeat that single success.
>
> Anybody got any suggestions? The same PC and Netgear WAP works in a
> different setup with a DSL broadband modem. And the NTL broadband modem
> works perfectly when Ethernetted directly to my PC - but not with my
> Netgear WAP in between!

That would be because the WAP does a DHCP request for an IP address for its
management interface.
It gets this from NTL.. unfortunately NTL only let you have one address so
the PC fails to get one.

It will work if you assign a static address to the WAP for its management..
just use something like 192.168.0.10.

"dennis@home" <(E-Mail Removed)> wrote in message
news:4591b193$0$2698$(E-Mail Removed)...
>
> "news outlook" <(E-Mail Removed)> wrote in message
> news:mDckh.23593$(E-Mail Removed)...
>> Hi,
>>
>> Another seasonal cry for help! I've got:
>>
>> NTL broadband cable modem
>> ethernetted to
>> Netgear ME102 WAP
>> WLAN to
>> PC running XP. (Less than a metre from the WAP.)
>>
>> Won't work - times out during "acquiring IP address" which I believe
>> means (cut)

>
> That would be because the WAP does a DHCP request for an IP address for
> its management interface.
> It gets this from NTL.. unfortunately NTL only let you have one address so
> the PC fails to get one.
>
> It will work if you assign a static address to the WAP for its
> management.. just use something like 192.168.0.10.
>

Many thanks, Dennis, that did the job. I unchecked a tick-box labelled
"Enable DHCP Client" on the Netgear ME102. It seems this refers to the
management interface though it was not described as such. This activated an
IP address 192.168.100.10 on that interface meaning that the WAP didn't need
to go looking for a second DHCP-assigned addressed, as you said. I also
unchecked a tick-box labelled "Enable SNMP Trap Messages" though I don't
know if that had any practical effect.

Thanks again, and happy new year!