Cannot connect to network / internet- Win 98


Just got another computer off of ebay.

I reformatted, installed windows and:

Connected to cable modem w/static IPs (6 on network)
Confirmed LAN cable is live.
Intel PROSet II software confirms Link & activity; passes EEPROM, Loopback etc.
Driver stats continue to show packets sent & received.
winipcfg shows internal address - not one of my statics (169.254..)
cannot ping

Interestingly, on all of my other machines, when I look at DHCP server in winipcfg, it shows the same address of;  must be road runners DHCP server(?) - but with *this* (new) box, the DHCP says

Seems to me - (the *non* -expert) - that it is simply not finding an address from the DHCP server for whatever reason.

Knowing my IP addresses for each LAN cable, I connected one and instead of allowing it to try to find an address, I specified the known address as well as subnet, DNS and gateway.  Surely *this* would solve it, providing the problem was that it was not being addressed properly!

Nope... Hence, my post.  Hoping someone can assist.

Who is Participating?
idez_rspConnect With a Mentor Commented:
Ok.  Try an existing cable from another machine, Use a known good port.  And power down (cold) your Cable modem.

I have seen RoadRunner (in NY) hold a MAC address and not allow another IP to get a lease because the allowed IP's 6? in your case were assigned to existing NIC's.

If that doesn't work try this Tech doc for Troubleshooting Winsock...

LucFEMEA Server EngineerCommented:
Hi dakine007,

You most likely have a corrupted winsock or tcp/ip stack, try this tool to fix this:

If that doesn't work, please try it manually by following the guide at this page:


I think you'll need a new driver for your NIC. Even if some things may be ok when the NIC looks onto the ethernet - i've seen a lot of faults beeing gone by just installing the newest driver.

As you don't tell your cardname, i can just point to the downloadpage of intel ->

If you don't find it there, you should try other resources like etc.

check this out before installing too much

good luck, Holger
The new generation of project management tools

With’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

dakine007Author Commented:
Hi LucF;

The site says that the winsock fix is for :
This program is designed to fix a situation where all of the following are true:

the computer can get a valid IP address
the computer can ping DNS numbers
the computer can be pinged from other computers
all other network services do not work (Telnet, ftp and Web browsers)

....and in fact, none of the above is true.  Despite this, I went to the earthlink site and followed the instructions to do it anyways.  

Still not working.

Any other ideas?
dakine007Author Commented:

Thanks for the reply - I should have mentioned that I did in fact, re-install the latest drivers for the onboard NIC - downloaded from the MSI site.  Also tried one from Driveguide

...   NIC tests out fine with loopback etc - it appears it is working / installed properly

dakine007Author Commented:
Sorry - was re-reading my post above to Holger - it may appear to some users that my problem is solved by the way it reads.

Not so.  Still cannot connect.  

If your getting a 169.x.x.x address then its having some type of network communication problem.
I would start with the basics, check your cable? Is it a standard cable or crossover?
Is your router configured for this many IP's?
Sometimes they limit the # of IP's by the subnet mask, what subnet mask do you have on the other PC's?
Check the port the cable is pluged into on the Cable modem, is it a LAN port?

Check this it has some good info:;EN-US;q220874
dakine007Author Commented:

Thanks for the reply.

Standard cable is confirmed - working.  When connecting this LAN cable to any other machine on the network, it connects fine.

Router is OK - this nubmer of machines is supported -

dakine007Author Commented:
The "problem" that I can see is that all of my other machines show a different DHCP server address.  This one shows

The question of how to change the DHCP address is now raised.

The is really saying that it doesn't see your DHCP server.  The computer listens or brodcasts for a DHCP server.  It's not seeing yours.  The 169.x.x.x is a IP built in to winsock now so computers that can't see a DHCP server still get an IP.

Since you got this computer from E-bay and as I can see have not been able to verify the NIC's function I would say pop in a new / verified NIC.  ($10).

Also, another thing to try is to manually (via the NIC driver) set the Speed of the card.  I have seen too many that do not properly autosense and don't negotiate the speed properly.

Try setting it to 10MB Full, or 10MB Half.  Cold Boot (No power at all) and see.  Also, you might try releasing the IP on another machine (command prompt:  IPCONFIG /RELEASE)turning off the other computers and rebooting your cable modem just to make sure it's not a Cable Modem config issue.

Good luck!
dakine007Author Commented:

Have tried another confirmed good PCI NIC - removed the on board and disabled then installed 3com with latest drivers.

I have released other IPs on network... even connected direct from cable modem to NIC.

Odd, because I have added/ changed / moved machines in the past and never had this problem!

Any other ideas?
dakine007Author Commented:

Despite releasing IPs from all the other machines, it wasnt until I power cycled the cable modem that this machine found an IP.

Geez!  Seems so obvious!  

Problem solved.  Thank you.
I've seen it happen all to often.  The Cable company / cable modem locks the IPs to the MAC Address of the computers NIC.  Even when it's down for a while.  RoadRunner (Time Warner Cable) recomends powering down for 20 Minutes in some cases.

Glad I could help.  :)
Oh, one last thing.  Please remember to close this question out.  :)  

Take care.
All Courses

From novice to tech pro — start learning today.