Discussion Locked

W2K Not detecting Network

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a w2k notebook. I have updated to sp2 and removed and installed all network connections but it keeps on picking up ip: 169.254.227.229. I am using an onboard network card. The laptop is an IBM Thinkpad A21m.
Please help.

8 replies

by ann777

168.254.x.x is a windows default; windows is not seeing your network at all. Are you sure that you have installed the Windows 2000 drivers for this network adapter (nic) that you have in this laptop?

Some of the IBM laptops also require a biosupgrade before working with Win2000 as well. Check into the www.ibm.com support section and make sure everything is correct for Windows 2000. Then check for the appropirate drivers for the nic.

by lordinfidel

What may be happening here is that your system is unable to talk to your dhcp server to get an IP.

This is very common in Laptops, especially with win98. Although win2k is usually pretty good about these things.

In those instances, most network cards will pull a predetermined address and assign it to itself.

Most of the time it is a private address, but I have seen instances where it assigns itself a public
address.

To troubleshoot this, assuming that you have an DHCP server located on your network, is to release
and renew the IP for that adapter.

Open up a command prompt (start/run/ type cmd press run) A msdos window will open up.

Type ipconfig, press enter. A list of all adapeters configured for that machine will be listed.

I usually choose the specific route by selecting the individual adapter. If you are unsure which
adapter to release you can issue the following command:

ipconfig /release_all enter
ipconfig /renew_all enter

or if you know the adapter number it would be

ipconfig /release "adapternumber" enter ie ipconfig /release 0
ipconfig /renew "adapternumber" enter

by lordinfidel

If you still do not see the correct IP show up for your network, then the first rule of networking
says to check the physical connection. That is, is your network cable connected, is the cable ok,
etc.

Assuming that the cable is connected and functioning properly, let's ping the loopback adapter.

type ping 127.0.0.1

If you get a sucessfully reply 4 times then the adapter is working, if you get a request timed out
then the adapter is not setup correclty.

Next check to make surethat you have tcp/ip installed for that adapter and that it is setup for DHCP.

Right click network neighborhood/properites..... right click on the connection/properties/click on tcp/ip
and click properties. Is there a IP adress assigned there?if yes then that is your problem, it needs
to be set up as Obtain an IP automatically.

Once you check those settings and if you have not been able to change anything. Then the next step is to
remove the adapter thru device manager and reboot the machine. It should autodetect it when you reboot and
allow you to configure the adapter.

If nothing else works, then you will need to contact IBM to send the laptop in for service, unless of course
you purchase a PC card (I suggest 3com 10/100 FE574B Fast-Ethernet card) so you do not have to send it in.

Good luck

by rishen.kyarkanaye

The problem was actually with the dhcp server - for some odd reason it just didn't give ip's. after restarting the server - the laptop was able to pick up an ip.

by jeffschre

I just wanted to make a correction to DarkOverlord's response pinging 127.0.0.1 (loopback) does not tell you the card is working it only tells you that TCP/IP is installed and functioning correctly. The loopback is internal address to TCP/IP no NICis required to get a good reply.

However he is correct starting with the physical connection, check for a link light first. Then move to software, pinging loopback...etc. One way to verify is to assign an IP (from a system that can access the network) statically and see if you can ping other systems on the network.

This discussion is closed to new replies.