• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

Cannot connect to the internet...

C

Charles W Davis

Flightless Bird
WinXP MCE. 2GB RAM. Clean of viruses. Running Microsoft Security Essentials.
Connected through a switch to a router, to a cable modem.

This club member's computer will not connect to the internet. When I do the
Trouble shoot bit, I end up with a message that reads:
Virtual C++ Virtual Runtime Error
Runtime Error
Prgram: C:/WINDOWS\Network Diagnostic\xpartdiag.exe
This application has requested the runtime to terminate it in an unusual way


Any thoughts will be appreciated.

Chuck
 
P

PA Bear [MS MVP]

Flightless Bird
Another hijackware infection, no doubt.

What anti-virus application was installed before MSE was installed & was the
subscription still current?


Charles W Davis wrote:
> WinXP MCE. 2GB RAM. Clean of viruses. Running Microsoft Security
> Essentials.
> Connected through a switch to a router, to a cable modem.
>
> This club member's computer will not connect to the internet. When I do
> the
> Trouble shoot bit, I end up with a message that reads:
> Virtual C++ Virtual Runtime Error
> Runtime Error
> Prgram: C:/WINDOWS\Network Diagnostic\xpartdiag.exe
> This application has requested the runtime to terminate it in an unusual
> way
>
>
> Any thoughts will be appreciated.
>
> Chuck
 
G

Greg Russell

Flightless Bird
In news:81E1D78C-403B-4B29-8EDE-EFB69C214DD5@microsoft.com,
Charles W Davis <newsgroup@anthemwebs.com> typed:

> WinXP MCE. 2GB RAM. Clean of viruses. Running Microsoft Security
> Essentials. Connected through a switch to a router, to a cable modem.
>
> This club member's computer will not connect to the internet.


Start your diagnostics with the fundamentals, working outward towards the
Internet:

Start -> Run -> cmd
ipconfig /all
route print

Post the results so people can see what's happening, and especially compare
the results with other working machines on your LAN. Then check the steps in
the route:


ping 127.0.0.1

The next address will be the "IP Address" from the ipconfig output:
ping your.machine.ip.address

The next address will be the "Default Gateway" from the ipconfig output:
ping your.router.lan.address

The next address will be what's returned when you connect to
http://cfaj.freeshell.org/ipaddr.cgi from another working machine on the
LAN:
ping your.router.public.address

The next address will be one (or both) of the "DNS Servers" from the
ipconfig output:
ping your.dns.server,as-stated

ping google.com

One will *always* discover the problem in one of the above 8 steps, and
usually it's faulty DNS configuration so that one can't resolve the IP
address of google.com.
 
Top