NTL BB: Need to register mac or not?

Hi All,

A question re the need to 'register' the mac address of a 'new' device
on an NTL (and other) cable (and possibly other, ADSL) .

Scenario:

PC working directly into a stand-alone cable modem, everything
working ok.

Replace PC with a router and see no DHCP from ISP (PC connects into
router ok).

So far the 'fix' has been one of these three:

1) Contact NTL broadband support and they "add the mac address of the
router to their table", and it all works within seconds (they mention
there can be several addresses in there).

2) Contact NTL broadband support and they say "change the mac address
of the router to that of the PC" and it all works within seconds (some
routers even have a 'clone mac address' feature) ?

3) Contact NTL broadband support and they say "we don't need to
register the mac address of the 'device', just the cable modem". In
spite of many power off (leave off) re-power cycles on the cable modem
and router it takes a while but eventually all works ok (a few mins
after the phone call?).

Anyone know what the real deal is here please (specifically re NTL and
stand-alone cable modems) ) or might it vary depending on the area?

All the best ..

T i m


T i m

What's the question.... ?

Guy
T i m wrote:
> Hi All,
>
> A question re the need to 'register' the mac address of a 'new' device
> on an NTL (and other) cable (and possibly other, ADSL) .
>
> Scenario:
>
> PC working directly into a stand-alone cable modem, everything
> working ok.
>
> Replace PC with a router and see no DHCP from ISP (PC connects into
> router ok).
>
> So far the 'fix' has been one of these three:
>
> 1) Contact NTL broadband support and they "add the mac address of the
> router to their table", and it all works within seconds (they mention
> there can be several addresses in there).
>
> 2) Contact NTL broadband support and they say "change the mac address
> of the router to that of the PC" and it all works within seconds (some
> routers even have a 'clone mac address' feature) ?
>
> 3) Contact NTL broadband support and they say "we don't need to
> register the mac address of the 'device', just the cable modem". In
> spite of many power off (leave off) re-power cycles on the cable modem
> and router it takes a while but eventually all works ok (a few mins
> after the phone call?).
>
> Anyone know what the real deal is here please (specifically re NTL and
> stand-alone cable modems) ) or might it vary depending on the area?
>
> All the best ..
>
> T i m

On Sat, 01 May 2004 11:22:07 GMT, "Bigguy"
<(E-Mail Removed)> wrote:


>T i m wrote:
>> Hi All,
>>
>> A question re the need to 'register' the mac address of a 'new' device
>> on an NTL (and other) cable (and possibly other, ADSL) .
>>
>> Scenario:
>>
>> PC working directly into a stand-alone cable modem, everything
>> working ok.
>>
>> Replace PC with a router and see no DHCP from ISP (PC connects into
>> router ok).
>>
>> So far the 'fix' has been one of these three:
>>
>> 1) Contact NTL broadband support and they "add the mac address of the
>> router to their table", and it all works within seconds (they mention
>> there can be several addresses in there).
>>
>> 2) Contact NTL broadband support and they say "change the mac address
>> of the router to that of the PC" and it all works within seconds (some
>> routers even have a 'clone mac address' feature) ?
>>
>> 3) Contact NTL broadband support and they say "we don't need to
>> register the mac address of the 'device', just the cable modem". In
>> spite of many power off (leave off) re-power cycles on the cable modem
>> and router it takes a while but eventually all works ok (a few mins
>> after the phone call?).
>>
>> Anyone know what the real deal is here please (specifically re NTL and
>> stand-alone cable modems) ) or might it vary depending on the area?
>>
>> All the best ..
>>
>> T i m


>
>What's the question.... ?
>
>Guy


Hi Guy ..

Erm > "Anyone know what the real deal is here please (specifically re
NTL and stand-alone cable modems) ) or might it vary depending on the
area?"

(With ref the above)

All the best

T i m

On Sat, 01 May 2004 08:08:19 +0100 and in article
<(E-Mail Removed)>, T i m said...
: Hi All,
:
: A question re the need to 'register' the mac address of a 'new' device
: on an NTL (and other) cable (and possibly other, ADSL) .

Right..

: Scenario:
:
: PC working directly into a stand-alone cable modem, everything
: working ok.

Ok.

: Replace PC with a router and see no DHCP from ISP (PC connects into
: router ok).

Right. Turn off the modem. Turn it back on, then when it's synched and
ready connect the (powered off) router to the modem. Turn the router
on. Give it a min or two and it should be in business.

