Got it

According to session information to solve the address mapping problem

Latest reply: Jun 19, 2016 16:25:20 4962 2 0 0 0
 

Phenomenon description:

The public network------fw------sw----server

There is an ERP server in an office site, and when use the intranet to access only by inputting IP addresses and related information at the client software can access, but the public network can't access after address mapping, the Server can access the intranet.

nat server 0 protocol tcp global 59.46.35.211 1433 inside 176.16.1.2 1433
nat server 1 protocol tcp global 59.46.35.211 768 inside 176.16.1.2 768
nat server 2 protocol tcp global 59.46.35.211 769 inside 176.16.1.2 769

 

 

Cause analysis:

1. Configuration problem
2. Carrier or server denied some ports
3. The port configuration is not whole

 

Handing process:

1.Telnet to check the configuration and it is correct.
2.check the session and find the route and nat server configuration is correct:
[USG2100]dis firewall session table destination inside 176.16.1.2
16:38:27 2012/03/27
Current Total Sessions : 1
tcp VPN:public --> public 59.46.35.210:14416-->59.46.35.211:769[176.16.1.2:769]
3. Check whether there is deny port or access on the Server
undo nat server 0
undo nat server 1
undo nat server 2
nat server global 59.46.35.211 inside 176.16.1.2

The access is ok. Customers check session many times and find the established connection exist other port


[USG2100]dis firewall session table destination inside 176.16.1.2
tcp VPN:public --> public 222.186.26.58:6000-->59.46.35.211:6666[176.16.1.2:6666]
tcp VPN:public --> public 124.227.192.165:6000-->59.46.35.211:8909[176.16.1.2:8909]
tcp VPN:public --> public 124.227.192.165:6000-->59.46.35.211:9415[176.16.1.2:9415]
tcp VPN:public --> public 119.139.120.32:4866-->59.46.35.211:769[176.16.1.2:769]
tcp VPN:public --> public 119.139.120.32:4973-->59.46.35.211:769[176.16.1.2:769]

4. Add address mapping port, and can access after check
undo nat server 0
nat server 0 protocol tcp global 59.46.35.211 1433 inside 176.16.1.2 1433
nat server 1 protocol tcp global 59.46.35.211 768 inside 176.16.1.2 768
nat server 2 protocol tcp global 59.46.35.211 769 inside 176.16.1.2 769
nat server 3 protocol tcp global 59.46.35.211 6666 inside 176.16.1.2 6666
nat server 4 protocol tcp global 59.46.35.211 8909 inside 176.16.1.2 8909
nat server 5 protocol tcp global 59.46.35.211 9415 inside 176.16.1.2 9415

Suggestions and summarizes
By configuring full-mapping can eliminate interference of firewall and server itself a certain extent, and also to the access port

thanks for sharing!
View more
  • x
  • convention:

给我来一瓶酱油
View more
  • x
  • convention:

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.