Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: VanguardLH Newsgroups: microsoft.public.windowsxp.general,alt.comp.os.windows-xp,comp.os.ms-windows.networking.misc Subject: Re: Can't connect to Web Date: Sun, 28 May 2017 05:31:39 -0500 Organization: Usenet Elder Lines: 97 Sender: VanguardLH <> Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: individual.net t35M+qGORZP+m0Ert+/HYwBy9bBbc4DX2h/sP9inR20BcNgo5d Keywords: VanguardLH VLH811 Cancel-Lock: sha1:1RiDw1/cT0x1Gx7P6Acy7lntUDA= User-Agent: 40tude_Dialog/2.0.15.41 Xref: csiph.com microsoft.public.windowsxp.general:144043 alt.comp.os.windows-xp:6414 comp.os.ms-windows.networking.misc:106 rickman wrote: > Paul wrote on 5/28/2017 2:17 AM: > >> No one seems to have made any comments about the registry key at the end. >> Am I missing a post ? > > Maybe the one where I posted the file? The registry key is just a > comment. In later posts it is broken onto a new line by the 72 > character limitation. > >> And I hadn't heard of the 26 thing before. I wonder how it gets set >> to just "Read" ? > > That rings a bell... I didn't remember that. But a value is worthless (the HKEY) unless added, changed, or deleted by a program (the registry editor). You entering HKEY... on a command line is just going to return an error message. You would need to put the key in a .reg file (along with data names and their values since a key along doesn't specify anything unless a placeholder for a non-named "*" default value) and use regedit.exe /s .reg to load the settings into the registry or use reg.exe for each directive that was in the .reg file. Something has to use the key. A house key laying beside the door won't unlock/lock the door. Someone has to use the key. https://technet.microsoft.com/en-us/library/cc753591(v=ws.10).aspx https://support.microsoft.com/en-us/help/299357/how-to-reset-tcp-ip-by-using-the-netshell-utility Since all the netsh programs do is to reset the winsock params to their defaults and the same for the IP bind, those won't help since the OP already said they were able to protocols *other* than HTTPS to connect to other Internet hosts. They could even use HTTP. Sockets are working just fine. They are used for the other protocols, too. His IP binding works just fine since he can do e-mail, news[groups], and other protocols. If his IP binding had expired or no longer permitted by his ISP, he couldn't get anywhere onto or past his ISP's network no matter what network protocol he used. Sans all the comment lines, all that batch file has are: netsh winsock reset catalog netsh int ip reset c:\reset.log HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc} 26 ^ there was probably supposed to be a backslash here --' and the command interpreter would puke up an error on the last line since HKEY...bc} is not a program (external or internal to the cmd.exe interpreter in its console or shell). By the way, NSI = Network Store Interface. Go into services (run services.msc) and read its description. http://maximumpcguides.com/windows-7/what-is-the-network-store-interface-nsi-service/ If the NSI service was unusable, stopped, or disabled, and according to its definition, the OP would be incapable of doing e-mail and new[groups] as he stated, not just problems with HTTPS (but with HTTP still working). https://www.windows-security.org/windows-service/network-store-interface-service If NSI wasn't working, DNS doesn't work. It is unlikely the OP is specifying IP addresses to connect to web sites but instead uses hostnames. Humans like names. Computers demand numbers for addressing. The OP very likely specified hostnames for the e-mail and NNTP servers, not IP addresses, in his e-mail and newsgroups clients. Without the DHCP client, his host would not be able to connect to an upstream DHCP server (in his router/cable modem) that assigns him a dynamic IP address (but he might be using a static one in his TCP config). Back in services.msc, go into the properties of the NSI service. Look under the dependencies tab. You can see all the other services that are dependent on NSI being available. Only a value is given in that invalid HKEY line (it's not a command or program) in your batch file so it is unclear if the original author meant it to be a value for a data item somewhere under that key or the name of a key. I went to HKLM\System\CurrentControlSet\Control\NSI and, for me, under that GUID, there is no "26" named subkey and none of the data items under any subkey for that GUID-named key have a value of 26. So the original author had something create that subkey but that doesn't mean it is applicable to anyone else. The problem is not with the NSI service nor with IP binding nor with sockets. The OP said he can do e-mail, news[groups], and the diagnostics said he can do HTTP. He has a valid IP binding, NSI is running, DNS works, and sockets work because other network protocols do work. Looks like "can't connect to web" really means he can go to http:// sites but not to https:// sites. Whoever wrote that batch file that you use doesn't know networking. They just proliferated some babble that they copied from somewhere else. He recites the OSI networking model he was taught in school or read somewhere. The author intended his netsh commands to fix something which is not the problem the OP is experiencing.