: So far the 'fix' has been one of these three:
:
: 1) Contact NTL broadband support and they "add the mac address of the
: router to their table", and it all works within seconds (they mention
: there can be several addresses in there).

A maximum of 3 iirc.

: 2) Contact NTL broadband support and they say "change the mac address
: of the router to that of the PC" and it all works within seconds (some
: routers even have a 'clone mac address' feature) ?

You don't need to do this, not for a good few years on NTL at any rate.
But if it works for you then fine.

: 3) Contact NTL broadband support and they say "we don't need to
: register the mac address of the 'device', just the cable modem".

Correct. However, you already did that when you registered your service
with NTL for the cablemodem.

: Anyone know what the real deal is here please (specifically re NTL and
: stand-alone cable modems) ) or might it vary depending on the area?

Erm, well NTL haven't told you any lies. In fact, the tech support @
NTL is pretty good ime. Can you still not get the router working with
the modem?

What *exact* problems are you having? Your post is a little lacking in a
question..

--
chris

On Sat, 01 May 2004 18:34:07 +0100 and in article
<(E-Mail Removed)>, T i m said...
: Erm > "Anyone know what the real deal is here please (specifically re
: NTL and stand-alone cable modems) ) or might it vary depending on the
: area?"
:
Still doesn't make much sense as all three scenarios are valid and will
work.
--
chris

On Sat, 1 May 2004 21:49:13 +0100, chris <(E-Mail Removed)> wrote:

>
>What *exact* problems are you having? Your post is a little lacking in a
>question..

Hi Chris , these *were* problems, seemingly 'resolved' by differing
methods and different suggestions from NTL c/s?

One NTL support guy said "change the mac address of the router to that
of the PC that was directly connected" (and it then worked straight
away).

Another re a similar problem (no DHCP on Wan port) said "give me the
mac address of the router" .. we did, then it worked where it hadn't
for 30 mins before?

I'm aware Blueyonder, NTL 'Set top Box' and BT type ADSL modem /
routers need pre registration, but you are suggesting (saying) the
NTL cable modem users don't?

I'll go along with that but it seems to contradict at least two NTL
c/s folk (who I'll agree are pretty switched on) and my own recent
experiences?

All the best ...

Confused T i m ;-)

On Sun, 02 May 2004 00:14:15 +0100 and in article
<(E-Mail Removed)>, T i m said...
: I'm aware Blueyonder, NTL 'Set top Box' and BT type ADSL modem /
: routers need pre registration, but you are suggesting (saying) the
: NTL cable modem users don't?
:
:
That is not remotely what I am saying. What makes you think I am?

Look:
[..]
': 3) Contact NTL broadband support and they say "we don't need to
: register the mac address of the 'device', just the cable modem".

Correct. However, you already did that when you registered your service
with NTL for the cablemodem.'
[..]

Which means NTL dont need to register your cable modem MAC address as
you already did that when you originally had the serviced installed !
--
chris

On Sun, 2 May 2004 01:38:00 +0100, chris <(E-Mail Removed)> wrote:

>On Sun, 02 May 2004 00:14:15 +0100 and in article
><(E-Mail Removed)>, T i m said...
>: I'm aware Blueyonder, NTL 'Set top Box' and BT type ADSL modem /
>: routers need pre registration, but you are suggesting (saying) the
>: NTL cable modem users don't?
>:
>:
>That is not remotely what I am saying. What makes you think I am?

Sri Chris, I wasn't trying to suggest for one moment you were saying
*anything* (it was just a turn of phrase) I was just trying to get
clear in my mind when registration is needed and when it isn't?
>
>Look:
>[..]
>': 3) Contact NTL broadband support and they say "we don't need to
>: register the mac address of the 'device', just the cable modem".
>
>Correct. However, you already did that when you registered your service
>with NTL for the cablemodem.'

Ok. What I do understand is that when you sign up for NTLWorld cable
modem broadband you either stick the CD in they give you (or go in via
the back door) and sign up through their registration server. At that
point it collects the mac address of the cable modem.

As you say here ..
>[..]
>
>Which means NTL dont need to register your cable modem MAC address as
>you already did that when you originally had the serviced installed !

But. can you explain when with at least two instances I am aware of,
some months after the install a user went from say a PC > Cable modem
to PC > router > cable modem and it didn't work (got no i/p stuff from
NTL). In both cases a call to NTL support had them suggesting
solutions that involved the mac addrress of the ROUTER?

