SSL & "The page cannot be displayed"

T

Tyler Style

Hullo folks! I'm at the end of my tether for this sucker. I keep getting
users with this message for the site
https://www.kinotox.net/kino/application.htm. However, it's not ALL users -
just a few. They click on a button from
http://65.110.86.247/welcome-all.asp to get to this page, and for most it
works just fine. But a few get the old standby:

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.

....blah blah blah...
Cannot find server or DNS Error
Internet Explorer
Happens every time these few users try to acces it using the button, or
even just via pasting the URL into the address bar. It is a machine-related
problem, as they can access this just fine if they use another machine. It
is probably an internet settings/OS problem as well, as the same behaviour
is displayed in Firefox on these machines.

This error doesn't happen for every SSL site, either. Online banking
sites and Windows Update work fine.

I've found countless things to try fixing, but so far none of them have
worked. Here's a list:

* Installing all updates, hotfixes, etc.
* Updating network drivers.
* Verified time & date settings on computer were correct.
* Verified that IE had 128bit encryption.
* Shutting down all other software while trying to access site.
* Shutting off Windows Firewall.
* Shutting off IE Popup Blocker.
* Setting IE security settings to Low.
* Deleting IE cookies, passwords, files, history and temp files.
* Deleting/editing HOSTS file.
* Reset security settings, trusted sites and zones to defaults, low, etc.
* Resetting/fiddling settings for Javascript, SSL2/3, TLS, etc.
* Disabling 3rd party extensions in IE.
* Creating a new user profile and trying to access the page
* Spyware & virii scan.
* Disabling/uninstalling antivirus.
* Reset corrupted winsock stack: netsh winsock reset.
* Disable check for Server Certificate Revocation in the Advanced Options
Tab of Internet Explorer.
* Shutting off all startup items and trying again.
* Turning on Windows Firewall and explicitly enabling port 443.
* Checking NAV settings.
* Reregister connectivity dlls: regsvr32 softpub.dll, urlmon.dll, etc.
* Ensure all sys files are intact: sfc /scannow.
* Removing all hotfixes and service packs.
* Removing all programs except the basics.
* Reinstall IE.
* Boot from XP disc and select install, then repair existing Windows (repair
installation).
* Checking to ensure that the Local Security Settings/Local
Policies/Security Options "System Crypto: Use FIPS..." is disabled.

As you can see, I've been trying!!! Still no joy in mudville, though.
And I'm not the only person, either - for example:
http://www.tlccreations.com/help.html has put up a disclaimer about it, as
have a couple other websites (I talked to tlccreations' webmaster, and she
is just as adrift as I am, alas).

Anyone have a clue they could spare me???

Tyler (e-mail address removed)
 
R

Robert Aldwinckle

Tyler Style said:
Hullo folks! I'm at the end of my tether for this sucker. I keep getting
users with this message for the site
https://www.kinotox.net/kino/application.htm. However, it's not ALL users -
just a few. They click on a button from
http://65.110.86.247/welcome-all.asp to get to this page


But why do they have to use an unpublished alias to get there? <eg>

Have you asked them for their DNS addresses so you can
see what *their* DNS does with a normal request to your site?

E.g. just ask them what they see if they enter, in a command window:

nslookup www.kinotox.net

If that doesn't help explain the symptom a packet trace would.


HTH

Robert Aldwinckle
---
 
T

Tyler Style

A damn fine suggestion! Thank you! I had used ntstat and ping, but not
nslookup. I am not well educated on networking topics, alas. nslookup
www.kinotox.net produces a DNS request timeout on the problematic machines,
whilst the functioning machines on the same network give me a proper
name/address pair. I finally have a decent handle on the problem!!! I am
so VERY grateful to finally have a clue here. I shall call up our ISP and
see if they can't help troubleshoot the issue (unless you have any more good
advice for me!).

Thanks again!
Tyler
 
T

Tyler Style

Well and good! This has resolved our intranet issues - we manually edited
the HOSTS and LMHOSTS file to redirect appropriately. Oddly enough, it
wouldn't work unless BOTH files had been edited.

Now I just need an outside user to test it out with, and see if things
work.

Tyler

Tyler Style said:
A damn fine suggestion! Thank you! I had used ntstat and ping, but not
nslookup. I am not well educated on networking topics, alas. nslookup
www.kinotox.net produces a DNS request timeout on the problematic
machines, whilst the functioning machines on the same network give me a
proper name/address pair. I finally have a decent handle on the
problem!!! I am so VERY grateful to finally have a clue here. I shall
call up our ISP and see if they can't help troubleshoot the issue (unless
you have any more good advice for me!).

Thanks again!
Tyler
 
R

Robert Aldwinckle

Tyler Style said:
A damn fine suggestion! Thank you! I had used ntstat and ping, but not
nslookup. I am not well educated on networking topics, alas. nslookup
www.kinotox.net produces a DNS request timeout on the problematic machines,
whilst the functioning machines on the same network give me a proper
name/address pair. I finally have a decent handle on the problem!!! I am
so VERY grateful to finally have a clue here. I shall call up our ISP and
see if they can't help troubleshoot the issue (unless you have any more good
advice for me!).


While they are sorting it out you could add a lookup override
in your HOSTS file.


Good luck

Robert
---
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top