[drewgraham]

Hey all,

I'm trying to expand a network that connects through a ntl cable modem.

I'm trying to add a ZyXEL router (Prestige 334) to a NTL Home 120 cable mode, but the router won't pick up an ip address.

When I connect directly to the router, it gives me an address in the 80.6.5.x range, although the default gateway is 80.6.4.1 (in a different subnet), on a 255.255.252.0 subnet mask. The router's config page is on 192.168.100.1!?

I've tried straight through and crossover cables (I can connect directly with either), tried specifying an ip address for the wan port (it wouldn't let me as the ip and the gateway were on different subnets, as above).

Will the router not pick up an IP address because the gateway and dhcp subnet are different?

[drewgraham]

Or, could it be an authentication issue?

What method, if any, does ntl use? Is it MAC address, host name, or a username and password?

[JohnWill]

The symptoms are that you have your cable modem connected to one of the LAN/Network ports, try connecting it to the WAN/Internet port.

[drewgraham]

Originally Posted by JohnWill

The symptoms are that you have your cable modem connected to one of the LAN/Network ports, try connecting it to the WAN/Internet port.

He he - no, it's definitely connected to the WAN port.

[TerryNet]

Maybe my binary is too rusty, but with 255.255.252.0 subnet mask 80.6.5..anything and 80.6.4.anything seem to be in the same subnet. And they are public IP addresses so no normal router's Dhcp server is going to assign any of those.

It's not impossible for 192.168.100.1 to be a router's default LAN address, but seems unusual to me. That happens to be my modem's address.

The User Guide for that router claims 192.168.1.1 to be its default LAN address.

[drewgraham]

Originally Posted by TerryNet

Maybe my binary is too rusty, but with 255.255.252.0 subnet mask 80.6.5..anything and 80.6.4.anything seem to be in the same subnet. And they are public IP addresses so no normal router's Dhcp server is going to assign any of those.

It's not impossible for 192.168.100.1 to be a router's default LAN address, but seems unusual to me. That happens to be my modem's address.

The User Guide for that router claims 192.168.1.1 to be its default LAN address.

I've got to the bottom of the 192.168.100.1 malarkey - it's not its actually IP address but it sniffs http traffic for requests to that address and intercepts them.

My binary is non existent, so if you say it adds up, it adds up.

But I still can't figure out why I can get an ip address (and a public ip address at that) through the modem to any computer, but the router can't.

[TerryNet]

You SHOULD get a public IP address when connected directly to the modem. Since your earlier posts were saying you got that address when connected to the router, maybe it would be best if you stated your problem again.

Oh, and if you forgot to power cycle the modem when switching to the router, that is the reason that the router did not get an IP configuration.