Friday, April 26, 2013

Chrome net internals, troubleshooting the parent technology, and ERR_SOCKET_NOT_CONNECTED message

Every now and then my mom encounters a computer error that she cannot resolve. By the time she calls or sends a text she has done everything in her knowledge base to fix an issue. I gave her a moratorium during my moves that she must start using the F1 key, click on the question marks, or do a Google search to resolve her technology issues. 

So today she encountered an error that displayed Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Unknown error.

A Google Search for this error message produces about 2,180 results. Sometimes clearing the cache and cookies resolves some basic connectivity issues but for this particular error she encountered, this response was helpful. Closing the idle sockets resolved her errors.

If you are using Chrome and come across a site you normally access and receive an unknown error message, check out the Net Internals Test function and see the test results.

The "chrome://net-internals/" webpage is a special URL in chromium that dumps a view of the network stack's internal state. This data can be helpful when debugging performance or connectivity problems. It includes information on request performance, proxy settings, and DNS cache.

With this function, input the URL that failed to load and press the Start Tests buttonNet Internals is described in the Chromium Projects.

Have you used any of Chrome's Net Internals or tinkered around the Chromium Projects while helping friends and family?

Post a Comment