no responce on port : message from java client

[gsunilman]

I m using wingate 5/6 for proxy access in intranet .

My wingate server is between two firewalls internal and external.
cascaded trougth trend web security

the port 80 .808, 8080 were given acces for wingate throught firewalls

wingate using java authentication.

problem is that my other locations are connected throught vsat connection

and they are connecting throught 8080 port

the java applet shows the error : no responce on port


This happens everytime I log in from vsat connected locations. Wingate doesn't log me saying "error... no response on port" even if the credentials are correct and the server with Wingate up and running...

[Pascal]

The Java applet needs to be able to reach the Remote Control Service. So you need access on that port / binding on an interface that is available to the client machine.

[gsunilman]

pls explain what the work to be on wingate side /configuration ,

because the firewall is confiugured to communicate on the 808, 80 and 8080 port to and from for the proxy server.

[Pascal]

Have you adjusted the properties of the Remote Control Service so that it will bind on the appropriate (And reachable) adapter? That is not firewall related.

[gsunilman]

Here the proxy server had the single network adapter which had been binded priviously.

Have you adjusted the properties of the Remote Control Service so that it will bind on the appropriate (And reachable) adapter? That is not firewall related.

the structure is as follows

VSAT connecting clients>> 172.100.100.227:8080 forged by router to 10.0.0.7 >>>firewall >>><<<(proxy server on ip ID 10.0.0.7)>>><<<local firewall.

here local connection has been now connecting to proxy server with proxy java authentification on port 80. And the remote clients are adviced to user 8080 port which is configured not to use java authentification on behajf of it is configured to the asumed uses on the specified IP addesss.

As this has to be forced to set as the java authentification failed happen on the remote clients.

We still requied to be java authentification on the remote clients.

[Pascal]

VSAT connecting clients>> 172.100.100.227:8080 forged by router to 10.0.0.7 >>>firewall >>><<<(proxy server on ip ID 10.0.0.7)>>><<<local firewall.

I think you've indicated this is the case, but to be sure - port 808 is also 'forged' in that fashion? You'll get that message when the Java client cannot reach the WinGate server (The WinGate server fills in what IP and port the Java client must try to reach it on) when it serves the page back to the appropriate web-client.

So this sounds like something surrounding the traffic not coming through properly. Do you have any network sniffers available so you can see what port the client is trying to reach and what traffic actually comes through to WinGate when you attempt to login?