RDP to LAB server, from home network , any tips ?

August 26, 2017 at 03:06:20
Specs: Windows 10, I7
I have created a lab network with a windows server at home , on a different subnet than my home network . What is the best way to log into the lab server remotely ?
The server is a fresh install of WIndows Server 2016 . I installed it to experiment with AD, DNS . The lab network is in an outhouse but routed through to the home , with its own router connected via Ethernet

It is cold in the outhouse, so wanted to use the lab network remotely , I tried to RDP to the server from the home network but ( Using Windows 10 Pro ) , it did not connect . I tried lowering firewalls but , still no connection

Home network 192.168.1.XX/24

Lab Network Server 192.168.2.232/24
Gateway Internal IP 192.168.2.1
Gateway External IP 192.168.1.253

Does anyone have any tips ?

message edited by 90Ninety


See More: RDP to LAB server, from home network , any tips ?

Reply ↓  Report •

#1
August 26, 2017 at 03:48:13
Where do you set "Gateway Internal/external"?
Can you ping the server from the PC you want to access it from?
Did you connect the server network router to the LAN of your home network router?
Possible need to forward RDP ports on the server-network-router.

Reply ↓  Report •

#2
August 26, 2017 at 04:28:37

Where do you set "Gateway Internal/external"?
as above (edited)
Can you ping the server from the PC you want to access it from?
No but I can ping the home desktop from the Lab Server
Did you connect the server network router to the LAN of your home network router?
Yes the the regular home network is connected to the Wan port of the Lab network
Possible need to forward RDP ports on the server-network-router
Yes this will need some investigation , as I havent done port forewarding though networks before

message edited by 90Ninety


Reply ↓  Report •

#3
August 26, 2017 at 06:55:33
OK I think I managed to open the ports by :
Port Forwarding 3389 from My ISP's ( home network ) router ( 192.168.1.254) to the external address of the Lab Router (192.168.1.253)
Port Forwarding 3389 from The Lab router ( internal address 192.168.2.1) to the server (192.168.1.232)

I ran an open port test from the server , the open port test now confirms that the lab server is receiving traffic though the 3389 ( the port is open for the server)

However I still cannot ping from my Internal home network ( ISP ) to my lab network . What gives ?

I can however ping my home network from my lab network


Reply ↓  Report •

Related Solutions

#4
August 26, 2017 at 17:48:09
Any other device on the lab network that you can ping?
Is the Server setup to respond to ICMP messages?
Does SAMBA works? Can you access files on the sever from the PC. (also server configuration/management)


Reply ↓  Report •

#5
August 28, 2017 at 06:47:22
Did you add a route to the lab network on the router? You need a route between the two separate subnets in order for them to "speak" to each other.

Without a route to that other network, you won't be able to "speak" to it from your LAN, or from a remote site. Once you can RDP in from your LAN, then you'll need a port forward to the appropriate IP of the server in your lab

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

message edited by Curt R


Reply ↓  Report •

#6
August 28, 2017 at 13:56:58
Further to what I said above:

Home network 192.168.1.XX/24

Lab Network Server 192.168.2.232/24
Gateway Internal IP 192.168.2.1

If you look on your router on the LAN side you'll see it has 192.168.1.1 as it's IP which is also the default gateway for your 192.168.1.0/24 network.

You show the 192.168.2.0/24 network as having gateway 192.16.2.1 but that IP is not configured anywhere so the traffic has no where to go. Ergo the network is unreachable and the need for a path going from 192.168.2.0/24 to 192.168.1.0/24

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Reply ↓  Report •

#7
September 18, 2017 at 11:39:33
Hi , ok the Lab router has two IP addresses
Internal IP 192.168.2.1
External IP 192.168.1.2

When you say the network needs a route , is this something done via command on the server, or additional config within the router

I had a friend try to do add route within command but it still did not connect

Can someone explain


Reply ↓  Report •

#8
September 18, 2017 at 13:29:38
I finally figured it out , in order to remotely connect to my lab network server , from my Home network - I had to enter the External IP address of the Router ( not the server IP ) into the RDP address bar

So from my home computer 192.168.1.202 I enter the IP of the Lab network external IP 192.168.1.2

Voila Works just fine - Not sure how to connect via the server name though

message edited by 90Ninety


Reply ↓  Report •

#9
September 18, 2017 at 13:37:09
I can also connect just fine with the public IP , however my understanding is that you can only host one service per public IP address , meaning that I can only have one remote desktop instance .

As a concept I wanted to have other computers in my lab to connect to but it seems that is not possible without the use of virtual machines ?

Virtual machines is another subject another time however


Thanks guys

message edited by 90Ninety


Reply ↓  Report •

#10
October 8, 2017 at 16:03:55
Weird , this suddenly stopped working , I can ping from Lab Network and Vice Versa but cannot access the router from the Home Network and the RDP connection drops off after initial connection

message edited by 90Ninety


Reply ↓  Report •

#11
October 8, 2017 at 18:23:35
restart the router no change?

If you need to forward multiple services (RDP) from WAN, Use a different port on the WAN side and forward to the right IP+ RDP port on the LAN side.


Reply ↓  Report •

#12
October 9, 2017 at 02:31:56
@Sluc :Hmm its something on either the client machine ( the one initially accessing the lab network ) or the Lan ethernet port . It worked fine when accessing from another computer on the Wireless LAN

More interestingly however , with regard to you mentioning 'multiple RDP from WAN ', Can I use a range of specific ports for RDP ? Say 3389 ~ 33XX , or are these configurable to be whatever on the host side?

This is exiting , however I thought most port numbers are reserved for different services and cannot be used ? Or do I reserve any port I like on the Local Host ( server/desktop) side ?

Also when you mention to port forward each different Port from The ISP WAN to the External Lab Router , do you also mean then to port forward each respective different port to each IP on the LAB Internal LAN ?

For Example
<ISP/Home Router>
Forward Port 1234 to Lab Router IP (External IP 192.168.1.2)


<Lab Router ( internal IP 192.168.2.1>
Forward Port 1234 to Desktop 1 ( Internal IP 192.168.2.201 )


Thanks , this is a great solution for me , if I can get this to work for multiple Remote desktops , however I am not sure which port range to use .

message edited by 90Ninety


Reply ↓  Report •

#13
November 7, 2017 at 16:12:21
just an update I can rdp to the lab just fine, by using the lab router external ip, however I noticed I cannot ping the lab routers external ip from the home network

Reply ↓  Report •

Ask Question