<div>
I thought that this would be the best avenue, but I was unsure if I could use the IP address on an ssl cert.<br />
<br />
Cheers!!
</div>


I thought that this would be the best avenue, but I was unsure if I could use the IP address on an ssl cert.

Cheers!!

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
I have a client with some SSL certificate issues.<br />
<br />
I will list some items relevant to this question:<br />
<br />
Windows 2003 server with Remote Web Workplace (RWW) &amp;&nbsp;exchange<br />
MX record from webhost pointing to the windows 2003 server for mail traffic<br />
Website hosted on remote server<br />
domain name points to webhost offsite<br />
<br />
So every time my client needs to access Remote Web Workplace they type in www.domain.com/remote&nbsp; which is then redirected (using a php script located on the offsite webserver) to the WAN IP address of the (no domain name only IP) windows 2003 server so they end up having 123.123.123.123/remote in their address bar (obviously they can type in 123.123.123.123/remote and still access RWW). Now the problem is that every time that they access RWW they receive an SSL error im thinking this is due to the certificate being used is for domain.com not 123.123.123.123.<br />
<br />
Is it possible to have a DNS record that will show that domain.com is one IP and domain.com/remote is another IP? This way the certificate will do its job.<br />
<br />
Cheers.<br />

</div>
</div>


Hi,

I have a client with some SSL certificate issues.

I will list some items relevant to this question:

Windows 2003 server with Remote Web Workplace (RWW) & exchange
MX record from webhost pointing to the windows 2003 server for mail traffic
Website hosted on remote server
domain name points to webhost offsite

So every time my client needs to access Remote Web Workplace they type in www.domain.com/remote  which is then redirected (using a php script located on the offsite webserver) to the WAN IP address of the (no domain name only IP) windows 2003 server so they end up having 123.123.123.123/remote in their address bar (obviously they can type in 123.123.123.123/remote and still access RWW). Now the problem is that every time that they access RWW they receive an SSL error im thinking this is due to the certificate being used is for domain.com not 123.123.123.123.

Is it possible to have a DNS record that will show that domain.com is one IP and domain.com/remote is another IP? This way the certificate will do its job.

Cheers.


SSL certificate

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.

SSL / HTTPS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.