Trouble shooting internet connectivity

Status
Not open for further replies.
Just a hypothetical question with regards to troubleshooting internet connectivity.

Considering all but one computer in a network are able to access the internet. Is it possible for the faulty computer to be able to successfully ping the network's default gateway and still NOT be able to access the internet??

Is it even possible. I think, no. what do you guys think?
 
Hi

Yes it is possible, especially if the TCP/IP stack is faulty or the winsock is corrupted, some adaware.malware can cause this to happen.

Regards
 
nettech667 said:
Considering all but one computer in a network are able to access the internet. Is it possible for the faulty computer to be able to successfully ping the network's default gateway and still NOT be able to access the internet??
define 'access the internet'. If you can ping a remote computer which is not on your lan,
then in reality you just did access the internet. Typically, 'access the internet' ends up
meaning the browser will not display website pages.

Accessing websites requires two 'accesses to the internet'; (1) a dns request
to translate the URL domain into an ip address and (2) a socket connection to
to ip address followed by GET / request. The ususal failure occurs on (1) with
a timeout reply instead of an ip address reply.

Using ipconfig /all wil show you the configured DNS address on your
system
and with NSLOOKUP www.google.com (or any other domain name) will
demonstrate that your current internet connection can translate the URL to
an IP address or not :)
 
Status
Not open for further replies.
Back