Solved

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

Posted on 2006-10-27
3
1,534 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
0
Comment
Question by:psk1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 34

Accepted Solution

by:
Dave_Dietz earned 500 total points
ID: 17824419
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
0
 
LVL 2

Author Comment

by:psk1
ID: 17824450
That would make sense -- aside from 443, are there other "normally recognized" SSL ports?
0
 
LVL 34

Expert Comment

by:Dave_Dietz
ID: 17824465
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

0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
can not add ASP.NET to IIS 8 73
Ways to scan an IIS if 'directory browsing' has been disabled 3 141
Hide http port number 5 63
Exchange 2013 certificate error 3 39
Here are the symptoms: You start receiving calls from users that one of your legacy web apps isn't coming up, so you log into your IIS 5 server to check it out.  When you pull up the services, you notice that the WWW Publishing service isn't runn…
If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
In an interesting question (https://www.experts-exchange.com/questions/29008360/) here at Experts Exchange, a member asked how to split a single image into multiple images. The primary usage for this is to place many photographs on a flatbed scanner…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question