J
Jerry Barrett
Hi
Im struggling with getting past the security layering to test an RDS Gateway configured on a 2019 Standard Server. (was easier with Access Anywhere)
Anyway I have a New PDC 2019 Server on a self contained Test LAN behind a router/firewall - connected to my Home LAN via its ethernet WAN port, this all works and the test server can surf the web and I have PC also connected to the test lan in the domain of the PDC 2019 server, That works perfectly too it can access domain resources on the New PDC 2019 server (seperate from my own home domain (2012R2 Server)
Because if the demise of the Essentials and Access Anywhere, I have configured the new PDC 2019 Server with RDS Gateway to enable access to LAN PCs from the internet (when its finally deployed) I setup the RDS Gateway with a self signed certificate to test it with during the setup wizards of the RDS Gateway. (there is a brought SSL cert available when deployed)
The Test Firewall/Router is setup with a static IP address 192.168.125.199 (192.168.125.n being my Home LAN subnet) and the ports 443 and 3391 are open from my Home LAN to the New PDC 2019 Server which also has a static IP address in the Test LAN.
Now from my own Home LAN PC the idea is to test the RDS Gateway connection to test domain PC or the New PDC 2019 Server with Remote Desktop Program - proving RDS Gateway is configured for deployement.
However, my client PC complains about verifying the identity of the device and network Im try to connect to with RDP on the client. I understood that a self signed SSL cert was supposed to be suffient for this testing purpose. but theres still something Im yet to discover to make this connection work.
- I copied the Self Signed SSL from the New 2019 Server cetificate store and installed on my Home PC client running the RDP and it still complains even though it askes for the User credentials to the New 2019 Server with the RDS gateway installed.
- I get the same issue when connecting to the Test PC on the Test LAN through the RDS Gateway after being asked for the PC/User credentials from the RDP connect request.
Any thoughts on what certs need ot be where would be great because I sort of scratching my head now
The Clients PCs are all Windows 10 V 2009
Regards
Jerry
Continue reading...
Im struggling with getting past the security layering to test an RDS Gateway configured on a 2019 Standard Server. (was easier with Access Anywhere)
Anyway I have a New PDC 2019 Server on a self contained Test LAN behind a router/firewall - connected to my Home LAN via its ethernet WAN port, this all works and the test server can surf the web and I have PC also connected to the test lan in the domain of the PDC 2019 server, That works perfectly too it can access domain resources on the New PDC 2019 server (seperate from my own home domain (2012R2 Server)
Because if the demise of the Essentials and Access Anywhere, I have configured the new PDC 2019 Server with RDS Gateway to enable access to LAN PCs from the internet (when its finally deployed) I setup the RDS Gateway with a self signed certificate to test it with during the setup wizards of the RDS Gateway. (there is a brought SSL cert available when deployed)
The Test Firewall/Router is setup with a static IP address 192.168.125.199 (192.168.125.n being my Home LAN subnet) and the ports 443 and 3391 are open from my Home LAN to the New PDC 2019 Server which also has a static IP address in the Test LAN.
Now from my own Home LAN PC the idea is to test the RDS Gateway connection to test domain PC or the New PDC 2019 Server with Remote Desktop Program - proving RDS Gateway is configured for deployement.
However, my client PC complains about verifying the identity of the device and network Im try to connect to with RDP on the client. I understood that a self signed SSL cert was supposed to be suffient for this testing purpose. but theres still something Im yet to discover to make this connection work.
- I copied the Self Signed SSL from the New 2019 Server cetificate store and installed on my Home PC client running the RDP and it still complains even though it askes for the User credentials to the New 2019 Server with the RDS gateway installed.
- I get the same issue when connecting to the Test PC on the Test LAN through the RDS Gateway after being asked for the PC/User credentials from the RDP connect request.
Any thoughts on what certs need ot be where would be great because I sort of scratching my head now
The Clients PCs are all Windows 10 V 2009
Regards
Jerry
Continue reading...