|
We recently moved to usiing NAT on our
firewall:
Private range: 192.168.0.0 -- 192.168.0.1-
192.168.0.100 for servers switches etc
DHCP: 192.168.0.101 - 254 DHCP clients
We have internal web servers and mail server with
FQDNs that outside can access no problems by using static NAT.
Problem is internal client cannot connect to these
public (statically natted) ip addresses within the local
network.
They can connect to it with the private
address.
The only fix I have so far is by putting host files
in their machines so that the web and mail servers gets resolved to the
private ip address. Also using internal DNS.
Question is why are these internal clients not
being able to access the public ip address of the web server. I cannot ping this
web server by its public ip address.
I can ping the firewall both internal anfd public
ip address.
Yes the web server's statically nated address
is in the same subnet as the firewall's external
ip.
| 
