Discussion Locked

TCP/IP error

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

After installing a cable modem card, The computer will not connect to the internet. If I run Winipcfg.exe, It returns this Fatal Error message: " Cannot read IP configuration". What is the cause of this and how does one resolve this issue?

Note: The cable modem card appears to be installed correctly. Under Device Manager, Network Adapters ,properties tells me device is working properly.

Thanks,

13 replies

by mphoffar

I've usually seen this from a winsock2 update that went bad. It'll be a pain to get rid of, but the way I've repaired this is to run the ws2bakup.bat from c:\windows\ws2bakup in windows. I usually get a fleet of sharing violations, so I reboot into a dos prompt and then run it again from there.

I then add in sometihng like NetBEUI and remove the TCP/IP in the network stack and reboot. I then rename the wshtcp.vxd file to force a copy from the cab files and add back in TCP/IP (and removewhatever protocol I added). WHen prompted, I overwrite the new files and then reboot.

I just add in the extra protcol, so I don't have to deal with installing the client and re-adding the adapters that I have in there.

Good luck to you

Mark

by manningj

Thank you, I went to Microsoft WebSite and downloaded the Winsock2 update. After installing the update, I was able to connect to the internet.

Thanks again for all who replied.

by cdobbin

What configuration does your ISP use, static or dynamic IP addressing? If its dynamic make sure you have DHCP enabled, if its static make sure your settings match what was supplied to you by your ISP.

by cajundon

Hi, I suggest that you contact the cable modem provider help desk to get the correct setup and parameters.

Good luck and have a great day.

Don Thibodaux, Computer Technology Consultant.

by jcsmith_pgh

It is highly likely that Marc's answer is correct and this is not a hardware or ISP problem. I too have had this error in the past which came from a problem with the winsock2 update. If you find and run the ws2bakup.bat file to remove the bad install, then reintall winsock2.

by cdobbin

Considering he said nothing about a failed install of winsock, I figured it may be his TCP/IP settings.

by loozzinit

I agree, why go crasy and start messing around with *.cab files, uninstall the Modem, and network protocols, make a note of the current "IPCONFIG /all" info before you do so tho... then restart, assuming your using a PnP/OS (98,95,w2k..etc) and seehow that goes.. before getting into the nitty gritty of IP troubleshooting, remember a phone call to your ISP for the settings, may save you a lot of time, and maybe they have seen this issue before, also " check that the cable is connected properly, may sound silly, but I once spent 4hrs on a similar issue, to only find out to my disgust that I had forgotten the first rule of Networking "Is the Network cable in properly"
Good Luck :-)

This discussion is closed to new replies.