Link to home
Start Free TrialLog in
Avatar of Simon Allaway
Simon AllawayFlag for United Kingdom of Great Britain and Northern Ireland

asked on

remote desktop over different lans

Hi All

I am trying to connect to my other network using RDP.  I have set up a VPN (lan2Lan) using draytek routers and setup port forwarding from the router to the pc 3389 to 192.168.2.1.  I have also enabled the pc to allow RDP connections (my computer, properties, remote) and still I cant connect.

Any ideas?

Cheers


Si
Avatar of bright12
bright12
Flag of Netherlands image

You are able to  ping the other PC?
You do not need port forwarding at all. The advantage of a VPN is all ports are open and you effectively have automatic routing between sites.
The two site MUST have different subnets i.e. if one uses something like 192.168.1.x the other can use anything but, so they could use 192.168.2.x

Then just enter the IP of the remote machine in the RDP connection box.
If the windows firewall is enabled there will already be an exception for RDP, but it will only allow connections from the local LAN. To allow the remote LAN you have to add the remote site's subnet or allow all computers. See the following for instructions:
http://www.lan-2-wan.com/RD-FW.htm
Avatar of Simon Allaway

ASKER

Hi Rob

My main office is 10.10.10.0 /24 do I add this range or do I give the public IP address?

Thanks  again

Si
ASKER CERTIFIED SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
are you able to connect machine with in the same LAN.have you checked terminal services in machine to which you want to connect also check windows firewall.
Hi

Yes I can RDP fine to my server etc!  


Thnaks

Si
what I mean is are you able to RDP to that specific machine.I understand your machine IP is 192.168.2.1
and presume you have opened only certain port from one LAN to other.

If it is router IP than your publishing rules has to changed and it should be redirected to machine IP to which you want to connect from different LAN

if multiple machine need to be connect than you can just open RDP port 3389 in your firewall from different lan.no publishing rule required
Have you tried to allow for your remote LAN (10.10.10.0/24) on 192.168.2.1, as RobWill suggested?
>>"presume you have opened only certain port from one LAN to other"
No ports need to be opened or forwarded, this is a suite to site VPN.
Hi  Guys

I also have McAfee Toatal defense that im trying to work out how to alow multiple lans

Simon
this is the error im getting at the moment!

I have diabled the mcafee firewall and about to look at the windows firewall!

Cheers fellas

Simon
rdp-error.JPG
right solved that last error its was a setting on the vista boxes

Simon
The remote site/subnet gas to be added to the McAfee firewall list of trusted networks as well.
Just as a "heads up" : I have run into a lot of problems with McAfee update or something re-enabling the firewall blocking even after I have had it working for several months.
Hi Rob

Right I have got it all working now.  Mcafee was a pain as you could not put mutliple lans in so ( maybe we have a different version).

Rob, Do you recon that remote software like VNC or dameware will work over the VPN now as I would really like to be able to log on to the machine while the user is logged on?

Thanks rob you are a Jedi!!!

Simon
Glad to hear you have it working.
Sure you can use any app like VNC, Dameware or others over a VPN. The only issues are the firewalls. They generally create exceptions when installed, but again only for the local LAN. Same fix to McAfee and Windows firewall will resolve.
Now that you have RDP fixed you could probably use Microsoft's "offer remote assistance" from a server without any further changes.
By the way if you have an Active directory server controlling the remote PC's you can apply the firewall changes to all PC's using Group Policy. This of course will only apply to the Windows firewall, not McAfee.
This guy rocks!!!!!!  All Hail RobWill!!!!

Thanks Bud for all your help!!!!
:-)
Thanks cybersi
Cheers!
--Rob