You just installed a new Web server in the DMZ that must be reachable from the Internet. You create a manual Static NAT rule as follows:
“web_public_IP” is the node object that represents the new Web server’s public IP address. “web_private_IP” is the node object that represents the new Web site’s private IP address. You enable all settings from Global Properties > NAT.
When you try to browse the Web server from the Internet, you see the error “page cannot be displayed”. Which statements are possible reasons for this?
i). There is no route defined on the Security Gateway for the public IP address to the Web server’s private IP address.
ii) There is no Security Policy defined that allows HTTP traffic to the protected Web server.
iii) There is an ARP entry on the Gateway but the settings Merge Manual proxy ARP and Automatic ARP configuration are enabled in Global Properties. The Security Gateway ignores manual ARP entries.
iv) There is no ARP table entry for the protected Web server’s public IP address.
A.
(i), (ii), (iv)
B.
(iii)
C.
(i), (ii)
D.
(i), (ii), (iii), (iv)
answer is A. Merge ARP entries, merges ARP entries not delete them.
Sean is right, correct answer is A:
“Merge manual proxy ARP configuration merges the automatic and manual ARP configurations. Manual proxy ARP configuration is required for manual Static NAT rules. If a manual ARP configuration is defined in the local.arp file and Automatic ARP configuration is enabled, both definitions are maintained. If there is a conflict between the definitions (the same NAT IP address appears in both), then the manual configuration is used. If this options is not enabled and Automatic ARP configuration is enabled, the Security Gateway ignores the entries in the local.arp file.
“