Voyager 220v blues - no connect, Default Gateway blank

[Beogista]

THIS IS MY ORIGINAL POST. THERE HAS BEEN A SIGNIFICANT DEVELOPMENT SINCE. SEE MY NEXT POST IN THIS THREAD.

I'm new to modem/routers and have just acquired a 2nd hand BT Voyager 220v. Been messing with it all day and am completely stumped.

XP home with built in NIC.

Did a reset on the 220v and connected it by ethernet cable.

Attempting to connect with the router by http://192.168.1.1 gets nothing.

ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : bel
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-15-58-6C-29-79
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 0.0.0.0
NetBIOS over Tcpip. . . . . . . . : Disabled
=================

Any idea what to try next?

How would I know if the router was "bricked"?

[Beogista]

OK. I just tried booting with an old Bart's PE and this time all the hardware appears to be working.

Can now connect with the router via http://192.168.1.1

ipconfig /all (from the Bart's PE)

Windows IP Configuration

Host Name . . . . . . . . . . . . : bartpe-4491
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter {5EF23729-915D-4FEB-A98A-894F0C31C259}:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-15-58-6C-29-79
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, January 06, 2012 5:40:25 PM
Lease Expires . . . . . . . . . . : Saturday, January 07, 2012 5:40:25 PM

At least now I know the problem is XP software/setup related. So I have to investigate that side of things.

[Beogista]

Hmm. Isn't it wonderful when advice is simple and straightforward.

"For Ethernet connections - Just connect the Ethernet cable from your PC to the modem."

Did that; didn't work. What next?

After 36 hours I found that my XP Home wasn't loading a driver: netbt.sys. There may be another way, but to force it to load I edited the NetBT registry entry, modelled on the entry for NetBIOS and changed a few settings.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT]
"Type"=dword:00000002
"Start"=dword:00000001
"Tag"=dword:00000001

After this I set DHCP Client service to auto and rebooted.

This worked on my system and I can now access the BT Voyager Router through a browser, as is amply described elsewhere.

[unlokia]

Hmm. Isn't it wonderful when advice is simple and straightforward.

"For Ethernet connections - Just connect the Ethernet cable from your PC to the modem."

Did that; didn't work. What next?

After 36 hours I found that my XP Home wasn't loading a driver: netbt.sys. There may be another way, but to force it to load I edited the NetBT registry entry, modelled on the entry for NetBIOS and changed a few settings.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetBT]
"Type"=dword:00000002
"Start"=dword:00000001
"Tag"=dword:00000001

After this I set DHCP Client service to auto and rebooted.

This worked on my system and I can now access the BT Voyager Router through a browser, as is amply described elsewhere.

Originally Posted by Beogista

Windows... marvellous for looking through, but not well designed for PCs.