Can anyone give me an idea of what the problem may be with a setup of a Full NAT rule.
- I have a UTM (10.0.0.1)
- I have a server (10.0.0.2) with a hostname of webserver.local. This hosts a web service on port 7090
- I have a Win7 client (10.0.0.254) on the same subnet as the webserver.local and an application that is hardcoded to talk to the web service using port 80 although it should be 7090.
To get around the client application needing to be reprogrammed to use port 7090, I have amended the local hosts file of the Win7 client(10.0.0.254) and created an entry of 99.99.99.99 webserver.local. This then will force the client to lookup the webserver.local with an external IP and then route to the UTM.
I have configured the UTM with the following:
Full NAT:
For traffic from: Win7(10.0.0.254)
Using Service: 80
Going to: 99.99.99.99
Translate to:
Change Destination to: 10.0.0.2
And Service to: 7090
Change Source to: UTM(10.0.0.1)
Firewall:
For traffic from: Win7(10.0.0.254)
Service: 7090
Destination: 10.0.0.2
Starting up the client application the connection works fine. However, after a period of time the connection seems to drop. If I then telnet from the Win7 client machine to 99.99.99.99 port 80 the connection does indeed time out . If I try again 30 seconds later using telnet or the application, the connection resumes.
What I have attempted to do when the connection times out was telnet from the Win7 client to 10.0.0.2 port 7090 and the connection is fine because I am not using the UTM. The problem seems to be when using 99.99.99.99 on port 80, that then passes through the UTM so I know it is the NAT or firewall causing a problem.
Any one have any idea on what the problem may be? The firewall log doesn't show any dropped packets.
Bizzare the problem is intermittent.
Thanks in advance
This thread was automatically locked due to age.