The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: ex2000 sever and aol


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [OTish] NTL Broadband - Help needed please.


  • To: <ukha_d@xxxxxxx>
  • Subject: RE: [OTish] NTL Broadband - Help needed please.
  • From: "Keith Doxey" <ukha@xxxxxxx>
  • Date: Sun, 12 Jan 2003 19:19:31 -0000
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

Hi Alan,

I am also not familiar with NTL for fairly obvious reasons :-)

I was hoping that as it was ethernet presented it was a router of sorts :-(

Will have to try and find out a bit more. Thanks.

Keith

www.diyha.co.uk
www.kat5.tv


-----Original Message-----
From: HA [mailto:ha@xxxxxxx]
Sent: 12 January 2003 19:10
To: ukha_d@xxxxxxx Subject: Re: [ukha_d] [OTish] NTL Broadband - Help needed please.


I'm not familiar with the NTL setup but would have thought the STB
would just be a modem which would suggest that you need some sort of
router rather than plugging it straight in to a switch.

Alan Shields

On Sunday, January 12, 2003, at 07:03  pm, Keith Doxey wrote:

> Hi All,
>
> Just been round to my father-in-laws house to help him get his PC's
> connected to NTL Broadband.
>
> He already had one PC up and running after the NTL engineer had put
> sockets
> on the end of his CAT5 cable for him.
>
> The instructions he was left for getting his other PC on Broadband
> were to
> disconnect his main PC, but the NTL disk in the second computer and go
> through the setup procedure again which involves rebooting the set top
> box
> ( a PACE).
>
> After doing this the second computer his second computer was on the
> net at
> super fast speed and had been allocated an IP address of xxx.xxx.xxx.42
>
> The address previously given to his othe r PC was xxx.xxx.xxx.72 but
> the
> same subnet.
>
> After reconnecting his main PC, it failed to be allocated a DHCP
> address by
> the set top box and WinXP ggave it a 169.x.x.x address.
>
> The only way to get his main PC back on the net was to diconnect the
> other
> PC and then reboot the main PC and set top box. It now had its
> original IP
> of xxx.xxx.xxx.72 and worked a treat.
>
> Reconnected the second PC and it failed to be allocated an IP address.
>
> The setup  is like this.....
>
> PACE STB ____10baseT____10/100Switch ______100baseT _____MAIN PC
>                                                   
> _____________100baseT
> _____Second PC
>
> The normal Network Icon doesnt show in the system tray, instead there
> is an
> icon for NTL Connect.
>
> I know several of you have NTL and have multiple PC's working over it
> so
> what have I done wrong?
>
> Thanks
>
>
> Keith
>
> www.diyha.co.uk
> www.kat5.tv
>
>
> http://www.automatedhome.co.uk
> Post message: ukha_d@xxxxxxx > Subscribe:  ukha_d-subscribe@xxxxxxx > Unsubscribe:  ukha_d-unsubscribe@xxxxxxx > List owner:  ukha_d-owner@xxxxxxx >
> List of UKHA Groups here -
> http://groups.yahoo.com/group/UKHA_Grouplists/
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>


http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/


Yahoo! Groups Sponsor
ADVERTISEMENT

http://www.automatedhome.co.uk
Post message: ukha_d@xxxxxxx
Subscribe:  ukha_d-subscribe@xxxxxxx
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx
List owner:  ukha_d-owner@xxxxxxx
List of UKHA Groups here - http://groups.yahoo.com/group/UKHA_Grouplists/


Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.