Freerdp is a client not the server. As far as I know for windows you’d need to use something like no machine or teamviewer for that kind of functionality (or upgrade to pro for the rdp function)
@socphoenix@On RDP server and client is Microsoft built-in, but bound to license restrictions. In general, 2 concurrent rdp sessions on one machine are possible without a need to extend the standard Windows license / price. You can add and license the rdp services role / terminalserver role to a machine setup and have more flexibility: more users, more administration of user sessions.
If your target is a Windows machine, you need a user that is a member of the target machine’s local rdp or local admin security group, either directly or via a domain security group, start a client software (below) depending on your machine’s operating system, enter the target machine’s address (ip or name) and user name and password, and have a desktop session on the target machine in a window to remote comtrol it. You might need a VPN or citrix connection to the target’s domain and you might need to qualify a user domain of your login credentials, but that’s it in general.
* Windows: You can use Windows built-in RDP client mstsc.exe. There are alternatives and wrappers. I found that using mstsc.exe through RDP+ (https://donkz.nl) is the most reliable, comfortable, and safely automatable solution.
* Linux: You need a client software. I use Remmina (often in your distribution’s standard repository) for that purpose. I understand from FreeRDP’s linked and the github pages that FreeRDP is a concurrent client. It’s tagged »Android« too. I usually need to work on the target and wouldn’t torture myself with a mini and touch screen for RDP, so I personally don’t mind.
You always need to try which client software works best in your situation and setup. So testing if FreeRDP is a client, and if for your operating system, can be done on the run.
@socphoenix@On You have other possibilities with Windows targets for remote control. You could set up the Windows built-in OpenSSH or another SSH server on the target, use Kitty SSH client, and tunnel RDP through SSH tunnel. Use FreeTube or NewPipe to find tutorial clips for that. If only classic SSH on the command line is possible, I’d prefer PowerShell remoting, if your client is on Windows too.
You wouldn’t usually bother to implement RDP services with Linux targets, if not forced to by policies.
In summary, Microsoft RDP can be easiest, because built-in. Can be obligatory. There are prequisites: access to the target’s domain (VPN, SSH, Citrix, …), entitled user credentials, client software, knowledge of target’s internal address / hostname.
@socphoenix@On If nothing with RDP necessary or possible: https://rustdesk.com/ is the easiest and recommended, it’s much like Teamviewer but free. (Free as in FLOSS, and free of charge as well.) It works with most operating system combinations. Technically, it has nothing to do with the concurrent protocols / standards Microsoft RDP, Teamviewer, SSH, …
The rdp client (at least in 10/11, I haven’t tried others) tells me I need at least pro instead of home to use it, thus my comment about upgrading windows. Thank you for the extra clarification for those that can use it though!
RDPWrp used to be able to run a patched version of RDP for Windows Home to enable incoming RDP but it isn’t maintained anymore. You didn’t need to upgrade to Pro.
@On@const_void@socphoenix RDP server = software on remote control target. So if this is about allowing incoming remote control on a Windows Home client machine: Use Rustdesk. ( https://rustdesk.com/ )
Windows Home is crippled. Microsoft in general is just a data vacuum cleaner, but functionally OK. But Windows Home …
Afaik Rustdesk server isn’t opensource and you’re limited to using their free servers in Europe for relay. I just need an alternative for lan remote desktop.
Freerdp is a client not the server. As far as I know for windows you’d need to use something like no machine or teamviewer for that kind of functionality (or upgrade to pro for the rdp function)
@socphoenix @On RDP server and client is Microsoft built-in, but bound to license restrictions. In general, 2 concurrent rdp sessions on one machine are possible without a need to extend the standard Windows license / price. You can add and license the rdp services role / terminalserver role to a machine setup and have more flexibility: more users, more administration of user sessions.
If your target is a Windows machine, you need a user that is a member of the target machine’s local rdp or local admin security group, either directly or via a domain security group, start a client software (below) depending on your machine’s operating system, enter the target machine’s address (ip or name) and user name and password, and have a desktop session on the target machine in a window to remote comtrol it. You might need a VPN or citrix connection to the target’s domain and you might need to qualify a user domain of your login credentials, but that’s it in general.
1/x
@socphoenix @On If the machine you are working at is on
* Windows: You can use Windows built-in RDP client mstsc.exe. There are alternatives and wrappers. I found that using mstsc.exe through RDP+ (https://donkz.nl) is the most reliable, comfortable, and safely automatable solution.
* Linux: You need a client software. I use Remmina (often in your distribution’s standard repository) for that purpose. I understand from FreeRDP’s linked and the github pages that FreeRDP is a concurrent client. It’s tagged »Android« too. I usually need to work on the target and wouldn’t torture myself with a mini and touch screen for RDP, so I personally don’t mind.
You always need to try which client software works best in your situation and setup. So testing if FreeRDP is a client, and if for your operating system, can be done on the run.
2/x
@socphoenix @On You have other possibilities with Windows targets for remote control. You could set up the Windows built-in OpenSSH or another SSH server on the target, use Kitty SSH client, and tunnel RDP through SSH tunnel. Use FreeTube or NewPipe to find tutorial clips for that. If only classic SSH on the command line is possible, I’d prefer PowerShell remoting, if your client is on Windows too.
You wouldn’t usually bother to implement RDP services with Linux targets, if not forced to by policies.
In summary, Microsoft RDP can be easiest, because built-in. Can be obligatory. There are prequisites: access to the target’s domain (VPN, SSH, Citrix, …), entitled user credentials, client software, knowledge of target’s internal address / hostname.
3/4
@socphoenix @On If nothing with RDP necessary or possible: https://rustdesk.com/ is the easiest and recommended, it’s much like Teamviewer but free. (Free as in FLOSS, and free of charge as well.) It works with most operating system combinations. Technically, it has nothing to do with the concurrent protocols / standards Microsoft RDP, Teamviewer, SSH, …
The rdp client (at least in 10/11, I haven’t tried others) tells me I need at least pro instead of home to use it, thus my comment about upgrading windows. Thank you for the extra clarification for those that can use it though!
RDPWrp used to be able to run a patched version of RDP for Windows Home to enable incoming RDP but it isn’t maintained anymore. You didn’t need to upgrade to Pro.
@On @const_void @socphoenix RDP server = software on remote control target. So if this is about allowing incoming remote control on a Windows Home client machine: Use Rustdesk. ( https://rustdesk.com/ )
Windows Home is crippled. Microsoft in general is just a data vacuum cleaner, but functionally OK. But Windows Home …
Afaik Rustdesk server isn’t opensource and you’re limited to using their free servers in Europe for relay. I just need an alternative for lan remote desktop.