|
|
|
|
Joined: Sep 2006
Posts: 329
Member
|
|
Member
Joined: Sep 2006
Posts: 329 |
Try LogMeIn Free! I still don't get what the topic-meister is asking. Could you please draw us a picture? Why have you forsaken us?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Apr 2001
Posts: 1,390
Member
|
|
Member
Joined: Apr 2001
Posts: 1,390 |
Well, getting back to your original question; does require a bit more attention with the ISP. You will need to let them know that you want a block of public IP’s on the Lan side of your router; this will allow them to build proper routes w/in their network defining the location of your Lan-side network. It’s really pretty simple, if the ISP will allow for it.
|
|
|
|
|
Joined: Jun 2006
Posts: 318
Member
|
|
Member
Joined: Jun 2006
Posts: 318 |
One thing you could do here is to install one server with RDP access. Then through that RDP connection run VNC to your servers. We do that at my work (through Citrix) and it works well for us. All you have to do is load VNC Server on the systems you want to manage and VNC Viewer on the system you RDP into. Less of a security risk as you only need Internet access to the server that you use VNC viewer on.
Sometimes you carpe diem, sometimes your diem gets carped.
|
|
|
|
|
Joined: Jan 2008
Posts: 148
Member
|
|
Member
Joined: Jan 2008
Posts: 148 |
I recommend you use at least two remote capable services in case one (usually windows TS) seizes up and wont allow connections. Then you can connect in with the other and reset it without needing slog out to the site.
About me:
8 years of network support
7 years IT field service
Always looking for the next project to be done.
|
|
|
|
|
Joined: Jun 2007
Posts: 2,106
Member
|
|
Member
Joined: Jun 2007
Posts: 2,106 |
I recommend you just set-up the watchguard router correctly.
Port Address Translation does not require you to change the port on the server. You are mapping external-IP port 3394 to server-interal-IP port 3389 inside the watchguard. BTW, 3389 is the standard windows RDP port. It's also recommended (by monkeysoft) to space the RDP ports 5-ports apart for whatever silly reason.
If you are worried about typing external-IP:3394 in your MSTSC connect window then all I can say is life's tough.
|
|
|
|
Forums84
Topics94,525
Posts640,013
Members49,852
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
