sglee
asked on
my home PC fails to connect to my office PC using Remote Desktop
Hi,
I have SBS2011 network and I connect to my work PC from home using remote desktop connection. In Remote desktop RD Gateway server settings, I enter "remote.domain_name" that points to public static IP address of the office network and that has been working just fine. In my internet router, Port 443 is forwarded to IP address of SBS2011 server - 192.168.1.9.
Now the situation:
I am in the process of migrating SBS2011 to Windows Server 2019. As first part of process, I created a couple of new domain controllers - DC1 and DC2 - to current SBS domain, but I have NOT transferred FSMO roles to DC1 yet and I still have 192.168.1.9 as Preferred DNS server in TCP/IPv4 properties.
Today, I wanted to install RD Gateway in DC1 and see if I can connect to my office PC via DC1 instead of SBS2011 and I did the following:
1. Since remote.Domain_name.com was already used by SBS2011 certificate, I created a new sub domain "rds.domain_name.com" and pointed it to the same public static IP address.
2. I installed RD Gateway role in DC1
3, After creating SSL certificate using Certifiytheweb, I opened Remote Desktop Gateway Manager, imported the certificate and created RD CAP and RD RAP policies.
4. In my internet router, I changed IP address port forwarding from SBS2011 to DC1 on port 443 & 80. (Although only port 443 was forwarded to SBS2011 currently in the router, but in the past whenever I set up RD Gateway Server in other W2019 Server networks, I forwarded both ports 443 & 80. Do I have to forward both ports? )
5. I imported new server certificate into my home PC and tried to connect to my office PC, but it failed to make the connection.
(1) Do you think it failed because I have not moved FSMO roles from SBS2011 to new DC1 domain controller?
(2) To make RD Gateway, do I need to create forwarding on both port# 443 and 80 or only 443?
I have SBS2011 network and I connect to my work PC from home using remote desktop connection. In Remote desktop RD Gateway server settings, I enter "remote.domain_name" that points to public static IP address of the office network and that has been working just fine. In my internet router, Port 443 is forwarded to IP address of SBS2011 server - 192.168.1.9.
Now the situation:
I am in the process of migrating SBS2011 to Windows Server 2019. As first part of process, I created a couple of new domain controllers - DC1 and DC2 - to current SBS domain, but I have NOT transferred FSMO roles to DC1 yet and I still have 192.168.1.9 as Preferred DNS server in TCP/IPv4 properties.
Today, I wanted to install RD Gateway in DC1 and see if I can connect to my office PC via DC1 instead of SBS2011 and I did the following:
1. Since remote.Domain_name.com was already used by SBS2011 certificate, I created a new sub domain "rds.domain_name.com" and pointed it to the same public static IP address.
2. I installed RD Gateway role in DC1
3, After creating SSL certificate using Certifiytheweb, I opened Remote Desktop Gateway Manager, imported the certificate and created RD CAP and RD RAP policies.
4. In my internet router, I changed IP address port forwarding from SBS2011 to DC1 on port 443 & 80. (Although only port 443 was forwarded to SBS2011 currently in the router, but in the past whenever I set up RD Gateway Server in other W2019 Server networks, I forwarded both ports 443 & 80. Do I have to forward both ports? )
5. I imported new server certificate into my home PC and tried to connect to my office PC, but it failed to make the connection.
(1) Do you think it failed because I have not moved FSMO roles from SBS2011 to new DC1 domain controller?
(2) To make RD Gateway, do I need to create forwarding on both port# 443 and 80 or only 443?
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
*The default Remote Desktop Gateway port is TCP 443, but you can change it as well.