Link to home
Start Free TrialLog in
Avatar of bhamguy3131
bhamguy3131

asked on

HTTP and HTTPS redirection

BY default...  I have SBS 2008 premium and a working

https://remote.domain.com/remote with a level 2 cert installed.

I also have a working ... https://remote.domain.com/owa

These exist at the core in essence.

But I want to have two HTTP URL's that redirect to these for ease.

for example.,

I want.

mail.domain.com  to go to https://remote.domain.com/owa
and  remote.domain.com to go to https://remote.domain.com.remote.

I am not super savvy in IIS or html coding or any of that mess....  

Id this can be done , it has to be SUPER easy and dumbed down. ...

Major respect to someone that can tell me an easy way to do this !
Avatar of ToBeHonest
ToBeHonest
Flag of United Kingdom of Great Britain and Northern Ireland image

Prior to doing this, have you checked out your DNS records?  mail.domain.com is most usually used to direct your incoming mail to the exchange server, just think you should consider this first but of course you may already have done that
Avatar of bhamguy3131
bhamguy3131

ASKER

ok , yes , there is a MX record already for that ... so yeah ... bad choice...

how about  

  owa.domain.com is redirected to https://remote.domain.com/owa
1) On internal dns, mail.domain.com should point to the nlp ip of remote.domain.com ?
2)  internal outlook clients should use the exchange server name as remote.domain.com
I dont know what you are asking... exchange already works fine.  Just forget about earlier comment about using mail.domain.com for owa...

Restated goal
  owa.domain.com is redirected to https://remote.domain.com/owa
 and remote.domain.com is redirected to https://remote.domain.com/remote
What you are asking for is called a Sub Domain. From what I gather, you need to do an A record setup in your IIS. There is a good article on this topic here, with the IIS info towards the bottom of the article:
http://content.websitegear.com/article/subdomain_setup.htm

Here is another article, more specific to IIS: http://www.seoconsultants.com/windows/isapi/subdomains/

Avatar of Roshan Mohammed
have you got any firewalls in between?
i think you have to put a small HTML file as the default page for each domain name to be redirected, as it is related to changing protocol from HTTP to HTTPS (actually changing the port number), and this is not related to name resolving via DNS which just converts a name string to a IP number.

the HTML source would look like this.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>Redirecting to the secured site</TITLE>
<META http-equiv="REFRESH" content="0;url=https://remote.domain.com/owa"></HEAD>
<BODY>
Optional text here.
</BODY>
</HTML>

hope it helps,
bbao
ok , so i make a notepad... call it .... redirect.htm ...  and then I place it precisely where in IIS for each site I want to redirect.  ????
they should be named "index.html" or "default.htm", or check your IIS settings for the file name of DEFAULT page.
I am not a guru for IIS AT ALLL ... i am on IIS 7.5 pack for IIS 7.0  on an SBS 2008

Can you dumb this down for me please :P
ASKER CERTIFIED SOLUTION
Avatar of bbao
bbao
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial