NTL - USB to ethernet technical problem

starlite_2

Have you installed the ntl software again for a direct ethernet connection?

We had the same problem when we got an ethernet port, and just needed to update the drivers etc.

bytenserve

Try this link, you may find the info required

http://www.chetnet.co.uk/articles/index.php?page=index_v1&c=8

This is the unofficial site for NTL but has some very useful info and they usually are helful and prompt if you drop them an email

itsfrommark

thank you all above for your advice. Have tried the ntl broadband installer to change from usb to ethernet, but it reported a problem (although the nic ethernet card was recognised and I selected it). Anyway will go away and try the other advice and report back in the next 24 hours. Thanks again. Mark

robnye

can you see a green/orange light on the nic card?
if not then check that it isnt disabled in control panel.
also try powering of the ntl modem and leaving for 15 minutes, then power the modem on then connect everything up

espresso

starlite wrote:

Have you installed the ntl software again for a direct ethernet connection?

We had the same problem when we got an ethernet port, and just needed to update the drivers etc.

NO NTL SOFTWARE is required to be installed on the PC to use NTL via Ethernet, updating your drivers is a totally different thing!

:rolleyes:

T4i

Yup, If you get a CD from your ISP DONT install it. You really dont need it, all it does is hog your p.c and have things starting up when you will never use them....

Blueyonder support 'tool' - What a waste of time and effort.

Not sure about AOL though, they prolly have something on the CD that needs to be installed to get it all *half* working.

itsfrommark

Dear all, the resolution (to my switching from usb to ethernet connection) was in the end to get ntl to replace the modem; but only after I had checked everything many times with NTL.
Apparently (according to the engineer) there are quite a few of this model ntl250 (dark blue) that exhibit an ethernet connection failure.
Mark