Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Just got my hands on this Sonicwall Pro 2040 Firewall, we actually migrated from Fortigate.

After setting up DDNS successfully I can log into the firewall from the internet through https : //firewall.dyndns. org, so what I'm trying to do next is to be able to access a business application on a server behind the firewall that runs IIS. Such a thing I did easily using virtual IP on Fortigate, previously I could access it using such URLs: https :// firewall.dyndns. com:3277/BusinessApplication

But with this new firewall I'm facing troubles doing the same, after setting up my NAT policies and access rules correctly "As I believe" it still wouldn't access to https://firewall.dyndns.com:3277/BusinessApplication

Below are what I did:

1- Created an Address Object with the Server having the business application: Name: Server123 Zone Assignment: LAN Type: Host IP Address:

2- Created Firewall Service: Name: BusinessApplication Protocol: TCP(6) Port Range: 3277 - 3277

3- Created the NAT Policy: Original Source: Any Translated Source: Original Original Destination: WAN Primary IP Translated Destination: Server123 Original Service: BusinessApplication Translated Service: Original Inbound Interface: Any Outbound Interface: Any

4- Created Firewall Access Rule: Allow From Zone: WAN To Zone: LAN Service: BusinessApplication Source: Any Destination: WAN Primary IP Users Allowed: All Schedule: Always on

This and a couple of many tries I've done doesn't seem to be working.

I'd appreciate your help if you could.


share|improve this question
I have an NSA3500 and to be honest, I never get it right the first time. Since you're running the Enhanced OS, you should have a builtin packet capture utility. Run a capture and try and find out where it's dropping the packets. In addition to that, you can also run a packet capture on your server to see if the packets are getting to your server and maybe it's an IIS config error, or a Windows Firewall issue, etc etc.. –  Safado Apr 18 '12 at 17:28
As a side note, I just checked some of my NAT rules and I had to put X1 (the WAN) interface for the inbound. Having "ANY" wouldn't work. –  Safado Apr 18 '12 at 17:32
I Tried changing the Interface for Inbound to "WAN1" but it does work as well. –  user117985 Apr 19 '12 at 7:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.