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 220.127.116.11/remote in their address bar (obviously they can type in 18.104.22.168/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 22.214.171.124.
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.