Quote:
|
Originally Posted by Rob C
Main reason for lack of preference for USB is that it relies on hardware (CPU) and other resources in your PC, rather than dedicated functionality of the ethernet card.
If your ethernet card works locally, then there is no reason why you should not be able to use it connected to the STB. Make sure you fully power down the PC and STB (unplug the STB from the wall), connect the wires then switch on.
You should now be able to browse. If not, go to internet explorer (or other browser) and type in the address box "start:ntl" should take you to the registration page.
Before you try that, it might be worth just looking in your internet connections and deleting any settings that might be buried in there. Best setup for ethernet connection is to allow everything to connect automatically.
|
before he starts deleting anything the best advice that noone
seems to give is simply download (ftp/html/torrent whatever)
a smallish selfbooting

linux liveCD and trying to browse through the NTL connection with that.
for instance Slax 5.0.2 works nice with my madwifi pcmcia
laptop machine , never tryed it with a standard rtl PCI net card
(OR whatever U have) but if not, many work just fine.
http://www.alltheinternet.com/texis/...?q=livecd+mini
if that can work than it points to a problem with
his (i assume- shouldnt really LOL ) windows OS install.
ohh and just for reference im on 2meg and in wythenshawe too
----------------------------------------------------------------------------------
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 * * * Request timed out.
2 19 ms 22 ms 27 ms bagu-t2cam1-b-ge96.inet.ntl.com [80.5.162.145]
3 107 ms 205 ms 222 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
4 160 ms 149 ms 217 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 356 ms 319 ms 322 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 190 ms 151 ms 161 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 155 ms 268 ms 246 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 230 ms 111 ms 88 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 108 ms 19 ms 26 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 17 ms 35 ms 18 ms 212.58.238.153
11 22 ms 28 ms 22 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:
1 * * * Request timed out.
2 29 ms 97 ms 98 ms bagu-t2cam1-b-ge96.inet.ntl.com [80.5.162.145]
3 7 ms 9 ms 10 ms bagu-t2core-b-ge-wan63.inet.ntl.com [80.5.161.13
7]
4 9 ms 9 ms 8 ms lee-bb-b-so-300-0.inet.ntl.com [62.253.188.29]
5 20 ms 95 ms 96 ms lee-bb-a-ae0-0.inet.ntl.com [62.253.187.185]
6 22 ms 15 ms 16 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 15 ms 18 ms 16 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 146 ms 91 ms 67 ms tele-ic-2-so-010-0.inet.ntl.com [62.253.185.86]
9 37 ms 135 ms 394 ms ntl-ge2-8.prt0.thdo.bbc.co.uk [212.58.239.217]
10 69 ms 93 ms 67 ms 212.58.238.153
11 42 ms 22 ms 27 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]
Trace complete.
the first 1 hop gets me LOl
as you can see its getting worse....................