Re: Network/Routing Question
- From: "Cliff Galiher" <cgaliher@xxxxxxxxx>
- Date: Wed, 4 Jun 2008 16:29:11 -0600
"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4BB952B0-2E39-4909-8371-9A1B8DFB9ED4@xxxxxxxxxxxxxxxx
First, thank you all for responding. I thought this would be easy, but IIt is possible to install OWA onto another website, and yes it is tricky. And yes, I've killed OWA and SBS doing so. :) I've also done it successfully. If you are 'satisfied' with the current solution, stick with it. :)
should have known better.
a) Dyn-DNS - I have used this in the past, the problem with this method is
that I can get it directed with no problem - the issue is that it still shows
remote.company.com in the address bar once logged in (create new message).
This is kinda pointless, as that's that what I'm looking for.
b) Internal DNS: Yes, I can push a host file - that was my next course of
action. I just thought I could do it another way - heck, if my Linksys WRT54g
with dd-wrt firmware at home had the ability - figured the expensive Cisco
router or Windows server could help me out - lol. That's where Linux rules
still I guess
Again, objective is to have external dns settings to point to various items
within IIS.
Currently:
remote.company.com/remote - takes you to Remote Workspace
remote.company.com/exchange - takes you to exchange.
all working off Default Website.
Since I am unsure of a way to install OWA to another website, other than
Default and I don't want to destroy Exchange or SBS (Horray for my ignorance!)
I have mapped webmail.company.com to the Default website as well.
I'm hoping no problems will occur with anything else by doing this.Nope. This is a fairly standard way of resolving this problem.
Baring no one can think of a better way.If your *default* website use remote.domainname.com, and you are thinking of adding a header to the default website then no, this cannot be done. The default site cannot have a header in the SBS world. Many of the internal scripts rely on the default site, and a header prevents them from properly accessing some of the IIS internals they need.
Looking at
Article: http://support.microsoft.com/kb/555053
Article: http://blogs.technet.com/jhoward/archive/2005/09/06/410185.aspx
(similar thoughts)
Could I not:
* Add remote.company.com has another header
And if you create a new site and add a header then you still have to make the default site accessible for the redirect. So, for example, assuming you create a new virtual directory for remote.domainname.com and have both it and webmail redirecting to the default site that you now call 'company.domainname.com' then all three sites have a /exchange and /remote subdir with them. Essentially you'd increase complexity without any gain.
* Find someone who know's more about ASP than I and can write code that willIf you are already redirecting webmail to the default website then what can ASP do that isn't already being done?
check which host header was referenced and redirect based on that.
If you are considering adding this ASP code to the default website then, again, you hit the problem outlined above with breaking various SBS components. Whether that filtering is happening by ASP or by IIS before the request is passed to ASP doesn't matter. You just can't monkey with the default site much in SBS.
* In addition, have all exchange requests on port 80 redirect to https (443)Yes, this can be done. You just change your redirect on the webmail virtual directory to include https and the browser receiving the redirect will do the rest.
once a certificate is in place
-Cliff
.
- Prev by Date: Re: OT - Licensing
- Next by Date: Re: RWW via VPN only partially working
- Previous by thread: Re: Network/Routing Question
- Next by thread: Re: Network/Routing Question
- Index(es):
Relevant Pages
|
Loading