Page cannot be displayed

[Guest]

I posted here a short time ago, but now have new info on my problem. Have
moved a computer that was on a wired connection (via a modem router) to a
wireless connection and found that I could not connect to the internet and
that IE was frequently hanging at start. IE seems to be behaving itself now
(cleared TIF/history/cookies, etc etc etc), but still get 'page cannot be
displayed'. But - I can ping ther router, ping yahoos IP address, use Skype.
Any ideas?

 

[Frank Saunders, MS-MVP OE/WM]

I posted here a short time ago, but now have new info on my problem. Have
moved a computer that was on a wired connection (via a modem router) to a
wireless connection and found that I could not connect to the internet and
that IE was frequently hanging at start. IE seems to be behaving itself
now
(cleared TIF/history/cookies, etc etc etc), but still get 'page cannot be
displayed'. But - I can ping ther router, ping yahoos IP address, use
Skype.
Any ideas?

Winsock damaged:
LSP-Fix - a free program to repair damaged Winsock 2 stacks (all Windows
versions)
http://www.cexx.org/lspfix.htm
Winsockfix for W95, W98, ME, NT, 2000, XP
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257
WinXP:
Get WinSockxpFix
http://www.spychecker.com/program/winsockxpfix.html
How to Reset Internet Protocol (TCP/IP) in Windows XP
http://support.microsoft.com/kb/299357
WinXP SP2: You can go to Start | Run and type
CMD
In the command window type
netsh winsock reset

 

[Guest]

Frank - you are a genius. I have spent days and days battling with this,
trying to work out if it was a network problem or an IE problem. The second
of your links did the job - which I was fairly certain it would when I read
the connection with stripping out newdotnet - never imagined that could have
been it. So you have my undying gratitude!

Best regards
Hayley

 

[Frank Saunders, MS-MVP OE/WM]

Frank - you are a genius. I have spent days and days battling with this,
trying to work out if it was a network problem or an IE problem. The
second
of your links did the job - which I was fairly certain it would when I
read
the connection with stripping out newdotnet - never imagined that could
have
been it. So you have my undying gratitude!

Thanks for the feedback.