<div>
https is already port 443. Therefor you don't need to add the port behind the url.<br />
So the url is <a href="https://servername" rel="ugc">https://servername</a>
</div>


https is already port 443. Therefor you don't need to add the port behind the url.
So the url is https://servername [https://servername]

<div>
Still get the same error when leaving out the port number.
</div>


Still get the same error when leaving out the port number.

<div>
Check settings on Default Website using IIS manger.<br />
<br />
Check certificate is valid and also authentication is ok
</div>


Check settings on Default Website using IIS manger.

Check certificate is valid and also authentication is ok

<div>
<div class="content wysiwyg-content">
I am trying to access my server via <a href="https://servername:443" rel="ugc">https://servername:443</a>&nbsp;and get &quot;The page cannot be displayed.&quot; &nbsp;Port 443 is not blocked by the firewall. &nbsp;IIS is running (Windows 2000 server). &nbsp;What am I missing?
</div>
</div>


I am trying to access my server via https://servername:443 and get "The page cannot be displayed."  Port 443 is not blocked by the firewall.  IIS is running (Windows 2000 server).  What am I missing?

Cannot access port 443

Windows 2000 is an operating system for use on both client and server computers. It is the successor to Windows NT 4.0, and is the last version of Microsoft Windows to display the "Windows NT" designation. Four editions of Windows 2000 were released (Professional, Server, Advanced Server, and Datacenter Server) that shared a core set of features, including many system utilities such as the Microsoft Management Console. All versions of the operating system support NTFS 3.0, Encrypting File System, as well as basic and dynamic disk storage. The Windows 2000 Server family includes support for Active Directory services, Distributed File System and fault-redundant storage volumes.