Free Republic
Browse · Search
News/Activism
Topics · Post Article

Any ideas, suggestions, comments would be GREATLY appreciated. (I shall ignore all the "Get a Mac" and "Learn Linux" comments, since the discussions for them are that way and over there.)
1 posted on 01/14/2004 6:50:59 AM PST by Xenalyte
[ Post Reply | Private Reply | View Replies ]


To: Xenalyte
Try another browser.

If you don't have one download Firebird

If you still can't visit secure sites it is definitely deeper than IE.

2 posted on 01/14/2004 6:56:04 AM PST by American_Centurion
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
I'll assume you're using Internet Explorer as a browser?

I strongly suspect the fix is simply changing a setting in IE "Tools" (at the top)...either Security or Privacy.

I think I had this happen to me for no apparent reason and I simply changed the slider bar for either Security or Privacy, but it was so long ago I'm not sure.

I'd try the Microsoft website and search for https and see what comes up.
3 posted on 01/14/2004 6:57:38 AM PST by John H K
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
I really have no advice for you, but an observation; THIS page starts with http and you're here. Is that your home page?

Also, FR STILL seems a little glitchy this morning. Very slow here.
4 posted on 01/14/2004 6:58:53 AM PST by EggsAckley (...................Repeal the Fourteenth Amendment.......................)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Have you tried to make all your security settings default in IE? Tools menu --> Internet Options menu --> Security tab --> Default Level button.

A quick look in google for "can't access https pages" reveals a lot of hits. The top-most hit refers to a firewall/proxy setting problem/fix on the local PC.

5 posted on 01/14/2004 6:59:19 AM PST by Cultural Jihad
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
If you know what secure port you're supposed to enter, try appending that to your URL. eg.: https://www.ebay.com:8080 The common ones are :8080 and :443 but I'm sure there are others.

9 posted on 01/14/2004 7:03:27 AM PST by brityank (The more I learn about the Constitution, the more I realise this Government is UNconstitutional.)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Hey Xenalyte, I'd check your IE settings as other posters suggested, also check the version you're using under Help --> About Internet Explorer.

Failing all that try another browser, ie: Netscape or Mozilla.

NFP

10 posted on 01/14/2004 7:03:38 AM PST by Notforprophet ("You can have a nanny state if you prefer. But not for long." - Mark Steyn)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
I have about 40 PC's here running Windows XP with various levels of patches installed (up to today's MDAC hotfix) and we test using SSL. None of these PC's has had a problem in the last 1 1/2 years accessing any secure sites. I think that maybe you have a third party software conflict, or you have inadvertantly changes some IE Settings. I suggest go to Tools -> Internet Options -> Advanced and select "restore defaults" unless you understand what all the settings do.
11 posted on 01/14/2004 7:04:10 AM PST by Woodman ("One of the most striking differences between a cat and a lie is that a cat has only nine lives.")
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Another hit FWIW:

"Dont know about netscape but i faced the same problem in IE - solved it thus: tools>internet options>connections>lan settings>Use proxy server>advanced>Use same proxy server for all protocols that did it - the "https://" secure pages started sowing up. reÆó{s Vishwaneet"

14 posted on 01/14/2004 7:04:32 AM PST by Cultural Jihad
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Another hit:

  I can't view secure Web pages


If you can see normal (http) Web pages but can't see secure (https) Web pages their may be several causes.


15 posted on 01/14/2004 7:06:56 AM PST by Cultural Jihad
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
I just wanted to state that I doubt that the problem is associated to security updates from microsoft.com. Try some of the good advice offered by others here.
Good luck.
16 posted on 01/14/2004 7:07:57 AM PST by thegreatbeast (Quid lucrum istic mihi est?)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Update to a current version of IE. Many secured sites will not allow access with outdated versions.
17 posted on 01/14/2004 7:08:54 AM PST by paul51
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
the non-secure Warrior Princess

Should this be the insecure Warrior Princess?

Please don't hurt me

You might look at your custom security options under intenet options for IE. I'm not experienceing any trouble with secure sites. So far this morning. I'll go check and report back, your Highness.

22 posted on 01/14/2004 7:11:49 AM PST by The_Victor
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
God is trying to tell you not to view Weebl porn.
24 posted on 01/14/2004 7:13:49 AM PST by Timesink (I'm not a big fan of electronic stuff, you know? Beeps ... beeps freak me out. They're bad.)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Are you logged on?
27 posted on 01/14/2004 7:20:04 AM PST by humblegunner (Got Mental Health Insurance?)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
Sounds like your port 443 is being blocked.

It might be an IE problem. First thing to check is to go in your browser to Tools/Internet Options/Advanced and make sure that both "Use SSL 2.0" and "Use SSL 3.0" are checked.

If you have any firewalls going, disable them.

Problems like this are frustrating. Sometimes they just go away, but if you've had it since August, doesn't sound likely.

Are you still using the same ISP you have had since then? It could be blocking the port.

Good luck with this.

39 posted on 01/14/2004 7:39:24 AM PST by KellyAdmirer
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
If you suspect that XP's Windows Update is the culprit, I have a solution when you get back up and running.

I do not use XP. I hate it. But I have a number of friends that I have set it up for.

The one thing you really must use is called XP Anti Spy.

XP AntiSpy is a little utility that let's you disable some built in update and authetication 'features' in Windows XP. It is a very small utility that runs as a stand alone and requires no installation and it is FREE

There are quite a number of settings in XP that allow it to "phone home" to MicroSoft and there are other settings that are simply a nuisance. If you like, you can disable these functions manually, by going through the System and checking or unchecking some check boxes. This will take you approximately half an hour.

With XP Anti Spy it takes about 30 seconds. Click on the link and give it a looksee. To download, look on the bar to the left and click "Downloads"...then click on "xp-antispy" then scroll down to "xp-AntiSpy English" (It's a .zip file). It's only 29 Kb in size. Download it and unzip it to your root directory then just double-click on the XPantispy.exe file.

Here's a screen shot:



42 posted on 01/14/2004 7:43:07 AM PST by Bloody Sam Roberts (Under penalty of law: This tag not to be removed except by the user.)
[ Post Reply | Private Reply | To 1 | View Replies ]

To: Xenalyte
The problem may not be on your end. Apparently, a bunch of Verisign issued certificates expired very recently. Verisign/Network Associates is blaming its customers, and some of them are blaming Verisign.

Expired VeriSign certificates cause confusion
http://news.zdnet.co.uk/0,39020330,39118994,00.htm
"Users have experienced problems when accessing SSL-encrypted pages on sites whose certification depended on VeriSign's own expired certificates.

The company said that older versions of its Intermediate Certificate Authority (CA) expired on 7 January. "As a result, users attempting to establish SSL session with sites that had not updated their CA certificates may start encountering error messages," said VeriSign in a statement. "There is no security danger, and users who ignore these error messages can successfully establish secure SSL connections. However, sites should update their CA certificates if they have not already done so, to avoid user confusion. No action is required on the part of end users."

Also:
http://www.zdnet.com.au/newstech/security/story/0,2000048600,20282575,00.htm
The expiration of some of VeriSign's certificate-authority certificates last week appears to have caused problems beyond harmless error messages generated when users tried to access secure areas of Web sites. Security-software firm Symantec on Friday blamed VeriSign for problems with its security products that left users' PCs unresponsive and unstable.
44 posted on 01/14/2004 9:58:27 AM PST by PAR35
[ Post Reply | Private Reply | To 1 | View Replies ]

Free Republic
Browse · Search
News/Activism
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson