Remote Administration setup

[clinthammer]

Hi!

Purchased Wingate 12users Enterprise edition.. will be getting the serial tomorrow or day after from the dealer.

Our setup will be as follows:

Wingate installed on Win2k Pro server (sp3 or 4) - internal
10 client pcs and macs - internal

By default the Win2k machine is locked (win key + l) so no one can access it.

When I am going away on business next month I want to remote admin the wingate software - basically just ensure it is running smoothly and no db corruption.

Since our network in the office is behind our Cisco pix firewall, what port does wingate need active on the PIX? So that I can fwd firewall requests for wingate remote admin to the win2k machine?

Will remote desktop on the win2k machine cause any interference?

Thanks,
CD

[gginerc]

I haven't used the remote admin feature, but you could do the same using the remote desktop included on WinXP or terminal service in a W2K to manage your wingate machine from Internet. Be sure to update your W2k to at least SP4 and all the windows updates (I've have tested them with Wingate 6.1.1.1077 and no problem, just a little bit more security). Then you only have to let the ENS to pass through port 3389, well if you haven't done yet open that port also on your CISCO and route it to your wingate machine. Obviously as this port could be reached from Internet and is a well known one be sure to only let one user to start a remote session and choose a good hard password. Hope to have helped you.

[Pascal]

I use Remote Desktop most of the time; however the Remote Control Service is what controls the GateKeeper connection. You need to setup a binding for that so it will listen on the appropriate IP+port combinations and will then need to forward it's port through from the PIX. (Usually port 810)

[Nev]

Hi all,

Can't recommend leaving port 3389 open, it's very vulnerable.

Try this KB article http://support.microsoft.com/kb/306759 on how to change the port to a non standard one for better security, even if it's one port away or in my case I use an un assigned one which so far hasn't resulted in any problems.

As a tip, to initiate the connection, just use the client 'ip:port" in RDP, eg: 192.168.0.111:5663 is all that is required.

All precautions apply about editing the registry.