DNAT Rule not Working

Hello Chaydo Nazario ,

Thank you for reaching out to the community, please refer Add a DNAT rule with server access assistant.

Can you share the screenshot of the service definition you created "API_service?"

Hi, 

Yes of course. see the attached picture. the service port is 8000. i try to use port number 6050. but i left port 8000.

Sorry for delay. 

I already did the test using DNAT rule with server access assistant. But I had the same problem. 
Do you advise deleting all the rules and creating them again with DNAT rule with server access assistant?

You have the DNAT service changed when you don't need to? (API_service)

When creating a DNAT rule, should you leave the Translated Service as the original if it does not need to be changed? sorry, I'm using the UTM and don't know the proper wording, but am referring to the way the UTM NAT rules are created, where you don't change the service unless you have to because it could cause issues. Does it apply to the XG too and could it be causing issues??

Port NAT from and to the same Service should not cause issues. And if the logviewer shows green, and you mouse over the port and take a look at the packets / bytes transferred, it is likely an application issue. 

The logviewer entry, which shows blocked, is likely a "Connection Close" Packet, which the server sends to close the connection but the firewall already closed. 

Hi alan weir , thanks for your support. 

Did you switch the DAR service when you didn't need it? (API service)

A: I changed the port to 8000, as I suspected that port 6050 was being used by another service. e By default, the API service we intend to publish runs on port 8000, so decide to keep it on that port.

When creating a DNAT rule, should you leave the Translated Service as the original if it doesn't need to be changed?

A: Yes. I didn't change any settings.

Does this apply to the XG as well and could it be causing problems?

A: I believe so.

Hi, thanks LuCar Toni 

NAT port to and from the same service should not cause any issues. And if the logviewer shows green and you hover over the port and watch the transferred packets/bytes, then it's probably an app issue.
A: In logview, I should move the mouse closer and see if there is packet transfer right?

The logviewer entry, which shows blocked, is probably a "Connection Close" packet, which the server sends to close the connection, but the firewall has already been closed.

A: I haven't started to do the application connection tests yet because I have been doing port tests with this app.

portchecker.co/checking

Have you opened the original port on a firewall rule on the Firewall WAN IP?