Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

on premise exchange 2013 behind sonicwall tz215 with no external owa access

I've got a new on premise exchange 2013 setup behind a sonicwall tz215. Mail is flowing in and out, and https://mail.domain.com/owa works internally, but not externally. DNS appears to be corrrect as everywhere I can think of to check resolves to the proper external IP. As for the sonicwall, I just ran the wizard once for mail server, and once for web server to open the needed ports. I also disabled external web management and set the default http and ssl ports to 81 and 4430 respectively. I can't for the life of me figure out which I can't access owa externally. I believe it may be hampering the autodiscover record process as well, as autodiscover works internally but not externally. A records are in place and correct with the domain host. A proper cert from godaddy is in place and installed, and as I said, mail flows just fine. I don't think its an IIS issue since I can open the site internally, so I'm really leaning towards the firewall. Any suggestions at all would be greatly, greatly appreciated.
0
sdholden28
Asked:
sdholden28
  • 2
1 Solution
 
suriyaehnopCommented:
On your public DNS, make sure there a records for mail.domain.com and point to external IP address of your sonicwall.
- say mail.domain.com point 202.141.2.1

From your sonicwall, configure NAT (Network Address Translation) to translate 202.141.2.1 to your Microsoft CAS server.

I think your network engineer able to help you with this.
0
 
sdholden28Author Commented:
I ended up contacting sonicwall support since the support agreement is still active, and after double verifying everything else. Sonicwall engineer agreed that the config was good, but packet capture showed dropped packes and no traffice for the http/https rules. He deleted the rules created by the wizard and recreated them. He also gave the new rules highest priority. This resolved the issue.
0
 
sdholden28Author Commented:
Only one other solution was posted, which had already been done and clearly stated in the question. I resolved the issue myself.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now