Enabling intranet users to access the internal server on the same subnet of the same security zone through a public IP address

15

Enabling intranet users to access the internal server on the same subnet of the same security zone through a public IP address
Configure a source NAT policy with the source and destination security zones being the security zone where the users and intranet servers reside to translate source IP addresses of intranet users into a public address. Then configure NAT Server to translate the destination addresses of packets destined for the public address of the servers into private addresses.

Other related questions:
nabling intranet users to access the intranet server on the same subnet of the same security zone through a public IP address
Configure a source NAT policy with the source and destination security zones being the security zone where the users and intranet servers reside to translate source IP addresses of intranet users into a public address. Then configure a server static mapping policy to translate the destination addresses of packets destined for the public address of the servers into private addresses.

When a user and a server are on the same intranet in the same security zone, how can I configure an FW to properly forward intranet user packets destined for the public IP address of the intranet server
Perform the following operations on the FW: -Configure a source NAT policy, in which the source and destination security zones are the same as those of the intranet user and server. The source NAT policy translates the source IP address of the intranet user into the public IP address of the intranet server. -Configure a NAT Server to translate the public address into the private address of the intranet server. The packets sent by the user to the server carry the server's public address as the destination address.

An internal user cannot access the internal server through the public address
An intranet user cannot use a public address to access an intranet server. Use the following method: 1. Check whether services on the intranet NAT server are running properly. 2. Check whether the NAT server is configured correctly. 3. Check the connection between the external host and NAT server and the configurations of the connected interfaces. 4. Check that the intranet NAT server is configured with the correct gateway address or route.

Intranet users cannot access the internal server using a domain name, but they can access the internal server using an IP address
Q: Intranet users cannot access the internal server using a domain name, but they can access the internal server using an IP address. A: Ping the domain name and check whether the public IP address can be parsed. If the IP address cannot be correctly parsed, check whether the account password and DNS information are correct. Configure DDNS software on the PC to check whether the IP address can be parsed. If no error is found in the preceding operations, contact the carrier to check the DDNS server. Check whether the DDNS server synchronizes the updated domain name to the DNS server. The causes are as follows: It is used in the scenario where terminals use PPPoE dial-up. The router runs normally when users can access the internal server using IP addresses. DNS resolution is the first step to access a domain name. Because the PPPoE interface dynamically obtains an IP address from a carrier, the DDNS server must send the updated mapping between the domain name and IP address to the DNS server in real time. Check whether the DDNS server synchronizes the updated domain name to the DNS server.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top