nat computer does not access internet

[nlbakos]

i have configured several server websites and ftp to use static nat.

i can access these computer via there webaddress and ip's both inside and outside the network.

however when i go to the actual computer lets say the FTP server and want to go somewhere on the internet (www.google.com) the server does not find the web page. if i back to the firewall and uncheck Add Automatic address translation rules. the computer access the internet just fine.

i want my webservers and ftp to beable to access the internet. what rule or rules do i need to apply to make this happen?

[melipla]

Originally Posted by nlbakos

i have configured several server websites and ftp to use static nat.

Have you tried manual nat?

Originally Posted by nlbakos

i can access these computer via there webaddress and ip's both inside and outside the network.

I'm guessing the NAT/public address is the "webaddress" and the private address is the "IP's"? Just want to make sure you can use both, at least internally.

Originally Posted by nlbakos

however when i go to the actual computer lets say the FTP server and want to go somewhere on the internet (www.google.com) the server does not find the web page. if i back to the firewall and uncheck Add Automatic address translation rules. the computer access the internet just fine.

Are there any logs in smartview tracker? You can also try doing a "fw monitor" on the firewall to see if anything is happening. I'd also look for anti-spoofing messages.

Originally Posted by nlbakos

i want my webservers and ftp to beable to access the internet. what rule or rules do i need to apply to make this happen?

Depends on when your NAT kicks in as to whether or not you use the private IP or the public IP in the rule to allow outbound traffic. You should see drops in the logs which will tell you which IP the firewall sees.

[MarioL]

From your description my guesses are:
1 - The Public addresses assigned via static NAT are not being routed to the firewall or the firewall isn't "arping" for them properly
2 - You are using a wrong address on the automatic NAT
3 - There is a rule that conflicts with part of the automatic NAT