<div>
Thanks for the reply. I tried that and it still crashes. In the binding port I also changed to 444, I can telnet in but it does not work over the web.<br />
<br />
telnet public ip 444
</div>


Thanks for the reply. I tried that and it still crashes. In the binding port I also changed to 444, I can telnet in but it does not work over the web.

telnet public ip 444

<div>
Found the issue, I was putting the web url in wrong.<br />
<br />
<a href="https://domainname:444/directory/" rel="ugc">https://domainname:444/directory/</a>&nbsp;is what it needed to be.<br />
<br />
becraig thanks for help.
</div>


Found the issue, I was putting the web url in wrong.

https://domainname:444/directory/ [https://domainname:444/directory/] is what it needed to be.

becraig thanks for help.

<div>
<div class="content wysiwyg-content">
I have a 2008 r2 server running Exchange in HyperV, on the host server its also running IIS website. Under the default website there are two directories, patient and patientEP. I need to be able to access the second directory from outside through a web browser over an HTTPS. &nbsp;Currently port 443 is being used by Exchange, so I have to use an alternate port for the SonicWALL. I do not mind the url using 444 as it will just be a hyper link<br />
<br />
ISP - SonicWALL - Server<br />
<br />
If I enable binding on the default website for port 443 the application crashes. I do have a wild card SSL installed.
</div>
</div>


I have a 2008 r2 server running Exchange in HyperV, on the host server its also running IIS website. Under the default website there are two directories, patient and patientEP. I need to be able to access the second directory from outside through a web browser over an HTTPS.  Currently port 443 is being used by Exchange, so I have to use an alternate port for the SonicWALL. I do not mind the url using 444 as it will just be a hyper link

ISP - SonicWALL - Server

If I enable binding on the default website for port 443 the application crashes. I do have a wild card SSL installed.

Server 2008 r2 Access to website in iis

Cloud computing, also known as on-demand computing, is a kind of Internet-based computing where shared resources and information are provided to computers and other devices. It is a model for enabling ubiquitous, on-demand access to a shared pool of configurable computing resources. Cloud computing and storage solutions provide users and enterprises with various capabilities to store and process their data in third-party data centers, relying on sharing of resources to achieve coherence and economies of scale.

Cloud Computing

The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, hypermedia information systems. Hypertext is structured text that uses logical links (hyperlinks) between nodes containing text. HTTP is the protocol to exchange or transfer hypertext. HTTP functions as a request-response protocol in the client-server computing model. HTTP is designed to permit intermediate network elements to improve or enable communications between clients and servers. HTTP is an application layer protocol designed within the framework of the Internet Protocol Suite; it presumes an underlying and reliable transport layer protocol.

HTTP Protocol

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.