Dead Connection with IP starting 169 - Page 2

Tiptoes · 01-12-2003, 17:14

I would reiterate what Th'enginner says,

Also have you Made sure that youe USB and OBOARD LAN in the BIOS are set to ENABLE?

I would also add that as someone said above NTL Assign a MAC address unless you use the same network card you proably wont get a connection. (Unless your coming through a router)

try disabling the onboard lan and installing the other Netowrk card and then Set it up...

It should work a treat....

Sociable · 01-12-2003, 18:01

OK try this:

First go into Device manager in System Properties and remove the lan card from the list that should clear down all the settings associated with the card. (Do not refind the lan card or boot at this stage.)

Then power down the modem disconnect all cables including the Main cable to NTL and RJ45 to the PC

Power up the modem after a few mins and it will reset to default settings.

Now power down modem again and reconnect all cables including the link to the PC let the modem stabalise then reboot the PC.

When the PC reboots it will find the Lan card and reload the driver then it should see the "live" connection and should set the DHCP to the correct address rather than the 169 one.

If necessary then run the network/connection wizard to tell IE which connection to use as default.

A bit convoluted but I find going through above routine clears everthing back to default settinmgs which should then work fine.

Dooby · 01-12-2003, 21:08

can i just ask one question...are you saying you moved the hard drive from one system to a new system without reinstalling the operating system?

if the motherboards etc are different the OS may need reinstalling.

01-12-2003, 21:23

Quote:

Originally Posted by Dooby

can i just ask one question...are you saying you moved the hard drive from one system to a new system without reinstalling the operating system?

if the motherboards etc are different the OS may need reinstalling.

good point!

- didn't think of that

, it could be a factor, especially if the motherboard chipsets are different, iirc it can be fixed without re-installing the OS, but it is a right pain

Sociable · 01-12-2003, 21:41

Quote:

Originally Posted by homealone

good point!

- didn't think of that

, it could be a factor, especially if the motherboard chipsets are different, iirc it can be fixed without re-installing the OS, but it is a right pain

Actually Did just that an XP took it all in its stride re-setting all the devices and drivers without a blip LOL

My bet is that the modem just hasn't tied itself to the new Mac address of the lan card and my suggestion above should sort that same time as fixing the 169 error.

klw · 02-12-2003, 08:55

Quote:

Originally Posted by Dooby

can i just ask one question...are you saying you moved the hard drive from one system to a new system without reinstalling the operating system? If the motherboards etc are different the OS may need reinstalling.

Yes I did, different motherboard, P3 processor to Athlon XP etc. I wasn't sure it would work but it did. XP removes any hardware devices that are no longer relevant and installs the new ones.

As for my connection problem I fixed it by uninstalling and reinstalling McAfee Personal Firewall twice. The first time my connection (USB) started working but the firewall was disabled and I couldn't enable it without getting an error. After the next uninstall/reinstall it worked okay. So thanks to nemesis for the advice.

This morning I tried switching from USB to Ethernet but that didn't work so I switched back to USB. The LAN icon tells me that a cable is unplugged, but it isn't so I'm not sure what the problem is there. I have installed the drivers for the onboard LAN and no longer have a network card so will try and persevere with the onboard LAN and follow the suggestions above when I have time. For now at least I have a working connection, albeit USB.

Nemesis · 02-12-2003, 09:24

Quote:

Originally Posted by klw

Yes I did, different motherboard, P3 processor to Athlon XP etc. I wasn't sure it would work but it did. XP removes any hardware devices that are no longer relevant and installs the new ones.

As for my connection problem I fixed it by uninstalling and reinstalling McAfee Personal Firewall twice. The first time my connection (USB) started working but the firewall was disabled and I couldn't enable it without getting an error. After the next uninstall/reinstall it worked okay. So thanks to nemesis for the advice.

This morning I tried switching from USB to Ethernet but that didn't work so I switched back to USB. The LAN icon tells me that a cable is unplugged, but it isn't so I'm not sure what the problem is there. I have installed the drivers for the onboard LAN and no longer have a network card so will try and persevere with the onboard LAN and follow the suggestions above when I have time. For now at least I have a working connection, albeit USB.

NP regarding the Mcafee thingy (give us a rep) .... the cable prob could be realted to the X-over cable post from earlier.

Would be worthwhile getting a 'straight' cable and an 'x-over' cable and trying both.

Terry · 02-12-2003, 15:24

Before trying anything, make sure the DHCP service is actually running in XP. I had a similar problem recently and having tried all the useful help given by the technical folk on dot com I discovered that the DHCP client was stopped and nothing could restart it. I know you probably dont want to hear this but it took a complete rebuild to solve the problem. Good luck

klw · 02-12-2003, 16:24

Thanks but the DHCP service is running. I checked it last night.

**Paul** · 02-12-2003, 19:23

The DHCP client would have to be running to get the 169.254.x.x address, it is the client that assigns this if it can't get a reply to it's request for a real one.

imback · 02-12-2003, 19:29

Since it's XP, reinstall the nic driver anway as it will be no hassle.

Also with regards to usb, doesn't matter if it's the same HD, it happens when it's exactly the same machine, sometimes usb drivers just need to be reinstalled.