destination net unreachable from XP dialup

XP SP3 dialup connection "connects", but can't ping anything beyond the modem itself.  All other IP addresses (e.g. the ISP's DNS server) return "Reply from 208.59.89.134: Destination net unreachable."  That address (208.59.89.134) is the ISP's "server IP".  Since I can't get to this address IE can't get anywhere.  This must be a simple configuration problem - but I've tried everything I can think of.  Help please.
cohenjm98Asked:
Who is Participating?
 
Michael_MCDSTConnect With a Mentor Commented:
Things to try...
Click START > Run type cmd and hit OK

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

Reboot the machine.
Or
ipconfig /flushdns
ipconfig /renew
 
Or
Start / Run / Cmd / Ipconfig /Release and then /Renew...
Reboot the PC
Start / Run / Netsh winsock reset
Rebbot the PC
Try ping www.google.com and check for any timeouts
0
 
houssam_balloutCommented:
sometimes you can't ping but you can browse website
had you try to browse websties using IE

also go to IE , toos>internet options >Connenctions> remove proxies if there are
0
 
cohenjm98Author Commented:
MIchael: tried ALL your reset suggestions, but still get "destination net unreachable" when pinging anything - even when pinging the ISP's "server IP" of 208.59.89.134.  BTW, the ipconfig /renew command will not work while in this "connected but can't reach anything" state.  The command replies with "The operation failed as no adapter is in the state permissible for this operation."

Houssam: IE browsing doesn't work at all - I get the "Internet Explorere cannot display the webpage" message. Also, no proxies are set.

Might this be (I know blaming HW is usually a desperate ploy) a modem problem?  The internal modem card has always worked on this machine - and in fact works now in that it dials and connects.

Other ideas?

Thanks.

0
 
cohenjm98Author Commented:
Turns out this was a RSN (the ISP) problem.  The user account was not current (i.e. outstanding billing issue) and RSN's "normal" splash screen that  indicated this state was not presenting properly.  All the user saw was the connected-but-not-connected state described above.  So, the PC was properly configured.  Thanks for your help on this.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.