Problem setting up VNC

[gsm]

We're currently trialing VNC, and a generally happy with the software except we're having trouble
getting VNC to work.

We have a Scenario 3 setup, with a router/firewall at 192.168.1.1, the WinGate server at 192.168.1.100,
and a WinGate client at 192.168.1.10. The gateway and DNS server for the WinGate client is set to 192.168.1.100,
and browsing is done using the WinGate proxy server with Java authentication.

Before installing WinGate, port 5901 on the firewall was forwarded to 192.168.1.10, and we were able to
remotely access this computer with VNC. We wish to set up the same capability under WinGate.

Initially, we made no changes to the VNC setup after installing WinGate, but any attempt to access the
WinGate client at 192.168.1.10 just hung.

After a little research, we made the following changes:

(1) The forwarding of port 5901 on the router firewall to the WinGate client at 192.168.1.10 was altered
to forward the port to the WinGate server at 192.168.1.100

(2) On the WinGate server, port 5901 (internet computers to WInGate PC) was redirected to port 5901
on the WinGate client, 192.168.1.10.

With this setup, whenever we try to remotely access the WinGate client, the remote VNC client terminates
with the message "unable to contact host: Connection refused (10061)". If we tick "Don't translate source IP",
we get the same result.

So we're looking for some guidance on how to set VNC access to the WinGate client. Any help would be much
appreciated.

[adrien]

Hi

Since you have only 1 subnet internally, and your client machine is using WinGate as a default gateway the following will happen

a) if you forward VNC port to the client:

in this case, an inbound packet from the internet will be forwarded to your client machine by the router. The client computer will respond with a SYN ACK packet, which will be sent to WinGate. WinGate won't know what to do with this, so the connection is broken (since inbound and outbound paths are different, and WinGate does address translation).

This is why the connection hangs in this case.

b) if you forward VNC port to WinGate:

this should work. The fact you get a connection refused message indicates a packet is coming back to the client (just the wrong sort).

This indicates you set the entry maybe in the wrong table? Depending on the type of the LAN interface (I presume internal), the table you would need would be "LAN connections to WinGate computer".


Regards

Adrien

[gsm]

Yes, that did the trick ! Thanks for your help.