windows server 2008r2 { SOLVED } [ Help Needed ] RDP Access From Outside Network

[WALLONN7]

Hello guys...

 

I already have networking experience but this is the first time I need to connect computers that are outside of one domain and in another network. RDP access in the same domain and network works perfectly...
I already followed several tutorials and no success ... Routers involved were configured with port routing

I need it to become functional without having to disable Firewall
The network has:

=> Windows Server 2008 R2 Standard [Updated (Active Directory / DNS / Files Server... enabled)]

=> Windows 7 Professional ( client outside network )

 

And here's how it should look:

 

Quote

                                                                                                                                                                                                  Server 2008R2  <-------------------> ( domain router ) <------------------------> internet <----------------------> ( access router ) <------------------------> Win7 Pro

 

Windows Server = firewall 3389 port open and remote desktop configured

 

Domain router = 3389 port forwarding to Server fixed ip

 

Access router = once it's in another subnet, I don't know what to do...

 

Win7 Pro = configured

 

 

Thanks in advance!!!

 

 

[Recruit]

If you have a router before the server you need to set up a port forwarding for the rdp port used.
Regarding the firewall should be simple : if it will not work directly , you can add an exception in incoming table for the specified port.

 

Tell us if you have a router, or the server os has also DHCP scope.

[WALLONN7]

8 minutes ago, Recruit said:

If you have a router before the server you need to set up a port forwarding for the rdp port used.

 

Already done before posting here with no success...

 

8 minutes ago, Recruit said:

Regarding the firewall should be simple : if it will not work directly , you can add an exception in incoming table for the specified port.

 

Same as above...

 

8 minutes ago, Recruit said:

Tell us if you have a router, or the server os has also DHCP scope.

 

Yes, I do have... DHCP = router... Server DHCP is not installed... Scope configured... Server IP is static...

 

Edit: message is always like "Server is not available or not connected"...

[Recruit]

Tell us which error have you got !
If your router has a vpn option, you can set up it and you can use remote desktop feature outside like in local.

[WALLONN7]

3 minutes ago, Recruit said:

Tell us which error have you got !

 

7 minutes ago, WALLONN7 said:

Edit: message is always like "Server is not available or not connected"...

 

About VPN thing... Router supports it...

Things I forgot to mention:

 

1.  Server will be behind one model router
2.  Client will be behind another

 

Is VPN configuration simple for this scenario?!

[Recruit]

11 minutes ago, WALLONN7 said:

Edit: message is always like "Server is not available or not connected"...

 

I see now : I will take a look into my infrastructure : I have a Cisco Router & Switch and recently I made a VM with Windows Server 2016. I will use vpn service from the client like I would be outside.
I will come back with the results .

 

2 minutes ago, WALLONN7 said:

Is VPN configuration simple for this scenario?!

 

If the client got an ip from the LAN through VPN everything should work like in LAN. All resources should be available if are not set up different.

[WALLONN7]

1 minute ago, Recruit said:

 

I see now : I will take a look into my infrastructure : I have a Cisco Router & Switch and recently I made a VM with Windows Server 2016. I will use vpn service from the client like I would be outside.
I will come back with the results .

 

 

If the client got an ip from the LAN through VPN everything should work like in LAN. All resources should be available if are not set up different.

 

I'll wait for your results... And a step-by-step... Am I asking too much?! 

[Dodel]

Can you ping the destination IP, are you logging in with domain\username, have you got RDP access to the destination IP ?

[Recruit]

Everything is fine here, Bro :

 

Steps :

 

1. Go to server os, right click on My Computer - Properties - Remote and set up it like in screenshot : think you made it already !

 

 

2.  We will setup up further the port forwarding into the router, like this : 3389 default rdp port and the ip is local for the server in vm :

 

 

3. I have added a rule into the firewall router to allow the incoming connection for rdp : the router has all incoming ports closed by default. Looks like rdp for incoming uses tcp.

 

 

4. Open remote desktop client (  I used the default client from Windows 10 for my test  ) and type the public ip address.

 

 

5. Type connect and you will be asked for username & password for the connection with server ( I used the admin ) I was in hurry to see if works and I forgot to make screenshot here

 

6. You can see below the result : Everything worked as it should be. I let you see the first and last digits from the public ip ( see the title bar & client ) to demonstrate that I used it like outside : you can see the public ip is different of the ip for the internal server ( vm )

 

 

The server is configured in AD mode !

 

I need to sleep now. If you have other questions I will take a look tomorrow.
Good luck, Man !

[WALLONN7]

22 hours ago, Dodel said:

Can you ping the destination IP, are you logging in with domain\username, have you got RDP access to the destination IP ?

 

Ping's fine and RDP works flawlessly in the same network... Even when client pc is not in the same domain...

 

 

22 hours ago, Recruit said:

Everything is fine here, Bro :

 

Steps :

 

1. Go to server os, right click on My Computer - Properties - Remote and set up it like in screenshot : think you made it already !

 

 

2.  We will setup up further the port forwarding into the router, like this : 3389 default rdp port and the ip is local for the server in vm :

 

 

3. I have added a rule into the firewall router to allow the incoming connection for rdp : the router has all incoming ports closed by default. Looks like rdp for incoming uses tcp.

 

 

4. Open remote desktop client (  I used the default client from Windows 10 for my test  ) and type the public ip address.

 

 

5. Type connect and you will be asked for username & password for the connection with server ( I used the admin ) I was in hurry to see if works and I forgot to make screenshot here

 

6. You can see below the result : Everything worked as it should be. I let you see the first and last digits from the public ip ( see the title bar & client ) to demonstrate that I used it like outside : you can see the public ip is different of the ip for the internal server ( vm )

 

 

The server is configured in AD mode !

 

I need to sleep now. If you have other questions I will take a look tomorrow.
Good luck, Man !

 

I restart everything from scratch to test your example... Works like a charm in the same network...  But not from outside... Thanks again, bro...

OP was updated with more info... I think I led you to wrong road before updating it... Sorry for that...

Any other ideas?!

[Recruit]

13 minutes ago, WALLONN7 said:

Works like a charm in the same network...  But not from outside

 

In the same network I don't need to forward any ports & and to add rules in firewall of the router .

 

Try with vpn and report.

 

Also tell us which router model is and eventually if there is available an online emulator for it.

 

Greetings,