Private VPN Connection

[bobby13]

Hi I have a wireless D-Link 604+ router, at present firewall on the router has been disabled. I have a static IP address (80.111.111.1) provided by my ISP on a 2Mb broadband link.

I basically want to Access my computer at home from office or anywhere, how do i do that? Ideally I would like to use a private VPN or remote desktop connection or PC Anywhere.

At present I have enabled port redirection so that incoming TCP packets from outside (80.111.111.1)get directed to my computer on IP 192.x.x.128, so TCP port 80, 3889, 5000 are directed here.

I disabled my windows XP Pro firewall and tried to logon to my computer from work via remote destop connection, got this error:
Protocol error detected at the client (code 0x1104)

I then tried Telnet from office, (open 80.111.111.1) got service is not available, connection lost.

I've started Telnet services, clicked on allow users to connect remotely to this computer, and Port 3889 is in the exceptions list for windows firewall. I'm currently using McAfee firewall+ and McAfee virus scanner on Windows 2000 Professional laptop, which is directly connected to the router via ethernet cable 24hrs a day.

What other windows services do i need to configure before i can successfully log on to my home network from anywhere?

Regards
Bobby

 

[msworld]

I believe the remote desktop port is 3389 instead of 3889. alos you may want to do RDC/TS over VPN. check this page for more details,

demo ts over vpnTo use TS over VPN, normally you need to establish VPN using the VPN ... However, with a pre-setup, you can just one-click to run TS over VPN in just one ...

http://www.chicagotech.net/demopages.htm

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on

http://www.HowToNetworking.com

 

[PeterHurst]

I would recommend you get the firewalls back up asap especially with ZOTOB etc floating around.

I'm not familiar with the DLINK but you should be able to forward just port 3389 (TCP) to your PC for remote access. If in doubt check that 3389 and Terminal Services is working locally first.