DISQUS

Anonymous · 5 years ago

If you're being assigned an IP via DHCP by your ISP, it is likely to change if for some reason you ever have to power your PIX down (as I had to do several times this summer due to violent thunder storms).

So wouldn't you be better off setting up your NAT using "PORT" instead of the DHCP address? Then you can sign up for a free Dynamic-DNS service (www.no-ip.com for example) which will automatically track your IP changes, and then you can ftp or vnc in by a name you create.

Also, be sure to use strong passwords, or even better, 2-factor authentication or certificates, if you're going to open up access to common ports on your firewall.

Just my 2-cents-worth.

Thanks.

Headhunter · 5 years ago

If you are running a FTP/Web/Email server behind it why not just get a static IP address from the ISP and then the PIX configuration will work everytime after an unplanned/planned outage.

Anonymous · 5 years ago

The extra $30.00 a month I would have to pay my ISP so I can have static IP's gets applied to shoes or clothes or something else for my kids!

But yes, you are right, if you have the money and you're running a high-traffic FTP or web site then static IP's are definitely the way to go.

Anonymous · 3 years ago

I've implemented the multiple statics and port forwarding using one public IP as you've said but for some reason the machines cannot go out to the Internet. There are access lists allowing this but still no luck. See the below and tell me what you think.

Static (dmz1,outside) tcp 200.100.100.76 80 192.168.250.50 80 netmask 255.255.255.255 0 0
Static (dmz1,outside) tcp 200.100.100.76 21 192.168.250.51 21 netmask 255.255.255.255 0 0

Access-list dmz1 permit tcp host 192.168.250.50 any
Access-list dmz1 permit udp host 192.168.250.50 any

Access-list dmz1 permit tcp host 192.168.250.51 any
Access-list dmz1 permit udp host 192.168.250.51 any

Access-list acl-out permit tcp any host 204.100.100.76 eq 80
Access-list acl-out permit tcp any host 204.100.100.76 eq 21