Link to home
Start Free TrialLog in
Avatar of cohenjm98
cohenjm98Flag for United States of America

asked on

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.
Avatar of Houssam Ballout
Houssam Ballout
Flag of Lebanon image

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
ASKER CERTIFIED SOLUTION
Avatar of Michael_MCDST
Michael_MCDST
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of cohenjm98

ASKER

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.

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.