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

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

Port forwarding... twice?

Here is the situation:

Internet---> Sonicwall ---> LAN ---> PIX ---> Webserver

Sonicwall port forwards port 443 to the PIX over the LAN.  The PIX port forwards port 443 to the webserver.  The webserver is unreachable from the Internet.  I'm not sure exactly why this isn't working but I have a feeling this isn't going to work.  Does this have to do with the fact that the client machine uses a randomly high numbered port when making connections and as a result this won't translate properly from the Sonicwall to the PIX?

What options do we have on making the Webserver reachable from the Internet going through two firewalls?

Thanks!

0
lighthousekeeper
Asked:
lighthousekeeper
1 Solution
 
briandunkleCommented:
Do both firewalls give out DHCP addresses? If so, what ranges are they using?
 How are you doing the forwarding? i.e. what addresses are you using at each point?

I don't know about putting SSL specifically through two firewalls...might not be possible but we can certainly try.
0
 
briandunkleCommented:
By which ranges I mean (outside address=?) <--> (internal network 1 range) <--> (deeper network 2 range)

Any chance of using a dumb switch instead of a firewall as the second, specifically meaning using IP addresses gotten from the FIRST firewall and just passed through? Actually a smarter switch should be able to do this, if you give machines in the inner circle, at least, static IPs.

(first firewall --> 192.168.0.2-20 <-- 2nd firewall --> 192.168.0.21.40 static

Dunno if I'm describing this well, but if you do static you should be able to do this.
0
 
briandunkleCommented:
sigh, I mean 21-40, not 21.40
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
sykojesterCommented:
I'm guessing the SonicWall is acting as a NAT (Network Address Translation) and not a passthru device.  The PIX more than likely is doing NAT.

You cannot double NAT. You can only translate an IP address to once. i.e.  Internet IP of 1.2.3.4 -> SonicWall passing 10.10.10.2 to the PIX which is handing out 192.168.1.2 to your webserver.

Eliminate either the SonicWall or the PIX from the equation and everything should work just fine.
0
 
lighthousekeeperAuthor Commented:
Yep, I think you are right--cannot double NAT--they are both performing this function.  I would assume if the PIX was routing instead of acting as a NAT/firewall role that I would be able to put the route on the Sonicwall and then port translate to the routed network?

0
 
andyalderSaggar makers bottom knockerCommented:
Double NAT should work, here's a thread with several people who have got it working, If you're using NAT for inbound traffic then anyone accessing your site from behind a NAT firewall will be using double NAT because the address is translated at their firewall and at yours.

http://episteme.arstechnica.com/groupee/forums/a/tpc/f/469092836/m/4680930245

I would try testing with HTTP rather than HTTPS and it may also help to seperate the two NAT devices with a router.

0

Featured Post

Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

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