HBMI
asked on
OWA on exchange 2007
I can't seem to get my external owa working but it works internally. I think it is because my external IP is pointing to my edge server from my firewall and my owa is set up on my main exchange server. HELP!!!!!!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
These are my routes in my firewall. 192.168.50.11 is my CAS server and 192.168.50.28 is my edge server. Email is flowing fine but doesn't see like the OWA is getting to the CAS server.
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
no fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list in_outside permit tcp any host 66.89.65.54 eq smtp
access-list in_outside permit tcp any host 66.89.65.54 eq www
access-list in_outside permit tcp any host 66.89.65.54 eq https
access-list in_outside permit tcp any host 66.89.65.54 eq pop3
access-list in_outside permit tcp any host 66.89.65.54 eq ldap
access-list in_outside permit tcp any host 66.89.65.54 eq 522
access-list in_outside permit tcp any host 66.89.65.54 eq 1503
access-list in_outside permit tcp any host 66.89.65.54 eq h323
access-list in_outside permit tcp any host 66.89.65.54 eq 1731
access-list in_outside permit tcp any host 66.89.65.54 eq 2004
access-list in_outside permit udp any host 66.89.65.54 eq ntp
access-list allowin permit tcp any host 66.89.65.54 eq www
static (inside,outside) tcp 66.89.65.54 www 192.168.50.11 www netmask 255.255.255.255 0 0
static (inside,outside) tcp 66.89.65.54 smtp 192.168.50.28 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp 66.89.65.54 https 192.168.50.11 https netmask 255.255.255.255 0 0
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
no fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list in_outside permit tcp any host 66.89.65.54 eq smtp
access-list in_outside permit tcp any host 66.89.65.54 eq www
access-list in_outside permit tcp any host 66.89.65.54 eq https
access-list in_outside permit tcp any host 66.89.65.54 eq pop3
access-list in_outside permit tcp any host 66.89.65.54 eq ldap
access-list in_outside permit tcp any host 66.89.65.54 eq 522
access-list in_outside permit tcp any host 66.89.65.54 eq 1503
access-list in_outside permit tcp any host 66.89.65.54 eq h323
access-list in_outside permit tcp any host 66.89.65.54 eq 1731
access-list in_outside permit tcp any host 66.89.65.54 eq 2004
access-list in_outside permit udp any host 66.89.65.54 eq ntp
access-list allowin permit tcp any host 66.89.65.54 eq www
static (inside,outside) tcp 66.89.65.54 www 192.168.50.11 www netmask 255.255.255.255 0 0
static (inside,outside) tcp 66.89.65.54 smtp 192.168.50.28 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp 66.89.65.54 https 192.168.50.11 https netmask 255.255.255.255 0 0
Confirm you set the right gateway (your pix ip address) on your CAS server
Is 66.89.65.54 your IP address?
If it is there are no ports open?
If it is there are no ports open?
You can check your open port facing internet with this online tools : http://www.canyouseeme.org/
ASKER
No I made that IP up.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks for the points!
http://technet.microsoft.com/fr-fr/library/bb794751.aspx
http://blogs.technet.com/isablog/archive/2008/04/29/troubleshooting-owa-2007-publishing-rules-on-isa-server-2006.aspx