Computer Hope
Internet & Networking => Networking => Topic started by: HB on November 08, 2006, 09:02:12 AM
-
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!
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 probnlem device or yellow exclamation point next to network adapter.
-
installing the right drivers might solve the problem.. did it work before the reformat?
unlovedwarrior
-
Hi, thanks for responding. Since no one responded previously I never posted the solution to my problem. Here it is: What was happening is that I installed the correct drivers but windows wasn't recognizing them for some reason so I removed the NIC and put it into a different slot. This tricked Windows2K into thinking it was brand new hardware. Then I inserted the CD rom with the drivers and voila! Good to go.
-
thanks for sharing the solution for other members to see.
-
Well, I hate when people don't share the solutions to these horrid computer problems! I actually posted the same question on two other forums and got replies so I posted the solution there but not here.
-
oh..