Remote Access

[Neil Duggins]

I have set this service up and bound it to my internal adaptor, I'm a bit puzzled I have installed the management console on my laptop, and if I understand correctly all I have to do is type 192.xxx.x.x:808 and this should connect to my home installation ????? How can that be surely there are millions of machines out there sitting on the same IP how does the management console know which on to connect to ??/?



Help

[erwin]

I take that you mean you want to connect to your home installation of WinGate (and administer it) from a remote location on the Internet.
If this is the case then you will need to connect to the Internet connection of your home network machine (ie its Public IP address). This also means that you will have to bind the remote control service (RCS)in WinGate to this external interface (so it can listen).

The remote access of WinGate Management is primarily designed to work for remote administration in LAN situations, but can be bound to an Internet connection to facilitate administration across the Internet if it is really needed. Be aware of course that by binding the remote control service to a Public IP address comes with any of the the inherent risks associated server applications on the Internet. (ie other people can try to access it.)

If WinGate is behind a NAT router, then you can have the router forward all incoming RCS connections (on port 808 by default) to the LAN IP of the WInGate server that is connected to the router. You would then bind the LAN interface on the WinGate server to the RCS, so it can listen for these incoming connections from the router.

[Neil Duggins]

Ah IC so does this open me up to hacker attacks ?? Its only a home install and its a dedicated proxy I use anti virus on the machines that connect to it and nothing on the proxy itself.

can I set up a time that adminiostration is available from remote ? so that its only in a small time window frame or once it binded to the external adaptor its available period ?

Thank you

Neil

[adrien]

Hi Neil

we run a bunch of servers with remote control service available from the Internet... it's been hardened specifically for that, as long as you choose decent passwords.

If you have an enterprise license, you can specify which accounts can be used to auth to what service from where and when using policy with the PreAuth event from Users and Groups.

If you don't have such a license, you can use normal policy to set where connections can be from and when, using the ClientConnect event in the Remote Control Service.

Regards

Adrien