HTTPS sites won't load, but HTTP ones will. What gives?

NotWormBoy

So my browser/net connection/whatever is acting up. I can load normal http:// sites no problem, like this one obviously since I'm posting, but I can't resolve any https:// sites, like gmail or AIB online banking for example.

Any thoughts?

I can't ping google.ie or boards.ie from the command line either, but I can get them through the browser, which is most odd. Must check if it works on a laptop or not... Turns out it does work on the laptop through FF and IE.

Firewalls are all off too, and AV disabled. No proxies in use.

And https links work in IE. The plot thickens.

Any suggestions welcome...

Gadgetman496

Unable to open certain Websites with your Browser:

HTTPS are what's known as a "Secure Sites", if you look at the address in the address bar it starts with https as opposed to http

If you are experiencing this issue only on secure sites (https) it may indicate that a component of Windows XP that processes digital signatures is damaged.

Assuming you are using XP:

RESOLUTION:

To resolve this behaviour, it is necessary to re-register the following Dynamic Linkable Library files (DLL’s)
Softpub.dll, Wintrust.dll, Initpki.dll, Dssenh.dll, Rsaenh.dll, Gpkcsp.dll, Sccbase.dll, Slbcsp.dll, Mssip32.dll, and Cryptdlg.dll files.

To do so, follow these steps:

1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type regsvr32 softpub.dll, and then press ENTER.
4. Click OK when you receive the message that DllRegisterServer in Softpub.dll succeeded.

5. Repeat steps 1 through 4 for the following files:

Wintrust.dll
Initpki.dll (Note: This file will take a while to repair. Carry on with the others anyway)
Dssenh.dll
Rsaenh.dll
Gpkcsp.dll
Sccbase.dll
Slbcsp.dll
Mssip32.dll
Cryptdlg.dll

6. Type exit and then press ENTER to quit Command Prompt.

Restart your machine & try to connect.


Second possible cause:

One other cause of this problem is the MTU settings in your router.

Secure sites may not be accessible if this setting is set too low.

RESOLUTION:

Set the MTU setting in your router to 1492

This setting is normally found in the “WAN Setup” section of the router under the PPPoE edit option.

Third Possible Cause:

Navigate to: (If the file is not present then this step is not causing your issue)

C:\WINDOWS\system32\drivers\etc\HOSTS

Right click the HOSTS file & choose OPEN
Open the file using Notepad.

Scroll to the bottom of the file & look at the entries below the line

127.0.0.1 localhost

See if the site you are experiencing problems is listed there.

Example: (assuming that the site you’re having problems with is Google)
The listing would look like this,

1.1.1.1 www.google.com

If the line with the offending Website is there, delete it.

Do Not Delete the line: 127.0.0.1 localhost (Make sure you leave this line there)

Now save the HOSTS file using this method.

From the top toolbar menu choose: File
Save As (Make sure to change the .txt option to ALL FILES in the “Save as Type” Drop down box.

Click once on the Hosts file (in the file list window)

Click Save (Agree to overwrite)

Note:
Doing any or all of the above will not in any way cause additional problems to your system.


-

gnxx

Because of the ping problem, I would really suspect that you have some type of proxy or firewall on your connection. I know you said "no proxy" but are you sure?

Alternatively, any chance of virus doing something bad.

This doesn't really explain IE vs. FF difference. Although a firewall blocking FF on port 443 would.

Can you telnet though to a HTTPS site?

NotWormBoy wrote: »

I can't ping google.ie or boards.ie from the command line either, but I can get them through the browser, which is most odd.

No proxies in use.

And https links work in IE. The plot thickens.

gnxx

Just one other quick thought, can you check your DNS and Default Gateway are as expected?

NotWormBoy

Thanks for the tips lads, appreciate it. I'll test them/check when I get home.

snappieT

One last thing, I've had this problem before. Make sure that SSL and TLS are enabled in your advanced internet options, you need them for https.