<div>
You're basically double NATing from your explanation. Try to get your router running in Bridge mode, so the IP is directly applied at the Sonicwall. Otherwise, you'll also have to set the rule up in your ADSL router as well. (NAT Public IP to SonicWall WAN port IP in Router, NAT Sonicwall WAN Port IP to Exchange server in SonicWall config). You also will want to limit the ports in the NAT rule to ports 443 and 25, since those are the ones that Exchange needs on the Internet.
</div>

<div>
Hi Rupert, 
 
It could be double NATing but we'd need to see more details. You could have issues with a 443 conflict. On the surface it isn't obvious but if you have remote management enabled (443 enabled on the WAN Interface) while opening 443 on the WAN &gt;&nbsp;LAN side. I said it is not terribly obvious because you'd typically think to look for open inbound ports on the WAN &gt;&nbsp;LAN Zone not actually realizing management services (ping, management, etc.) run on WAN &gt;&nbsp;WAN. The way to remedy this is to go to System &gt;&nbsp;Administration and change the port next to HTTPS Port: under Web Management Settings. 
 
Let me know how it goes!
</div>

<div>
Thanks Guys, 
 
The ADSL router is locked by the service provider and can't be edited. 
However, traffic from the internet (via the DSL router) is arriving at the SonicWALL router. 
I realised this, when the admin page of the SonicWALL was displayed initially. 
 
I changed the SSL port under Web Management settings for the SonicWall, and the admin page is no longer displayed. 
 
This tells me that the 443 traffic is reaching the SonicWall, but not being relayed through to the Exchange server on 10.0.0.27. 
 
Are the access &amp;&nbsp;NAT rules above correct?
</div>

<div>
Thank you Diverseit, 
 
I've deleted the NAT policy and used the wizard to setup a new set of NAT policies for publishing the server. 
 
The wizard only created 2 x NAT rules, and still did not work. 
I logged a call with SonicWALL and we've added a 3rd rule with their assistance. OWA is working ;-) 
 
I encountered a strange problem, possibly a bug in the firmware; 
Upon adding NAT rules, &quot;custom rules&quot; option, 
Upon moving a rule to position 1, the SonicWALL deletes the rule without a prompt. 
I tried a couple of times, the same problem occurred. 
 
I have another server to publish on a different range 192.168.2.x &nbsp;(SonicWALL on 10.0.0.x) 
I've setup a static route, and the SonicWALL can ping the server successfully. 
Setting up the same 3 x NAT rules for this server, doesn't work. &nbsp; 
 
Any ideas?
</div>

<div>
Strange. The wizard should always add three rules inbound, outbound and loopback. Did you have the option not to select loopback? 
 
You can leave the priority of the NAT Policies default. I'm not sure I understand the auto-delete NAT policy. What NAT policy are you trying to create that the wizard hasn't already? 
 
Regarding the other server, I'd love to help but it is outside of the scope of this question. Please open a new question and I'll hop on that and answer it for you. Experts Exchange likes to keep a specific question/specific answer so that when users try to find issues they find the answers instead of offshoots, etc. I hope you understand. :)
</div>

<div>
<div class="content wysiwyg-content">
Hi Guys, 
 
I have difficulty setting up an OWA access rule in SonicWall. 
 
I have SonicWall WAN connection (192.168.1.4) 
.. coming from an ADSL router translating internet traffic to 192.168.1.4 -&gt; SonicWall 
 
LAN connection on 10.0.0.240 / 24 
Exchange server on 10.0.0.27 / 24 
 
I can't get the access rule / NAT to work: 
 
ACCESS RULE: 
From: &nbsp;WAN 
To: &nbsp;LAN 
Source Port: &nbsp;Any 
Service: &nbsp;Exchange 2013 (http &amp;&nbsp;https) 
Source: &nbsp;Any 
Destination: &nbsp;WAN Interface IP 
 
NAT RULE: 
Original Source: &nbsp;Firewall Subnets 
Translated Source: &nbsp;WAN interface IP 
Original Destination: &nbsp;WAN interface IP 
Translated Destination: &nbsp;Exchange Server (10.0.0.27) 
Original Service: &nbsp;Exchange 2013 (http &amp;&nbsp;https) 
Translated Service: &nbsp;Original 
Inboud Interface: &nbsp;Any 
Outbound Interface: &nbsp;Any 
 
I've tried other configurations as well, but still no joy. 
 
The log monitor has also not been really helpful, perhaps I am using wrong log-filter?
</div>
</div>

Hi Guys,

I have difficulty setting up an OWA access rule in SonicWall.

I have SonicWall WAN connection (192.168.1.4)
.. coming from an ADSL router translating internet traffic to 192.168.1.4 -> SonicWall

LAN connection on 10.0.0.240 / 24
Exchange server on 10.0.0.27 / 24

I can't get the access rule / NAT to work:

ACCESS RULE:
From:  WAN
To:  LAN
Source Port:  Any
Service:  Exchange 2013 (http & https)
Source:  Any
Destination:  WAN Interface IP

NAT RULE:
Original Source:  Firewall Subnets
Translated Source:  WAN interface IP
Original Destination:  WAN interface IP
Translated Destination:  Exchange Server (10.0.0.27)
Original Service:  Exchange 2013 (http & https)
Translated Service:  Original
Inboud Interface:  Any
Outbound Interface:  Any

I've tried other configurations as well, but still no joy.

The log monitor has also not been really helpful, perhaps I am using wrong log-filter?

Setting up OWA access rule in SonicWall

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.