I am new here and have limited experience of IIS7 & OWA so forgive me if my questions sound amateurish.
System : Server 2008 SBS (with Exchange 2007)
Problem : No Access to OWA or Remote externally.
Observations :
1. I have no instance of OWA or Remote in the Default Web Site in IIS these are in the SBS Web Applications Site - should OWA & Remote be in Default Web Site?
2. I can access the sites within Default Website from an external computer but this has to be done via the IP address e.g. xxx.xxx.xx.xxx/application
3. If I type my IP address into browser from an external computer it immediately shows the IIS7 screen which says to me there is nothing between my ISP & Router blocking access to the server.
I have tried everything I know to resolve this and have ensured that the firewall has the relevant ports accepting and with me being able to get the IIS7 screen up after typing in IP address I am assuming the problem is within IIS unless there is something I am missing.
If the Exchange setup has put OWA in the SBS Web Applications site, then that's probably what it was designed to do for SBS. It sounds like you have your default web site listening for SSL traffic on port 443 instead of the SBS Web Applications site. I don't have SBS, so I don't know if that is the default setting or not. Anyway, if you do not have anything in the default web site that you want to access via SSL, remove the SSL port 443 setting on that, and add it to the SBS Web Applications site. Unfortunately (since it wouldn't make sense anyway), you can't have it on both.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Teh Default Website does not have 443 https enabled on any of the applications in there.
I was contemplating adding an OWA application to the Default Web Site, pointing to the OWA folder and seeing what happens then but I am concerned that it may impact on other areas.
Right, I had seen that on this forum, do I just put that command into a command prompt or is there somewhere else I have to put it? (told you I was a bit of a cabbage)
It has to go into the Exchange Management Shell. An ordinary CMD prompt will not understand it. There is a kind of 'super-CMD-prompt' available on Server 2008 (and it can be installed on 2003) called PowerShell. The Exchange Management Shell is a PowerShell (a shell is like an instance of a command prompt) with Exchange management extensions loaded. It is an extremely powerful and versatile concept (you can create reports, combine commands, and even write code in it), but it comes with a steep learning curve, so you needn't feel like a cabbage.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________
Unfortunately doing this crashed my 3rd Party WebApp and we had to call them in to create a new website in IIS we live and learn!
Have tried everything to connect externally but cannot get to teh OWA or Remote. I can see the IIS7 screen when I type in IP address from external machine so I must be getting through to the server but it looks like a setting within IIS7 is blocking me, maybe it's related to trusts or security it seems really odd.
It may be the case that you have Host Header names configured for one or more of the web sites on the server. This is certainly likely if there is more than one site on the same server, and you hope to be able to use them all on the standard ports (80 and 443). If you have a host header name configured for the site with OWA in, then you won't be able to access the site unless you use the correct host name in your browser bar.
_____________________________
Lee. ___________________________________
Outlook Web Access for PDA and WAP: www.leederbyshire.com ___________________________________