Can't Connect to Internet

I am working on a friend's machine and I am having problems getting it to connect to the Internet. The machine is a Gateway G6-333, 333Mhz processor, 128 Mb RAM running Win 98. They access the Internet using a cable modem using Optimum as an ISP. The machine was working fine. The only thing they say they changed was they downloaded and installed Kazaa. (I have already used Ad-Aware and removed 142 pieces of spyware!!).

Here is some background on what I have done so far. Attempted to run WINIPCFG but got the following error: "IP Configuration Failed to Initialize ". I restored winsock.dll, wsock32.dll, and wsock32n.dll from the 98 CD and deleted the WINSOCK2 registry entry. I removed TCP/IP and reinstalled the drivers (most current version from the vendor, NDC) for the NIC card. After rebooting, I was able to run WINIPCFG but it doesn't appear to have any affect. After I do a release/renew all, the IP address never changes. I don't remember the exact address but it starts with 161. Since they are using the same ISP as us, it should start with 24. I have also installed a brand new (right out of the box) NIC card with no affect. I have used the modem that my machine uses to verify that it wasn't a modem problem.

One thing that is odd is when I run WINIPCFG, the only item that is in the adapter dropdown is PCI Bus Master Controller. There is nothing else for me to select. I would have expected to see the NIC as one of the choices.

Thanks for any help with this.

 

I would expect to see it as well. Quick check to tell you if there is a working NIC would be to ping 127.0.0.1 and see if you get a response.

At this point, I think I'd remove all traces of networking and start from the beginning. And make sure the version of DUN you install is the newest.

First, empty all temp files including temporary internet files & cookies.

Boot to safe mode. Remove all networking pieces including the NIC from device manager, scandisk & defrag, shut down. Remove the physical NIC. Boot up normally and shut down again. Replace the NIC (after using a pencil eraser to clean the contacts) and install all the networking hardware/services from the beginning.

 

Newt,

Thanks for you post. Sorry it took so long to respond but I didn't get a chance to work on the machine until this weekend.

I tried everything that you recommended with no success. I even tried moving the NIC to a different slot. No luck. I can ping the card and I get a response. I did notice that if I added a dialup adapter, I would get a 'PPP Adapter.' as a choice in WINIPCFG. I even tried running ipconfig from a DOS prompt to see if it would work from there. It didn't. I reinstalled the O/S with the same results. I finally did a low-level format and then reinstalled. The O/S could not find the correct drivers for the PCI Ethernet Controller. Sounds like a problem with the controller?

The only thing I have left to try is to use the Restore CD that came with the Gateway and see if that will restore the system.

Thanks for your help.

 

The restore CD is probably your best bet.

If that doesn't work, I'd try a new NIC. Get em for around $10 these days that will work fine for internet use and light-duty home networks.

 

I tried the Restore CD last night and got the same results. I already tried a new NIC and that didn't make a difference either. At this point I'm thinking it has to be a hardware problem because I've tried everything else from a software point of view.

Thanks for you help!

 

One thing to check is how well the NIC is seated in the slot. They are by far the worst for not behaving if not completely, totally down in the slot. Will work sorta.

I've seen some PCs where the motherboard was mounted just a tiny bit off-center and something would prevent the NIC from seating properly. Same symptoms as yours.

 

Not sure I understand what you mean regarding the motherboard being off center. If this was the case, would I still be able to ping the NIC and get a normal response? I can ping it and have 0% packet loss.

 

I meant the mount points for the motherboard (where it is ******* to the case) might be placed so the board would be positioned so a chip or some other obstruction could prevent proper seating of the NIC.

Or it might just not be pushed in all the way.

And yes. I've seen cases where the NIC would properly do some things and not others. I don't know nearly enough about hardware to have a clue how this could be but since I've seen it, I know it can happen.

This may well not be your problem but I simply don't have any other reasonable ideas to offer.