Limited or no connectivity solution for the errors on the socket, SMP and TCP/IP Stack

[Inigo]

The common mistake occurs with a notice of limited or no connectivity accompanied, as appropriate, by an error message like "An operation was attempted on something other than the socket". Sometimes, using the fundamental and popular diagnostic tool, pc Hijackthis, can be seen entries for the socket type "Unknown file in Winsock LSP" that HijackThis can not solve. Network problems are frequent, difficult to connect to the first stroke, sudden disconnections from the Internet, the DNS errors, mistakes and problems getting a DHCP IP ind2010irizzo to surf or chat can be caused by a bad configuration of two elements called Socket and TCP / IP Stack. Winsock, is instead to show the Windows Sockets API to define the rules by which programs connect to the network. Windows in general and this is all automatic WinSocket never encountered. Briefly, the socket is the address of the network including IP and port that uses a program or a specific application to enter the network, the socket of Internet Explorer or other browsers can not see but it is "site address: 80" with 80 to is the port number.

[Inigo]

We do not know why, perhaps a virus or a program that bad, but these rules address could be lost thus preventing the programs installed on PCs, as well as the browser to surf the Internet, to access the network. Both for those novice users who have a problem on Windows of this type of problem is difficult to analyze because it is unclear and the solution is not unique. My advice is, however, if there are sudden or unexplained connection problems, to prove, as a first option, to repair the socket and TCP / IP stack which, even if you do not have the slightest idea what they are, can be managers of limited or no connectivity. Winsock errors can be solved manually or with automated tools obviously much more immediate and easy. Just to make things clear, we see first the manual procedure, which can then be replicated by a small tool effortlessly and without having to go crazy.

[Inigo]

Manually to resolve the limited or no connectivity, you can go to Start -> Run and type "regedit" thus opening the editor of registry keys. As before touching the registry keys should make a backup to prevent most damage, for each key to be deleted, click on "Export" from the File menu and save so the original versions of these items in order to restore them properly in If you make mistakes. The keys to delete are:

HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ Winsock
HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ Winsock2

Now you can close the registry.

In the C: \ Windows \ inf (if you do not see the folder options and go from the menu "View" enable view hidden files and folders) Nettcpip.inf search for the file and open it with Notepad.

the section where it is written [MS_TCPIP.PrimaryInstall], you must modify the Characteristics = 0xa0 entry by replacing 0xa0 with 0x80. After saving and closing the file you can go to Control Panel, click Network Connections and look for your connection (LAN). Click the right mouse button, go to the properties, press the Install -> Protocol -> Add, and then "Disk Driver". In the text box you must write the path c: \ windows \ inf, and the next step, select Internet Protocol (TCP / IP).

[Inigo]

If all went well, now becomes available on the Uninstall button you can press to the Internet Protocol (TCP / IP) and when finished, close the window. Returning finally to the property, you reinstall the protocol TCP / IP repeating the same procedure as the driver disk. This method should work but I can recommend, before venturing into the settings manually, try the automated tool Rizone Winsock Repair. This is a program where there is a new portable version described in the article on how to repair and restore the Internet connection network ) that has several functions:

• Reset the TCP / IP stack that major rewrite of the Windows registry keys and their default values (to dos can also be made by writing netsh winsock reset)
• Repair the Windows Sockets, Winsock, so that network connectivity issues disappear.

With this tool are also reset the so-called LSP (Layered Service Providers), those that Hijackthis can not remove. Some of them probably will be reinstalled and then, if some program does not work anymore, probably to remove and put back again because it has lost the references LSP. LSP Fix Winsock Repair is an alternative and is recommended if the connection works, but you encounter problems with these mysterious objects, or you receiving alerts with HiJackThis. This second tool lists the LSP and this allows them to be removed so selected and not indiscriminately. If you have not understood anything about the article is quite normal because they are network concepts rather articles that deal in such a place can not be understood. The important thing though is that following this procedure, there may be a good chance that the connection failures are resolved, if it does not work then you can call the call center of your provider and report the transactions carried out with bravado in order to prevent them from say that "you need a technician because the problem is yours".