1) If this step isn't needed why did *they* suggest it?

2) If it wasn't needed why didn't it work before we spoke to them but
did afterwards (when they added a mac address to the 'table' and we
changed the mac add in the router to that of the pc that had been
connected for months).?

And before I confuse you I'm not saying that I know you do *need* to
register the router mac, I'm just asking what may of been going on
here to make it look that way?

Sorry I don't seem to have put it across very well Chris. I'm not much
into the theory behind it all (never could get excited by the "OSI 7
Layer model" but I generally get it all working in the end) ;-)

All the best and thanks for your time

T i m

"T i m" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi All,
>
> A question re the need to 'register' the mac address of a 'new' device
> on an NTL (and other) cable (and possibly other, ADSL) .
>
> Scenario:
>
> PC working directly into a stand-alone cable modem, everything
> working ok.
>
> Replace PC with a router and see no DHCP from ISP (PC connects into
> router ok).

DHCP is triggered by the device requesting an address or a renewal - and
maybe the cable modem ignores different MAC addresses unless the old lease
has expired / been released, since you are only allowed 1 IP address at a
time.
>
> So far the 'fix' has been one of these three:
>
> 1) Contact NTL broadband support and they "add the mac address of the
> router to their table", and it all works within seconds (they mention
> there can be several addresses in there).
>
> 2) Contact NTL broadband support and they say "change the mac address
> of the router to that of the PC" and it all works within seconds (some
> routers even have a 'clone mac address' feature) ?

never needed this - on a set top box power cycle fixes it, and i would try
that 1st with a cable modem.
>
> 3) Contact NTL broadband support and they say "we don't need to
> register the mac address of the 'device', just the cable modem". In
> spite of many power off (leave off) re-power cycles on the cable modem
> and router it takes a while but eventually all works ok (a few mins
> after the phone call?).
>
> Anyone know what the real deal is here please (specifically re NTL and
> stand-alone cable modems) ) or might it vary depending on the area?

it does. Also depends on whether you have a set top box or a cable modem.

Try this site for the details: -- http://www.chetnet.co.uk/

>
> All the best ..
>
> T i m
--
Regards

Stephen Hope - return address needs fewer xxs

On Sun, 2 May 2004 10:21:50 +0100, "shope"
<(E-Mail Removed)> wrote:


>> PC working directly into a stand-alone cable modem, everything
>> working ok.
>>
>> Replace PC with a router and see no DHCP from ISP (PC connects into
>> router ok).
>
>DHCP is triggered by the device requesting an address or a renewal - and
>maybe the cable modem ignores different MAC addresses unless the old lease
>has expired / been released, since you are only allowed 1 IP address at a
>time.

Hi Stephen. This was what I was wondering. But I'm not sure the cable
modem would get involved with such things would it?
>>
>> So far the 'fix' has been one of these three:
>>
>> 1) Contact NTL broadband support and they "add the mac address of the
>> router to their table", and it all works within seconds (they mention
>> there can be several addresses in there).
>>
>> 2) Contact NTL broadband support and they say "change the mac address
>> of the router to that of the PC" and it all works within seconds (some
>> routers even have a 'clone mac address' feature) ?
>
>never needed this - on a set top box power cycle fixes it, and i would try
>that 1st with a cable modem.

I believe that is the case with a STB and helped a mate get onto NTL
(ex C&W customer) with one by doing so.
>>
>> 3) Contact NTL broadband support and they say "we don't need to
>> register the mac address of the 'device', just the cable modem". In
>> spite of many power off (leave off) re-power cycles on the cable modem
>> and router it takes a while but eventually all works ok (a few mins
>> after the phone call?).
>>
>> Anyone know what the real deal is here please (specifically re NTL and
>> stand-alone cable modems) ) or might it vary depending on the area?
>
>it does. Also depends on whether you have a set top box or a cable modem.

Apart from the case mentioned above they have all been cable modems?
In all cases the CM / Router / PC were left off for some time (5
mins?) and re-connected (and allowed to 'settle down') but with the
same results. Warmstarting the router would initiate a DHCP cycle but
no reply? Have the mac added to the 'table' or re assign the mac of
the PC to the router and away it goes? Very strange then?
>
>Try this site for the details: -- http://www.chetnet.co.uk/

Thanks for that .. I might run it past Chet and see what he says ..?
;-)

All the best ..

T i m