Cable Forum - View Single Post

basa · 09-11-2005, 08:57

An acquaintance has Win XP Home on a box from Tiny (dunno the exact specs .. but it's irrelevant anyway).

Basically it came with Supanet dial up installed and enabled and they used this for around 12 months with no problems.

They elected to go for ntl BB as they were already using ntl digi TV.

The ntl engineer installed a splitter close to the STB downstairs, ran the co-ax outside upstairs to an ntl SACM with ethernet to their PC.

The ethernet adapter will not 'refresh' its IP, it retains the one assigned by XP's autoconfig.

I have adjusted the Internet Connection to read "never dial a connection" and ensured all the correct boxes in Networking are selected with DHCP enabled. All the lights on the SACM are flashing (except 'send' which does not light and 'power' and 'ready' which are steady) and the NIC on the PC flashes happily.

I am satisfied the PC and SACM are 'talking' and pinging 127.0.0.1 gives a satisfactory result. ntl say they can 'see' the SACM and went through the usual routine of refreshing the 'winsock' using the 'netsh' commands.

Obviously I cannot get to start.ntl to register this connection without a DHCP assigned IP.

I have completely removed all references to the Supanet dial up software and uninstalled / installed both the adapter and 'Client for MS Networks' and run the 'WinsockXPfix' TCP/IP and Winsock refresh utility to no avail.

They have no Win XP disc only a 'Reload' CD from Tiny.

Any ideas ?

09-11-2005, 08:57	#1
basa Inactive Join Date: Jun 2003 Location: S Manchester Age: 78 Posts: 1,766	New BB connection fails An acquaintance has Win XP Home on a box from Tiny (dunno the exact specs .. but it's irrelevant anyway). Basically it came with Supanet dial up installed and enabled and they used this for around 12 months with no problems. They elected to go for ntl BB as they were already using ntl digi TV. The ntl engineer installed a splitter close to the STB downstairs, ran the co-ax outside upstairs to an ntl SACM with ethernet to their PC. The ethernet adapter will not 'refresh' its IP, it retains the one assigned by XP's autoconfig. I have adjusted the Internet Connection to read "never dial a connection" and ensured all the correct boxes in Networking are selected with DHCP enabled. All the lights on the SACM are flashing (except 'send' which does not light and 'power' and 'ready' which are steady) and the NIC on the PC flashes happily. I am satisfied the PC and SACM are 'talking' and pinging 127.0.0.1 gives a satisfactory result. ntl say they can 'see' the SACM and went through the usual routine of refreshing the 'winsock' using the 'netsh' commands. Obviously I cannot get to start.ntl to register this connection without a DHCP assigned IP. I have completely removed all references to the Supanet dial up software and uninstalled / installed both the adapter and 'Client for MS Networks' and run the 'WinsockXPfix' TCP/IP and Winsock refresh utility to no avail. They have no Win XP disc only a 'Reload' CD from Tiny. Any ideas ?