It's running WinXP
Main Topics
Browse All TopicsCustomer just got a Cable Modem and is having me set it up(I've setup lots of these modems with this ISP). I attached it to computer and all pertenant(sp?) information: IP, Gateway, Subnet, DNS; is pulled. Problem is that the setup program can't contact the registration server and when I go to ping the gateway all I get is timeout errors. I can ping the machine itself but nothing else. I think something has happened to his winsock but I haven't had a chance to run an (Layered Service Provider)LSPfix yet(I didn't have the disk with me). I'm going back tomorrow and wanted to exhaust all possibilities on here so I can try different things if it turns out not to be his winsock. I'm not exactly sure on machine specs but it is running XP and has network card built onto MB so I'm guessing it's probably a realtek chip.
Oh, when he tries to use regular phone line dialup he just gets a username error which tells me it's not having success contacting the authentication server. I'm sure the problems are related.
Thanks in advance
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
sirbounty has your fix for you, but just in case..... (if it works, give the points to SB..!!)
To reset TCP/IP within XP
(Unable to initiate Window Sockets Interface, error 0) :
Click Start -> Run -> CMD <ok>
At the prompt type:
NETSH INT IP RESET C:\IPRESET.TXT
<Enter>
Close the window and reboot.
Also:
Winsock Fix
http://members.shaw.ca/tec
You may have a hardware problem, I have had to replace (well, put in another ethernet card) countless on-board ethernet. I have had some that would work fine on a network, but would fail to work with a cable modem. I am not sure exactly why, but they have all been on-board ethernets. I would try another card and cable and see what happens.
I also have had some XP machines that flat out refused to work with cable modems. Even after rebuilding TCP/IP and trying everything else. The only fix was to do a clean reinstall.
Hope this helps! ;)
Was able to fix problem. Turns out that it was the cable companies fault. Somehow the activation server wasn't recognizing the activation software so we had to manually activate the cable modem and account. I ended up taking the machine to my shop and testing it on my network and it worked fine. I'm guessing his modem wasn't working because he had the wrong password for his ISP. That's a moot point now.
Business Accounts
Answer for Membership
by: sirbountyPosted on 2004-02-03 at 20:14:49ID: 10268133
What OS?
tallations /WinsockFi x.exe
If you suspect winsock - download this to fix it:
http://members.shaw.ca/ins
Otherwise,
Start->Run->CMD <enter>
netsh int ip reset c:\ipreset.txt <enter>