Windows is quite adept at telling you if you have a properly functioning Internet connection, but how exactly does it do so? Digging into how Windows handles the problem offers insight into Windows connectivity messages.
Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-drive grouping of Q&A web sites.
SuperUser reader N. Hinkle poses the following question about the Windows internet check and authentication process:
In Windows 7, the notification area networking icon will show an error indicator if there is no internet access , and the error icon goes away once there is a successful connection to the internet . Sometimes, if the WiFi connection requires an in-browser authentication step, like on many guest networks in hotels or universities, then the following pop-up bubble appears, saying as much:
How does Windows know whether or not it has a successful internet connection?
Presumably it is checking some online Microsoft service to see whether it has a successful connection, gets redirected to some other page, or doesn’t get any response at all, but I haven’t seen anywhere that this process or the services used are documented. Can anybody explain how this works?
Such checks are one of the many things we take for granted when using a modern operating system, but even the most taken for granted elements of the user experience have an underlying mechanism. How does Windows tell us if there is an internet connection and whether or not we need to log into a Wi-Fi authentication portal?
SuperUser contributor Tobias Plutat offers some insight into the process:
After some digging (the sheer number of network and Internet related services in Windows is astonishing), I think I found it. Windows Vista and 7 have a variety of Network Awareness features, one of which is the Network Connectivity Status Indicator that performs connectivity tests that in turn are used by the network systray icon. The test for internet connectivity is simple:
- NCSI tries to load a specific page via HTTP (more precisely: a text document) and tests whether it can be retrieved.
- If that is not successful, Windows reports “No Internet access”.
The mechanism also checks whether the domain the document is hosted on resolves to the expected IP address. So, it might also assume proper internet access if this test is successful but the document can’t be retrieved.
The reason it reports “No Internet Access” when you haven’t authenticated on a Hotspot yet lies in the way a Hotspot works. It blocks all ports besides 80 and 443 (for HTTP and HTTPS, respectively), which get redirected to the Hotspot’s authentication server and might mess with DNS requests in one way or another. Thus, NCSI can neither resolve the domain its test file is hosted on, and even if it could it wouldn’t reach the actual file because HTTP traffic is redirected to the Authentication server.
Another contributor, Jeff Atwood, highlights some key quotes from the document Tobias references:
Here are the details of the connection status determination process:
The following list describes how NCSI might communicate with a Web site to determine whether a network has Internet connectivity:
- A request for DNS name resolution of
- A HTTP request for
http://www.msftncsi.com/ncsi.txtreturning 200 OK and the text
This can be disabled with a registry setting. If you set:
0, Windows will no longer probe for internet connectivity.
Apple does something very similar in iOS to detect internet connectivity and possible hotel “login” wifi pages, etc.
While this entire process is usually 100% transparent to end users, occasionally after authenticating through a Wi-Fi hot spot’s web portal, you will find yourself staring at the the actual contents of NSCSI.txt. How you ended up looking at a nondescript text document instead of the web page you were attempting to load is no longer a mystery when coupled with the previous answers on the topic.
Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.