How do I connect to my office via Remote Desktop Connection?

[Amado]

Do I need static IP's?
Do I need to configure the Netopia DSL/router at the office?

The office already have a VPN/Firewall/Router connected to the same DSL line but I don't have access to it. Is this a problem?

At home I use a "regular" dynamic 2Wire router.

I could log in to the Netopia DSL/router from any web browser but HOW DO I GET TO MY COMPUTER?

(I think I'm asking for too much)

Thank you!

[AboveTheLogic]

Originally Posted by Amado

Do I need static IP's?

Absolutely not, but if it changes often, you might consider some sort of dynamic dns service (search the forum a bit, this has been discussed a few times).

Originally Posted by Amado

Do I need to configure the Netopia DSL/router at the office?

Yes, you will need to forward port 3389 to the machine you want to access.

Originally Posted by Amado

The office already have a VPN/Firewall/Router connected to the same DSL line but I don't have access to it. Is this a problem?

I'm not sure I understand. Do you have 2 routers? If you only have one, you will absolutely need to access it to forward the port.

I noticed you mentioned VPN. If you have VPN access to the office network, this is preferable. Once logged into the VPN, you should be able to use remote desktop to access the machine using the local IP just as you would from another machine at the office. No port forwarding required.

Originally Posted by Amado

At home I use a "regular" dynamic 2Wire router.

Home setup does not matter.

[Amado]

I was told I should find an answer to my question on this website; but I never expected it to be so soon. Now, not to push my luck too far:

How easy is it to "forward port 3389" once I log in to the Netopia 3346N-VGx DSL Modem/Ethernet Managed Switch? or do you recommend I connect and configure the Netgear VPN/Firewall to the DSL Modem?

[Amado]

Current Office Set Up:

Phone/DSL Line (5 Static IP) - Netopia 3346N-VGx DSL Ethernet Managed Switch ("DSL Modem") - *Netgear ProSafe VPN Firewall FVS338 - Office Computer.

Note: I don't have (and will prefer not to have) access to the VPN.

[Amado]

I only have Admin access to the Netopia 3346N-VGx DSL Ethernet Managed Switch ("DSL Modem").

Can I connect directly to my office computer via RDC without using the VPN or I will need to order a dedicated DSL line (with a new modem)?

[AboveTheLogic]

Originally Posted by Amado

I was told I should find an answer to my question on this website; but I never expected it to be so soon. Now, not to push my luck too far:

How easy is it to "forward port 3389" once I log in to the Netopia 3346N-VGx DSL Modem/Ethernet Managed Switch? or do you recommend I connect and configure the Netgear VPN/Firewall to the DSL Modem?

Here is a link to an article on their website that talks all about it:

http://www.netopia.com/support/hardw...s/CQG_025.html

Originally Posted by Amado

Current Office Set Up:

Phone/DSL Line (5 Static IP) - Netopia 3346N-VGx DSL Ethernet Managed Switch ("DSL Modem") - *Netgear ProSafe VPN Firewall FVS338 - Office Computer.

Note: I don't have (and will prefer not to have) access to the VPN.

I wonder about the VPN Firewall device. You can try setting up the Netopia alone, but if the VPN Firewall device is between the DSL modem and the computer you are trying to access, it might block your connection attempt.

Then again, it might just be functioning as a switch and work just fine.

Originally Posted by Amado

I only have Admin access to the Netopia 3346N-VGx DSL Ethernet Managed Switch ("DSL Modem").

Can I connect directly to my office computer via RDC without using the VPN or I will need to order a dedicated DSL line (with a new modem)?

The only reason I can think of that you would need a dedicated line is if the Netgear VPN device (that you say you dont have access to) is blocking your connection attempt, AND you don't change your mind on just using it for a VPN connection.

Still, then, you can try fotonique's suggestion.

Or, there are other much more advanced alternatives, such as VNC.

It is possible to setup VNC server on the work side, and VNC viewer on the home site, and tell VNC server to connect to VNC viewer (rather than the other way around), and then all the firewall configurations simply need to be made on the VNC viewer (home) end... but this is much more complicated than many other solutions out there (although its free).

[Amado]

I did push my luck and it worked.

In conclution; there is no easy and secure way to use Remote Desktop Connection (Microsoft makes it sound so easy) outside my LAN.

I guess for now I'll keep using WebEx to connect to my office computer.

Thank you for all the assistance.

Note: Have you used Microsoft Remote Assistance? Any advice?

[wimiadmin]

Originally Posted by Amado

I did push my luck and it worked.

In conclution; there is no easy and secure way to use Remote Desktop Connection (Microsoft makes it sound so easy) outside my LAN.

I guess for now I'll keep using WebEx to connect to my office computer.

Thank you for all the assistance.

Note: Have you used Microsoft Remote Assistance? Any advice?

Hi Amado,

I disagree when you say there is no easy and secure way to use Remote Desktop Connection.

In Windows Server 2003, XP, and Vista, you right click My Computer and choose Properties. Then hit the Remote tab and put a check mark in the box that says "Allow Remote Connection" and select the users that are allowed to connect.

Forward the port on the router to the computer you wish to connect to and you're done.

That's pretty simple if you ask me.

To reduce the chance of the computer being logged in to by an intruder, you can easily change 2 things. First, rename the Administrator account to something else and ensure all users have strong passwords www.passwords.com And secondly, you can change the listening port from 3389 to whatever you want in the Windows Registry. Hackers can still scan for open ports, but they're lazy and will probably give up when they find that the "common" ports aren't open.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro l\TerminalServer\WinStations\RDP-Tcp\PortNumber

Of course, after you change the RDP port, you'll need to reboot the system and change the port forwarding on the router.

Those 2 steps should keep you very safe.

You could even go a step further if you have a static IP at home and only allow connections to your PC from that IP in the Local Security Policy for XP and Vista and then IPSec in Server 2003. Even if you don't have a static IP and it's something like 1.2.3.* you can only allows connections from 1.2.3.* or 1.2.*.*.

I'm not going to give an in depth explanation of IP Security, but just to tell you it's available.

But, ultimately, as AboveTheLogic stated, if you could connect to your network via VPN and remote in to your machine that way, that would be the best method....in my opinion.

Brian

[AboveTheLogic]

I 2nd that, changing the port is good, but as good and secure as VPN, but much easier to do.

Using VPN gives 2 layers of authentication before getting to the machine.

What I don't understand is that you say it worked, but you are not going to use it now?

May I ask why?

[AboveTheLogic]

Originally Posted by Amado

Note: Have you used Microsoft Remote Assistance? Any advice?

I've used it, it works, and you don't need to configure the router.

Its not designed to access an unattended machine, though, its designed more for accessing a machine that someone is sitting in front of and they let you in.