Change port of OWA
Posted 29 May 2007 - 02:55 PM
Posted 29 May 2007 - 03:10 PM
it's the same as changing the port of any other IIS website...
is there an issue with both being on port 80? i'm sure there is since you're asking..but i can't think of a terribly large one off hand...since the two servers surely have different IP's
Posted 30 May 2007 - 06:21 AM
Posted 30 May 2007 - 06:23 AM
Posted 30 May 2007 - 06:40 AM
Posted 30 May 2007 - 06:51 AM
Posted 30 May 2007 - 09:05 AM
When this is done, no website will show when I go to my email domain name, and when we try to view the OWA site from IIS and it won't load locally either.
So at this point what I thought to be the easiest path turns out to be a little more complicated than I thought. I'm not sure if I need a DNS server to process all port 80 traffic and forward it to the appropriate server and change the OWA port back to 80. If this is the case I'm out of luck because I don't know the first thing about setting up a DNS server.
Posted 30 May 2007 - 12:32 PM
Posted 31 May 2007 - 10:26 AM
We have a Business Class Time Warner Cable connection
After the modem comes a Cisco RV082 VPN Router (no VPN configured)
From the router it goes to a 24 Port 10/100 Switch
The servers are then connected to the switch
The servers are both on the same Domain: "CIS"
The webserver's name is "websrv1"
The exchange server's name is "exchangesrv1"
The servers have a static set IP address, not DHCP.
Local Network IP Addresses:
Subnet Mask: 255.255.255.0
Let me know if you need any more information. I tried to give all relevant information on network setup.
Posted 31 May 2007 - 10:29 AM
Posted 31 May 2007 - 10:33 AM
basically what i'm driving at is based on my configuration
i've got a T1 connection, with this connection i have a block of PUBLIC ip's that i can use. after the supplied router from the ISP i've got a PIX firewall...i've got OWA and a couple of other publicly visible sites hosted inside the PIX....in the PIX firewall (for all intents and purposes it's a router in this situation)...i've got a NAT rule that translates my OWA server to one of my public ip addresses and another NAT rule that translates my other public site's server address to a public ip...then in my public DNS (with my ISP...this would be where you would make the settings at godaddy)....i've got an entry for my OWA server that translates www.myowaaddress.com/exchange to the public ip that i've chosen for owa...and for the website i've got a dns entry that does the same for that ip address...then of course there's the standard access rules in the firewall that specify the traffic allowed to either of these servers once the connection is made...but the NAT rules basically tell the router that anything for this public ip goes to this server and anything for the other one goes to the other server etc...
Posted 31 May 2007 - 11:01 AM
The setup that you have makes good sense to me but I'm guessing that with my current equipment and ISP limitations that the same idea won't exactly work for me.
I will call Time Warner for sure and make sure there's no way to get another public IP without having to buy a whole other internet connection.
Posted 31 May 2007 - 11:16 AM
when you changed the port in IIS....you weren't able to get to OWA internally right? did you just type in the web address? or did you try the ip and port? (i.e. http://192.168.172.4:85)
Posted 31 May 2007 - 11:33 AM
through the forwarded domain.com:port
Publib IP Address:port
Tried previewing it locally on the exchange server in the IIS control
No matter what it would not run unless it was on port 80.
Posted 31 May 2007 - 11:58 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users