IT WORKED FOR ME!!! THANK YOU

After two days of trying net sh commands and reinstalling and uninstalling antivirus and personal firewalls, disabling services and even trying to test telnet to 443 ok and telnet to 80 without success, it did work for me this app from Check Point.


THANK YOU!
http://download.zonealarm.com/bin/fr...cpes_clean.exe


> On Sunday, July 01, 2007 11:00 AM Raymo wrote:

> When I run connection diagnostics in IE (Windows XP Pro)
> it reports FTP OK, HTTPS - OK, but could not make HTTP connection
>
> Only one computer of three on my adhoc workgroup reports this error.
> It reports this error for both wired and wireless connections that are
> otherwise available.
> Sure enough, I can connect to email, newsgroups, and FTP and websites via
> HTTPS.... only HTTP won't work.
>
> What's the problem and how do I fix it?


>> On Sunday, July 01, 2007 6:32 PM nas wrote:

>> "Raymon" wrote:
>>
>>
>> Open a Run command and type in:
>> regedit.exe click [OK] locate this Key, does the value exist on it?.
>> [-]HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\URL\Prefixes =
>> ftp"="ftp://"
>> "gopher"="gopher://"
>> "home"="http://"
>> "mosaic"="http://"
>> "www"="http://
>>
>> = ... First, try to clean up your caches, Internet files and delete cookies
>> by doing this:
>> Click Start >> Control Panel >> Double click Network and Internet
>> Connections >> Double click Internet Options.
>> On the IE properties windows you will see these Taps:
>> General | Security | Privacy | Content | Connections | Programs |
>> Advanced
>> Under General Tab clear your History, Internet Files and Cookies.
>> Then click on Advanced tab and scroll down to under the Browsing Option:
>> [&] Browsing
>> [ ] Enable Third-Party browser extensions (Req Rest) uncheck this box.
>>
>> [&] HTTP 1.1 Settings
>> [ ] Use HTTP 1.1 ,= Make sure this checked
>> [ ] Use HTTP 1.1 through proxy connections
>> If you using proxy check the proxy one if not check only the first one.
>>
>> Then under Security Option:
>> [&] Security
>> [ ] Use SSL 2.0
>> [ ] Use SSL 3.0
>> [ ] Use STL 1.0
>> Then click on Programs Tab and click Manage Add-Ons and Disable all non
>> Verified Add-Ons (You should Renable them later one-by-one and see the
>> culprit and update it or remove it.
>>
>> Then download this software and update it then run a scan for malware:
>> http://www.lavasoft.com/products/ad-...e_personal.php
>>
>> = Then Open a run command and type in these DLLs to re-register them:
>> regsvr32 SOFTPUB.DLL
>> regsvr32 Wintrust.dll
>> regsvr32 Mssip32.dll
>> regsvr32 Initpki.dll
>> regsvr32 Msjava.dll
>> regsvr32 Gpkcsp.dll
>> regsvr32 Sccbase.dll
>> regsvr32 Slbcsp.dll
>> regsvr32 Urlmon.dll
>> regsvr32 Cryptdlg.dll
>> regsvr32 Dssenh.dll
>> regsvr32 Rsaenh.dll
>> Note you can copy the above and paste in a Notepad and Save As on the
>> Desktop reg.bat file then you can open a run command and type in:
>> C:\reg.bat click [OK] and then Yes.
>> Again on the Run command type in:
>> ipconfig /flushdns click [OK]
>> ipconfig /renew click [OK]
>> netsh winsock reset click [OK]
>> Reboot your machine and see if you can access any website/link easily and
>> without the cannot connect error message.
>>
>> = Open the Windows
>> Explorer and locate this path:
>> C:\Windows\System32\drivers\etc = look in the Right Pane/window for this
>> file called the HOSTS file but not the one with the extension *.SAM* leave
>> this as is.
>> If you can't see it try to click Tools >> Folder Options and select show
>> Hidden files and folder, then right Click the Hosts file and select open with
>> Notepad.
>> There see any reference for that site and remove it, you Hosts file will
>> looks like this:
>> 127.0.0.1 LocalHost
>> ------------------------------------------
>> Remove all other References other than those above.
>> You can also try to assign the web address in the trusted zone on the IE
>> properties.
>>
>> => Before we go further are you connecting by Router or Modem, in either try
>> to
>> Power or unplug the Power cord for the Router/Modem for about 40 seconds or
>> so be generous with it <g> turn the computer OFF and wait for the time to go
>> by!!.
>> Then Turn the Router/Modem ON and wait a minute or so then Power ON the
>> computer and try to establish a connection and try the link, does it work?.
>>
>> If still then continue the heavy work:
>> Open windows Explorer and locate the Hosts file and Rename it to Hosts.OLD
>> Reboot the machine and try, does it work.
>>
>> If not try this:
>> search for them by this name *index.dat* and you can delete them
>> then the on reboot the system will recreate them for you.
>> Some of them here:
>> C:\Documents and settings\Administrator\Cookies = index
>> C:\Documents and Settings\User\Cookies = index
>> C:\Documents and settings\User\User data = index
>> C:\Windows\Temp\Cookies =index
>> C:\Windows\Temp\History = index
>> C:\Windows\Temp\Temporary Internet Files\Content.IE5 = Index.dat
>> Reboot your machine and see if this helped.
>> Check your connection (TCP/IP setting) are set correct.
>>
>> http://www.microsoft.com/communities...=en-us&m=1&p=1
>> HTH.
>> Let us know.
>> nass
>> ===
>> www.nasstec.co.uk


>>> On Sunday, July 01, 2007 9:34 PM Raymo wrote:

>>> "nass" wrote:
>>>
>>>
>>> I tried all the above, I still cannot connect with HTTP.
>>> Only command that did not work was ipconfig /flushdns
>>> which reported it was unable to do.
>>>
>>> All ipconfig settings are normal, I use a wireless and wired linksys router
>>> which allows two other computers to operated normally. The defective computer
>>> connects normally thru this same router (by wireless or wired) via ftp, thru
>>> newsgroups and also to secure www via https but still will not connect via
>>> HTTP only.
>>>
>>> Anyother ideas?


>>>> On Monday, July 02, 2007 8:22 PM Raymo wrote:

>>>> "Raymon" wrote:
>>>>
>>>>
>>>> Just some additional information. This problem occured after I un-install
>>>> EZ Trust firewall/anti-virus after which I had no connectivity at all. After
>>>> researching and trying many different suggestions including those in the
>>>> first post below the original posting, I found connectivity was restored as
>>>> mentioned above... all except HTTP. I think the clue may be that something is
>>>> blocking port 80 on this machine since FTP, SMTP, HTTPS and news all have
>>>> the ability to connect.
>>>>
>>>> How do I find what is blocking port 80??


>>>>> On Tuesday, July 03, 2007 2:31 AM Chuck [MVP - Windows Networking] wrote:

>>>>> On Mon, 2 Jul 2007 17:22:01 -0700, Raymon <(E-Mail Removed)>
>>>>> wrote:
>>>>>
>>>>>
>>>>> Raymon,
>>>>>
>>>>> One of the things tried above was the native Winsock reset. Our experience here
>>>>> has been that several different tools, each with its own different ability to
>>>>> reset a problem, can be necessary to fix LSP / Winsock. If you've just un
>>>>> installed a security product like the EZTrust suite, this is definitely a
>>>>> possibility.
>>>>> <http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
>>>>> http://nitecruzr.blogspot.com/2005/0...-layer-in.html
>>>>>
>>>>> And look at the LSP enumeration process too, if corruption isn't the problem.
>>>>> This will give you a hope of identifying the port 80 block.
>>>>>
>>>>> --
>>>>> Cheers,
>>>>> Chuck, MS-MVP 2005-2007 [Windows - Networking]
>>>>> http://nitecruzr.blogspot.com/
>>>>> Paranoia is not a problem, when it's a normal response from experience.
>>>>> My email is AT DOT
>>>>> actual address pchuck mvps org.


>>>>>> On Tuesday, July 03, 2007 6:56 PM Raymo wrote:

>>>>>> "Chuck [MVP - Windows Networking]" wrote:
>>>>>>
>>>>>>
>>>>>> Thanks for the help, it at least gave me some more things to try.
>>>>>> I downloaded and ran the LSP fix program but it did not help.
>>>>>> So far everything checks good when I compare with two other XP machines
>>>>>> that have good connectivity. Only difference is the
>>>>>> lack of HTTP, and the only test besides the two browers that won't browse is
>>>>>> the MS Network connections test built into IE, as reported previously.
>>>>>>
>>>>>> Still looking for more ideas,
>>>>>>
>>>>>> Raymon


>>>>>>> On Wednesday, July 04, 2007 1:21 AM Chuck [MVP - Windows Networking] wrote:

>>>>>>> On Tue, 3 Jul 2007 15:56:00 -0700, Raymon <(E-Mail Removed)>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> OK, you tried the native Winsock reset ("netsh winsock reset"), and you tried
>>>>>>> LSPFix. Did you try WinsockXPFix? The Cerelli registry key reload? Reset
>>>>>>> TCP/IP?
>>>>>>>
>>>>>>> How many HTTP hosts did you try, that didn't work? How many HTTPS hosts that
>>>>>>> did? Did you try to access any hosts by IP address?
>>>>>>> <http://nitecruzr.blogspot.com/2006/05/identifying-dns-problem-in-your.html>
>>>>>>> http://nitecruzr.blogspot.com/2006/0...m-in-your.html
>>>>>>>
>>>>>>> Did you check your MTU?
>>>>>>> <http://nitecruzr.blogspot.com/2007/06/determining-mtu-to-single-server.html>
>>>>>>> http://nitecruzr.blogspot.com/2007/0...le-server.html
>>>>>>>
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Chuck, MS-MVP 2005-2007 [Windows - Networking]
>>>>>>> http://nitecruzr.blogspot.com/
>>>>>>> Paranoia is not a problem, when it's a normal response from experience.
>>>>>>> My email is AT DOT
>>>>>>> actual address pchuck mvps org.


>>>>>>>> On Wednesday, July 04, 2007 8:46 AM Raymo wrote:

>>>>>>>> "Chuck [MVP - Windows Networking]" wrote:
>>>>>>>>
>>>>>>>> I have tried the WinsockXPFix, I believe that is what restored some
>>>>>>>> functionality
>>>>>>>> originally.
>>>>>>>>
>>>>>>>> I have tried many HTTP sites both name and IP address, none will connect. I
>>>>>>>> have only tried three or four different HTTPS sites and they all work.
>>>>>>>> I have gone thru all the ideas about DNS.. don't think that's it.
>>>>>>>> I have reset and/or reinstalled TCP/IP several times.
>>>>>>>> Pinging with 1472 bytes works so not a MTU issue according to your website.
>>>>>>>> I have not tried the Cerelli registry key reload although I may try that
>>>>>>>> later today.
>>>>>>>> At this point I'm not sure that it's a registry issue. I have restored my
>>>>>>>> registry
>>>>>>>> at least once to a point before I had the problem. Still no luck.
>>>>>>>> Still looking for more... short of a complete format HD and re-install....
>>>>>>>>
>>>>>>>> Much thanks for all help... I am quickly becoming a networking expert...
>>>>>>>>
>>>>>>>> Raymon


>>>>>>>>> On Wednesday, July 04, 2007 7:42 PM Raymo wrote:

>>>>>>>>> "Raymon" wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Additionally
>>>>>>>>> Running Gateway Diagnostic from IE7 shows
>>>>>>>>> the only error: Could not locate the specified NIC from iphlpapi
>>>>>>>>> I don't know what that means.... the iphlpapi.dll file is located
>>>>>>>>> in C:\Windows\system32 and also C:\Windows\system32\dllcache
>>>>>>>>> as it is in my other two working systems.
>>>>>>>>> Still FTP, HTTPS , etc continue to work but no HTTP
>>>>>>>>>
>>>>>>>>> Gateway diagnostic from IE7 shows:
>>>>>>>>>
>>>>>>>>> info FTP (passive) sucessfully connected to...
>>>>>>>>> info HTTPS: sucessfully conected to...
>>>>>>>>> warn HTTP: Error 12029 ...connection could not be established...
>>>>>>>>> error Could not make an HTTP connection
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> HELP....
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Raymon


>>>>>>>>>> On Sunday, May 25, 2008 9:42 AM Leslie Weston wrote:

>>>>>>>>>> Did you ever get your PC working? If so, what was the problem, because my main PC now has the same problem as far as I can see: I can connect over the Internet using FTP and HTTPS, but not HTTP. (I haven't tried email yet because I want to leave my emails on the server for now.)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> [My problem started when I (eventually!) got my PC working again after accidentally installing an old Beta upgrade to Microsoft .NET Framework. That locked up my PC every time I rebooted it, and I eventually fixed it by completely removing .NET Framework, but that left me with the HTTP problem.]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Internet Explorer's "Diagnose Connection Problems" tool (available when it fails to load a web page) eventually led me to the discovery that it was just HTTP that was affected, and that FTP and HTTPS were fine.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I *might* be able to fix the problem by rebooting my PC, but I'd rather find the real cause.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Les.


>>>>>>>>>>> On Sunday, May 25, 2008 9:53 AM Leslie Weston wrote:

>>>>>>>>>>> A quick correction to my previous reply. I *had* uninstalled .NET Framework yesterday for the reasons I explained, but I *did* have HTTP access immediately after that. My HTTP problem only emerged today, after I had woken the PC up from hibernation overnight.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -Les.


>>>>>>>>>>>> On Sunday, December 14, 2008 5:50 AM Leslie Weston wrote:

>>>>>>>>>>>> Just to complete my story, I did eventually get the problem fixed, but only by sending my PC away to have a clean Windows reinstall (I'd lost my installation CDs so I couldn't reinstall it myself; fortunately I still had my licence details).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Reinstalling Windows did mean that I have to reinstall all my applications (I am still doing that, but only on an "as needed" basis).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> And when something (I forget what) demanded that .NET Framework be installed before it would work, I made absolutely sure that I had a full backup before installing it. But that was over a month ago, and so far (touch wood!) everything seems to be OK.


>>>>>>>>>>>>> On Friday, October 30, 2009 5:34 PM Bill Murphy wrote:

>>>>>>>>>>>>> I had the same issue. For me it was caused (more than once) when Windows forced a hibernate because of low battery while my Sprint mobile broadband wireless modem was active. I am running Windows XP SP2.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Symptoms are the same:
>>>>>>>>>>>>>
>>>>>>>>>>>>> - HTTPS connections work normally
>>>>>>>>>>>>>
>>>>>>>>>>>>> - HTTP connections error out with no error code
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Same symptoms from using either Chrome or IE7.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I believe the underlying issue is that the winsock registries become corrupt.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here are the resolutions that have worked for me:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1. Run "netsh winsock reset" from a command prompt and then reboot. This worked once and had no effect the second time.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2. Run "netsh winsock reset catalog" from a command prompt and then reboot. This worked for me the second time this issue occurred when the first option failed. Not that this option netsh command is only available with Windows XP SP2.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> If 1 and 2 both failed, I was next going to try to reinstall TCP/IP using the instructions found here:
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://support.microsoft.com/kb/811259
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hope this helps save a few hours from someone's day.


>>>>>>>>>>>>>> On Thursday, December 24, 2009 4:30 AM as if wrote:

>>>>>>>>>>>>>> I thought this was a winsock issue for the longest time. At first using netsh to recreate the catalog worked -- but only for a couple minutes and it would go back to being crappy again.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Then I noticed a post about incomplete ZoneAlarm uninstalls sometimes leaving vestiges of ZoneAlarm around that cause the behaviour I was seeing.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I downloaded this cleaner from zonealarm:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://download.zonealarm.com/bin/fr...cpes_clean.exe
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And so far, things seem to be working.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hope this helps someone.


>>>>>>>>>>>>>>> On Thursday, July 08, 2010 7:49 AM L Roberts wrote:

>>>>>>>>>>>>>>> Try unchecking the proxy server: Click start, control panel, internet options. select connections tab, click on Lan settings, then unclick the box for using a proxy server.


>>>>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>>>>> Simple .NET HEX PixelColor Utility
>>>>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials...r-utility.aspx