Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Outlook Web Access 2
- Thread starter spc1
- Start date
-
1
- Thread starter
- #3
-
1
- #4
- Thread starter
- #5
Im sure, Im testing it now. im putting in I just get page cant be displayed. Do i need to do anything in DNS or IIS?
What's the rest of your network config? Is there a firewall doing NAT between your server and the internet? If so, is it set to forward SSL (port 443) as well as HTML port 80 traffic to your server?
Generally, the recommended practice with OWA is to have external DNS set to resolve the host mail.domain.com to your public IP. The SSL cert used should be generated with that identity rather than just the IP address.
Generally, the recommended practice with OWA is to have external DNS set to resolve the host mail.domain.com to your public IP. The SSL cert used should be generated with that identity rather than just the IP address.
ISS asp.net both need be up and running for owa to work
gunthnp from
gunthnp from
- Thread starter
- #8
when you go int exchange system manager is the http vitrual server started
gunthnp from
gunthnp from
- Thread starter
- #11
HTTP virtual server is started, When i type in i get page can not be found and when i type in i get page can not be displayed
Are you sure there isn't some sort of port-forwarding problem. Your IIS is clearly working given that you said it works internally, but the errors you describe sound like your outside router isn't touching the IIS server at all.
If you go home and telnet to:
telnet 195.147.x.x 80
and it manages to connect () and you then type:
GET
and it returns back html code like:
--------------------------------------------------------
HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.0
Date: Tue, 22 Mar 2005 23:05:59 GMT
Content-Type: text/html
Content-Length: 87
<html><head><title>Error</title></head><body>The parameter is incorrect. </body>
</html>
Connection to host lost.
--------------------------------------------------------
then you know it's hitting the IIS server, if you get nothing or the port seems to be closed off, then it's most likely a problem at the edge of your network.
You can also, from your LAN, go to and do the "Shields UP!" test, it can tell you which ports are open and forwarding on your router.
If you go home and telnet to:
telnet 195.147.x.x 80
and it manages to connect () and you then type:
GET
and it returns back html code like:
--------------------------------------------------------
HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.0
Date: Tue, 22 Mar 2005 23:05:59 GMT
Content-Type: text/html
Content-Length: 87
<html><head><title>Error</title></head><body>The parameter is incorrect. </body>
</html>
Connection to host lost.
--------------------------------------------------------
then you know it's hitting the IIS server, if you get nothing or the port seems to be closed off, then it's most likely a problem at the edge of your network.
You can also, from your LAN, go to and do the "Shields UP!" test, it can tell you which ports are open and forwarding on your router.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
