Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I recently installed Win XP Pro on my new hard drive, and now I have a dual boot system with two Windows XP installed on two different drives.
When I try to access certain web sites, particularly credit card login pages, from my new Win XP, all I get is "cannot find server" page.
The message at the top suggests to adjust my browser settings, but I adjusted the settings in my new browser the same way as they were in my old browser (2 systems installed on 2 different drives are absolutely identical, and include Win XP Pro, IE6 ,etc.)
When I try these same sites from the other win XP installed on my old hard drive, they are displayed correctly.So the question is, which browser settings might make certain web pages unavailable?
-------------
Below is a typical example of "unavailable" page:the address bar:
https://service.capitalone.com/cgi/Home?Login
the text on the page:
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.----------------------
Please try the following:
Click the Refresh button, or try again later.
If you typed the page address in the Address bar, make sure that it is spelled correctly.
To check your connection settings, click the Tools menu, and then click Internet Options. On the Connections tab, click Settings. The settings should match those provided by your local area network (LAN) administrator or Internet service provider (ISP).
If your Network Administrator has enabled it, Microsoft Windows can examine your network and automatically discover network connection settings.
If you would like Windows to try and discover them,
click Detect Network Settings
Some sites require 128-bit connection security. Click the Help menu and then click About Internet Explorer to determine what strength security you have installed.
If you are trying to reach a secure site, make sure your Security settings can support it. Click the Tools menu, and then click Internet Options. On the Advanced tab, scroll to the Security section and check settings for SSL 2.0, SSL 3.0, TLS 1.0, PCT 1.0.
Click the Back button to try another link.Cannot find server or DNS Error
Internet Explorer

This indicates a connectivity problem - like your internet connection is no good. I've never seen this problem caused by system settings - its always a conneciton issue. Who's your ISP?

ISP is not a problem - my old system is identical to the new one, with the only difference being that certain sites don't work when I access them from the new system. I think it has something to do with the security settings.

I can navigate to that page fine.
I'd say to check your security settings also, since it's an https secure web page.
Open INTERNET EXPLORER > Click TOOLS > INTERNET OPTIONS > ADVANCED tab

EC,
I can navigate to this page just fine, too, only from my old Win XP. I remember tweaking my old IE6's settings, but I don't remember what I changed.
Do you have any suggestions on what Security Settings might affect the accessibility of https secure web pages?
Thank you for your cooperation.

I just made a terrible discovery - I can't access ANY of HTTPS sites. All I get is a standard "page is unavailable" window.
I run Windows XP Pro SP1, IE6 with 128bit protection, Java Run Time environment 1.4.1 and some generic ISP software which never had any problem with accessing web-sites.

If you are running a firewall, then check that also.
The INTERNET OPTIONS > SECURITY tab
may be helpful as well.

Can you ping ip's but not domain names?
That error page is the standard 404 we all see when a page wont load. Its not specific and contains no information that will be helpful. Other than letting you know somethings wrong...

It sounds like it would be the 128-bit cipher strength missing that would cause that problem. But you said you checked that.
Try this just in case - in IE, click tools, internet options, advanced. Scroll down to the area where it says security and make sure that "use SSL 2.0" and "use SSL 3.0" are checked.
Good luck.

