Static NAT, Proxy, Reverse?
Hello, I have a Watchguard Firebox T30 at a doctor's office. It works great but they tell me that they have not been able to send documents to a specific ftp site since I changed to it from their old Cisco Router that was installed by another company years ago. I know how to configure static NAT on a Watchguard but this is in reverse. Let me explain. The specialized software on the internal server opens up ports 1116-1120 for sending documents out to an external ftp server at port 21. So I have tried creating a custom policy to port 21 and then a static NAT to the internal IP of 192.168.43.252 port 1116. If I just ftp to the external address on port 21 it works fine from my laptop or any other computer on the network but as you can tell they are using different ports on the server.
I have tried just 1 specific port at the moment. So if I create a policy with the ip address of x.x.x.x (this is the address of the ftp server) as an external "host" in the "From" field and a Static NAT from External to Internal ip of 192.168.43.252 port 1116 in the "To" field will this translate both ways? Is the ftp proxy that is enabled on the router by default blocking the connection? I tried this and it failed. I did not disable the default "ftp proxy". The sad thing is that the server only sends this out once a month and no one knows how to activate it on the server to run a test. So this makes it really hard.This will not happen again until the end of this month.