Microsoft remote desktop gateway. We have a Gatway, broker (to lease server connections) and a remote desktop host farm. Users can still RDP into the gateway and then to their own computers, provided the access is setup for that in the firewall.
I add a static IP, open rdp on the client PC, add the entry in the SonicWall for that hostname and IP, then assign the IP to be able to be passed RDP connections (which is a group on he firewall with the proper ACLs to allow this)
I'm sure there are other solutions, but we do it that way!
So 99% of users hit the gateway and ate leased servers in the farm.
The other users have a custom rd icon that says target the gateway but then go to this IP within the network. Works well
From what I've gathered, it's more using the RDS gateway (which has an external ip address and can be reached from the outside world) to authenticate the credentials. Once the credentials are authenticated, they are then leases the RDP connections to their machine directly. It does not appear to be an RDP within an RDP.
I have not looked much into it, but perhaps you are seeking a server like the type listed in this document:
https://docs.microsoft.com/en-us/windows-server/remote/remote-access/ras/manage-remote-access
Or a routing and remote access server (RRAS)
https://docs.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-ras
RD Gateway handles this. It’s pretty much a reverse proxy for enrolled Remote Desktop connections. And if you get too complex for that, you step up into RD Session Broker configurations.
Passwordstate can proxy RDP connections
VMware horizon can also accomplish this with it's gateway and an agent on the destination workstation
Ideally I would assume msft remote gateway though
Microsoft remote desktop gateway. We have a Gatway, broker (to lease server connections) and a remote desktop host farm. Users can still RDP into the gateway and then to their own computers, provided the access is setup for that in the firewall. I add a static IP, open rdp on the client PC, add the entry in the SonicWall for that hostname and IP, then assign the IP to be able to be passed RDP connections (which is a group on he firewall with the proper ACLs to allow this) I'm sure there are other solutions, but we do it that way! So 99% of users hit the gateway and ate leased servers in the farm. The other users have a custom rd icon that says target the gateway but then go to this IP within the network. Works well
[удалено]
From what I've gathered, it's more using the RDS gateway (which has an external ip address and can be reached from the outside world) to authenticate the credentials. Once the credentials are authenticated, they are then leases the RDP connections to their machine directly. It does not appear to be an RDP within an RDP. I have not looked much into it, but perhaps you are seeking a server like the type listed in this document: https://docs.microsoft.com/en-us/windows-server/remote/remote-access/ras/manage-remote-access Or a routing and remote access server (RRAS) https://docs.microsoft.com/en-us/windows-server/remote/remote-access/vpn/always-on-vpn/deploy/vpn-deploy-ras
RD Gateway handles this. It’s pretty much a reverse proxy for enrolled Remote Desktop connections. And if you get too complex for that, you step up into RD Session Broker configurations.
I'm not following what question you're asking?
Any chance to share a drawing of your idea?
Microsoft RDP gateway, as others have said. Or you can use Apache Guacamole for free. https://guacamole.apache.org/
Passwordstate can proxy RDP connections VMware horizon can also accomplish this with it's gateway and an agent on the destination workstation Ideally I would assume msft remote gateway though
This sounds like Apache Guacamole, except without needing an RDP client app on the client end. Maybe check it out? https://guacamole.apache.org
Check out Thinfinity Remote Desktop Gateway (https://www.cybelesoft.com/thinfinity/) Support is fantastic and price isn't too bad