Computing.Net > Forums > Windows 2000 > autoconfig 169.254

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

autoconfig 169.254

Reply to Message Icon

Name: HB
Date: November 8, 2006 at 07:54:08 Pacific
OS: windows 2k
CPU/Ram: intel 815 256,592KB RAM
Product: Chaintech motherboard
Comment:

I have a wired desktop with win2k Pro and a wireless laptop with XP. Netgear wgr614 router. Verizon DSL westell 2200 modem. Modem is in full bridge mode because the westell 2200 is a modem/router . My laptop is set up for wireless and works fine. However, I have no internet connection on my desktop.

Downloaded all the service packs and updates etc. for windows.

Cables are fine, ports are fine, powered on etc, etc. Uninstalled Zone Alarm on desktop. Tried static IP address. Nothing. When I do ipconfig always comes up 169.254.x.x or 0.0.0.0. ipconfig /release gives me: All adapters bound to DHCP do not have DHCP addresses. Addresses were auto configured and can't be released.

Device manager shows that NIC (3com etherlink 10/100 PCI TX NIC(3C905B-TX) is fine. Drivers are fine. Everything working properly. I've uninstalled and reinstalled and installed the latest drivers.

Here's what I think is happening. I wiped out the computer and did a clean install of windows 2K Pro. I didn't have the disk so I borrowed one from a friend. The ethernet card on that disk is 3com 3C918 Integrated Fast Ethernet Controller (3C905B-TX compatible) whereas the actual NIC installed in the computer (as I mentioned above) is 3com Etherlink 10/100 PCI TX NIC (3C905B-TX).

Is this why I get 169.254.x.x???? Subnet mask is always 255.255.0.0

Will installing a new NIC solve the problem??

Thanks!



Sponsored Link
Ads by Google

Response Number 1
Name: HB
Date: November 8, 2006 at 08:28:27 Pacific
Reply:

PS--can ping 127.0.0.1 but nothing else --gives me request timed out.


0

Response Number 2
Name: HB
Date: November 8, 2006 at 09:28:02 Pacific
Reply:

Sorry can't figure out how to edit posts. I'm trying to give as much info as I can.

More info. :Prior to setting up router, I could not connect to internet via ethernet cable and westell 2200 modem in regular mode. Only could connect to internet with USB cable. Again, device manager never shows a problem device or yellow exclamation point next to network adapter.


0

Response Number 3
Name: haroldw
Date: November 8, 2006 at 14:36:37 Pacific
Reply:

There is something wrong with your network card or it's driver. Windows defaults to a 169.254 ip address when this happens.


0

Response Number 4
Name: haroldw
Date: November 8, 2006 at 14:57:29 Pacific
Reply:

"Cables are fine"...have you actually tested the ethernet cable in some way? If not, then I suggest you try a "known good" network cable. You could also disable the wireless in your laptop and connect it with the modem. If it works fine, you have ruled out the cable and the wired portion of the router as a problem. Also, check with your ISP you may need a special type of ethernet cable, called a "crossover cable".


0

Response Number 5
Name: HB
Date: November 8, 2006 at 17:37:00 Pacific
Reply:

Thanks for replying. Yes, I've tested the cable. Used it to connect the modem to the laptop before installing the router and it worked fine. Going to download the drivers again (fresh start) and reinstall one more time.

Question: Anyone know if there are several download versiions available do I have to install them in order or can I just download and install the latest one?


0

Related Posts

See More



Response Number 6
Name: HB
Date: November 8, 2006 at 19:16:28 Pacific
Reply:

NG (no good). It didn't work ended up that windows just kept using default drivers and wouldn't touch the download drivers. Off to buy a new network adapter tomorrow. Hopefully that will be it.


0

Response Number 7
Name: HB
Date: November 9, 2006 at 09:28:14 Pacific
Reply:

PROBLEM SOLVED:

Someone on another board suggested this and here's what happened:

Quote:
Try physically removing the NIC and putting it into a different PCI slot (assuming it's not on-board). This should confuse the OS just enough to prompt for drivers. Also, if you have a bad PCI slot (yep, I've seen it) Win2K will often recognize whatever you put in there, but still the device wouldn't work.

AND IT WORKED!!!!!!! I did just what he suggested. Took off the computer case, removed the NIC and inserted it into the PCI slot above. Fired up the computer and it asked for the CD. I inserted the CD containing the proper drivers I downloaded from 3com for my NIC...and the system installed them. Voila! Internet connection.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: autoconfig 169.254

Win2K computer has strange IP from DHCP www.computing.net/answers/windows-2000/win2k-computer-has-strange-ip-from-dhcp/29463.html

DHCP clarification www.computing.net/answers/windows-2000/dhcp-clarification/35945.html

DHCP address?? www.computing.net/answers/windows-2000/dhcp-address/61447.html