by jamescap » Jul 02 08 4:56 pm
This is what I would probe to isolate the problem or provide an alternative solution. And my apologies if you definitely know that the application cannot use a proxy.
If you temporarily disable PureSight or any other plugin from the proxy, does the application work?
Temporarily reduce the session timeout for the proxy?
Temporarily disable caching?
If this application has the ability to use a proxy server, have you tried manually setting it, or sending the request to a second www proxy server that you create in WinGate - no auth etc..?
Can you set this application to use a different port number for this destination address e.g. 81 instead of 80? Setting port numbers might be found in the GUI or registry or other parameters/command lines associated with the program. If you cannot find a port number to edit then you could try setting it inline with the destination ip address/domain name; x.x.x.x:81 – assuming that can be found/edited. So on the scenario that the port number can be changed, you could setup an ENS redirection for LAN to internet for port 81 that overrides the port back to 80; possibly specify an ip address, or leave blank / 0.0.0.0 if the destination address changes. And then of course lock down via policies etc...
I am not sure if this will work but… IF this application makes a DNS request before it uses NAT then you may be able to resolve the request to the WinGate servers IP and then pass the connection through a TCP Mapping. So first of all you would add a second ip address to the WinGate servers internal network card. Then you would edit your WWW Proxy Service so to only bind to the original ip address. Create a new TCP mapping in WinGate and bind it to port 80 on this new address you created, then map it to the proper destination for that application. Then go to the LAN Client and adjust the ‘hosts’ file so to resolve e.g. application.software.com to the WinGate servers new internal ip address. Hence any request made by the application will be relayed through the new TCP Mapping on port 80. And then of course lock down via policies etc…
Depending on your network setup, If this LAN Client is connected to the same switch/hub as the hardware internet router, can you make a route on the LAN Client to bypass WinGate for this applications destination ip address, and send it directly to the hardware internet router instead?