Here's some other ideas, and some good background info on how https/SSL works, but mostly from a developer perspective.
It's stuff I found on the WEB while searching for a similar match for a problem for a friend.
...below from the web...How to Access Those Secure (https://) Web Pages
Having problems accessing web pages on secure connections (URLs that begin “https://…)? Your browser may need to be upgraded to a higher level of encryption. To check if the browser you use is current with the highest encryption level possible, check the following:
In Microsoft Internet Explorer 4 and 5:
Select Help -> About Internet Explorer from the menu. The dialogue box should read:
Cipher Strength: 128-bit.
If it doesn’t, then you will need to install a patch or a new version of Internet Explorer. Refer to the following page at Microsoft for information on obtaining and installing the patch:
http://www.microsoft.com/windows/ie/download/128bit/intro.htm
Do I need load somthing to make https work?
You need to install certificate on your web server to make https (SSL) work. These you can buy from verisign or generate yourself using microsoft certificate server. Verisign gives free 15 days trial certificate. first generate a request file from IIS and send it to verisign with 15 minutes you will have your certificate for testing
Thanks,
Al[/b][/quote]check you cookie settings
verify your network settings
If you are connecting to the standard SSL port, 443, you have the option of appending the
port number to the URL string. However, if your Web server is using a nonstandard port
for SSL traffic, you'll need to append the port number to your URL string like this:URL url = new URL("https://[your server]:7002");
Secure connections, HTTPS and SSL
The secure hypertext transfer protocol (HTTPS) is a communications protocol designed to transfer encrypted information between computers over the World Wide Web. HTTPS is HTTP using a Secure Socket Layer (SSL). A secure socket layer is an encryption protocol invoked on a Web server that uses HTTPS.Secure Sockets Layer (SSL) allows software to communicate with Web servers in a secure, encrypted manner. Many Web sites that conduct electronic commerce use SSL to securely transmit credit card numbers from a customer's Web browser to the Web server.
All sites stored on the central Web Servers supports both the http:// and https:// protocols. If you want to take advantage of SSL, you can create secure hyperlinks in Web pages. Secure hyperlinks begin with https:// instead of the standard http://
Example:
HTTPS Example Link
When users will click on the link, they will transfer the document encrypted.If you are using FrontPage, you can also use https to edit your web site. This means that no one will be able to intercept and read the information you are sending back and forth between your computer and the Web server.
Important Notes
Web sites mapped to NICE home or divisional directories (DFS) do not support HTTPS.
SSL imposes a performance hit on serving of Web content due to the additional encryption steps that must be performed. Information that does not need to be transmitted over a secure channel should be left to normal HTTP. An example of this might be any image files (GIFs, JPEGs) used on your site.
In order to offer secured communications using SSL, a digital certificate from a certificate authority has been installed on the central servers. A certificate is valid for only one server name and only one certificate can be installed on a server. This means that the certificate is valid only if the site is accessed using the physical machine name (webxx.cern.ch/sitename) instead of the logical one (sitename.web.cern.ch/sitename). The redirector behind cern.ch takes care of the correct translation but this will expose the physical machine name that may change with time. In this case it is essential to use hyperlinks of the type https://cern.ch/sitename/xxxx that are guaranteed to be valid forever.
Disabling normal http:// access
All pages stored on the central Web servers are always accessible using both http:// and https://. This means of course that you can use https:// instead of http:// but also that your users can use http:// instead of https://, therefore using a non-secure connection where you had wanted to do so. Even if this is a non-problem as it is unlikely that users may do that, you can disable http:// on a per-page basis using a simple ASP script.To do so, you should give your document the *.asp extension and then type in, at the beginning of its body something like:
"ON" Then
SSLUrl = "https://www.cern.ch" + Request.ServerVariables("URL")
If LCase(Right(SSLUrl, 12)) = "/default.asp" Then
SSLUrl = Left(SSLUrl, Len(SSLUrl)-11)
End If
QS = Request.ServerVariables("QUERY_STRING")
If Len(QS) > 0 Then
SSLUrl = SSLUrl + "?" + QS
End If
Response.Redirect SSLUrl
Response.End
End if
%>
The script above uses the variable Request.ServerVariables ("HTTPS") that returns "ON" if the request came in through secure channel (SSL) or it returns OFF if the request is for a non-secure channel. Instead of denying the user access to the document, the browser is automatically redirected to the same page with https://SSL can also be used together with X509 client certificates. This is not currently supported by the central web services because there is no client certificate infrastructure available in CERN.
Note: You can also enforce the usage of SSL by changing the Directory Attributes of the web site from the CERN Web Registration site. This has the advantage that all documents in the directory tree is protected.
END

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |