We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

SSL Secure port 8443 not working in some clients' browsers (Page cannot be displayed)

psk1
psk1 asked
on
Medium Priority
2,549 Views
Last Modified: 2012-08-13
I have a website which is using port 80 for HTTP and port 8443 for SSL/HTTPS.  Most of my remote users are able to access the secure pages fine (https://mydomain.com:8443/securedirectory/securepage.aspx).  At least two so far have reported that they are unable to access the secure pages, and instead get a "page cannot be displayed" error.

I am wondering what might cause this rare issue, and of course how to resolve it.  I've tried it myself on 5 computers, and have not been able to replicate the issue.  The users reporting the error are using XP and Internet Explorer.  Is there something about port 8443 that isn't letting the page get to some clients?

Using IIS 5 on Windows 2000 Server.

Michael
Comment
Watch Question

Top Expert 2007
Commented:
Most likely answer is that the affected clients are behind a firewall that does not allow outbound traffic on port 8443 - this is *not* a normally recognized port for SSL and many firewalls will block suspicious traffic.

Dave Dietz

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
That would make sense -- aside from 443, are there other "normally recognized" SSL ports?
Top Expert 2007

Commented:
C:\windows\system32\drivers\etc\services contains all the well known ports that are generally recognized (open it in notepad and take a look).

443 is the only recognized port for HTTPS.
444 and 4443 are occasionaly considered alternatives but there is no offical recognition of this by the IETF.

Depending on what's blocking the end users they may simply be out of luck, although they may be able to poke through on a different port below 1024 - most router/firewall appliances won't let this happen but it is much more likely to work below 1024 than above it.

Dave Dietz

Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.