Has anybody gotten remote desktop to work in AL10 now that VNC no longer exists? I have remote login enabled on port 3389. netstat shows it is listening. I am not logged onto the server I’m trying to connect to. But Windows RDP craps out with, “An internal error has occurred” and AL10 Connections says, “Authentication failed: The connection transport layer failed” systemctl status gnome-remote-desktop show enabled and running.
I’ve spent way too many hours screwing around with this and could use some help.
Thanks
@jmr , hello.
Are you positive you are connecting to the port 3389/tcp on the remote machine in the first place?
Run the a non-stop check of netstat -anpt | egrep 3389; but with the following specifically, on the remote (running RDP service):
watch -n1 "nestat -anpt | egrep 3389"
Execute your rdp-cli connection over to this remote host, then check on the session looking to see if you actually did connect. If you did, you should see the evidence of your client machine’s IP listed in the output, where you are executing the “watch” command.
If you do not, look into your firewalld rules. Perhaps, also start with firewalld not even running.
Respectfully,
Warron
Many thanks. Really appreciate the reply.
Where I’m at with this is simply that with Xorg gone, vncserver gone and rdp failing (I’m following the RHEL 10 documentation) what exactly are the options to get a remote desktop or at least run remote GUI applications?
netstat shows:
tcp6 0 0 :::3389 :::* LISTEN 1036/gnome-remote-d
Tried netwatch, but it fails so fast there’s nothing to catch. I’ve tried with clients from AL9, AL10, Windows 10 and Windows 11, always specifying rdp protocol and port 3389.
Also a telnet to port 3389 fails.
firewalld is running – everything else connects just fine from remote systems.
firewall-cmd --list all port line says,
public (default, active)
ports: 5902/tcp 631/tcp 8983/tcp 3389/tcp 3390/tcp
Don’t think I care what utility to use, I’d just like to find ONE solution!
SOLVED! For me, at least.
Seems setting username and password in Settings/System/Remote Login doesn’t do squat. But as soon as I entered:
# grdctl rdp set-credentials USER PASSWORD
and restarted gnome-desktop-session, everything immediately worked.
That is great news @jmr
I was going to point out that your netstat was only listing a listener on port 3389/tcp but for IPv6, but not IPv4, which could have an impact.
Ironically, your firewalld allowed connectivity to port 3389/tcp but on the public zone. I have no idea what interface was assigned to the Public zone, not on your machine anyway.
However, it looks like the configuration was altered, and you got it corrected.