Hi there
Still battling with the broken RDP since I installed a VNC with the wrong desktop environment. Timeshift didn't put 'every little thing back together again', and rdp between the two Zorin PC's is still sick.
I get this result in terminal
xrdp.service - xrdp daemon
Loaded: loaded (/lib/systemd/system/xrdp.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2025-10-04 19:18:42 NZDT; 1min 27s ago
Docs: man:xrdp(8)
man:xrdp.ini(5)
Process: 43197 ExecStartPre=/bin/sh /usr/share/xrdp/socksetup (code=exited, status=0/SUCCESS)
Process: 43205 ExecStart=/usr/sbin/xrdp $XRDP_OPTIONS (code=exited, status=1/FAILURE)
CPU: 12ms
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation systemd[1]: Starting xrdp daemon...
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation xrdp[43205]: [INFO ] address [0.0.0.0] port [3389] mode 1
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation xrdp[43205]: [INFO ] listening to port 3389 on 0.0.0.0
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation xrdp[43205]: [ERROR] g_tcp_bind(7, 3389) failed bind IPv6 (errno=98) and IPv4>
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation xrdp[43205]: [ERROR] trans_listen_address failed
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation xrdp[43205]: [ERROR] Failed to start xrdp daemon, possibly address already in>
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation systemd[1]: xrdp.service: Control process exited, code=exited, status=1/FAILU>
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation systemd[1]: xrdp.service: Failed with result 'exit-code'.
Oct 04 19:18:42 zcdadmin-HP-Z210-Workstation systemd[1]: Failed to start xrdp daemon.
~
~
~
~
and terminal never completes the command, meaning it doesn't go back to the username $.
Local networks shares are working, both win10 and Zorin.
thinking it might be time to do a clean install, which is stupid, just for an RDP issue.
As usual people, any suggestions.
cheers CD
EDIT Update - the files app has refused to open again, so I'm going for a fresh install.
Edit - update x2
The files app won't open but after installing Thunar (which I like) I have file management back.. cheers CD
Hi there
I've got it, the password for the RDP authentication on my remote (well, it's in the cupboard) is resetting itself every time the system is restarted.
[videos remove by me to save space - resend available]
Any suggestions before I reinstall the whole OS ?!?!
cheers CD
P.S. - I have brought the pro version, (every little helps) this doesn't happen on that version.
I have no experience with RDP but the error message from your first post suggests that there's another service running that is already listening the same network port.
sudo ss -ntlp
This will list all processes that are running and listening for network connections, and on which ports. If you find something running on port 3389, make a note of the process name that appears on the last column on the right. You can terminate it through System Monitor, searching for that process name or process ID.
Have you checked the firewall settings as well? The port in use is 3389, in case you are running it and need to open that one up.
The firewall is disabled.
here's the line from the terminal command:
LISTEN 0 10 *:3389 : users:(("gnome-remote-de",pid=1914,fd=60))
there is only entry with that port number.
But surely the problem is that the RDP authentication password for the receiving computer is changed every time it restarts!?
cheers CD
So, just to make sure I understand this correctly, the issue is that you can or cannot connect to the remote server? And if you can, is it that you must enter the password every time?
I just noticed that another thread where you're talking about a similar problem, are these two the same issue?
And lastly, what client are you using to establish the connection? By default, Remmina comes installed with Zorin OS, or are you using a different one?
Hi there, thanks for your reply.
There are two issues here, both to do with the RDP connection through REMMINA. # 1 was posted before #2.
The fact that the RDP connection will fail to connect if:
a) the remote Zorin PC has gone into screen blank mode
b) it has no monitor connected.
This issue was apparent before I followed the (now aware of) 'outdated' instructions to get a VNC remote access to the same Zorin PC, setup using tigervnc. I had already tried VNC through REMMINA but failed to get it to work.
Is that since I did try those instructions (which didn't work and as well, broke the Nautilus/Zorin file manager).
The Zorin PC will reset it's own RDP authentication, by itself automatically, every time the PC is restarted.
Thus making it impossible to RDP into it because one doesn't know the password it requires.
So may request is/was for suggestions on a fix, before I go ahead and reinstall the Zorin OS from scratch. Something I'd rather not do, since I spent quite some time setting up that machine for my plex, SQBox and Asset media servers.
It does, thank you. As I said I've no experience with RDP... I'll try to my hands on a spare computer later today and see if I can figure something out.
Some more poking around revealed:
when a folder is marked as a 'public share' in Thunar, it wasn't actually showing as a share in the network. But if it is marked in the 'Files' app (nautilus) as a share, is does appear as a share.
I have now removed Thunar. This required 2x terminal commands, (the software installer app did nothing).
Regards RDP from main pc to remote.
When the password that is automatically generated by the remote pc, is used, the RDP will connect as expected. If the admin password for that pc is entered instead of the automatically generated password, the RDP will fail to connect.
Ok I think I have sorted the sharing issue caused by me using the incorrect/outdated instructions to install tigervnc in zorin core and pro.
Firstly on the remote pc (core), I restored the 'timeshift' image taken before this all started.
Then 'Reinstalling' on both pc's, Zorin desktop and gnome-shell and Nautilus-share and cifs-utils and Remmina and upgrading all available apps, and setting up a smb password in terminal, as well as entering that PW in each rdp link.
And the 'cherry on the top', I think I also fixed, the RDP connection cutting off as soon as the 'screen blank' time limit is reached, by using a dummy 'HDMI monitor plug'.
So far all seems good, so here's hoping.
Cheers for all replies on this matter. You people are a great help.
This manual setting only last two restarts, now it is resetting the password for remote desktop, automatically by itself again.. bummmm
I need help again people, sorry. Q. what can be wrong with the system not remembering the password assigned to it.?!
EDIT - Q#2
If I install an additional 3rd party VNC program, will it rely on the same settings as the in-built remote desktop setup does in Zorin?? in other words might i have the same problem with any vnc or rdp setup???
Sorry, I've been quite absent from the forum lately as I've been busy outside. I still haven't got the time to look into this but it sounds to me like this makes sense:
The RDP server has its own username and password that you can set. It would be a very bad idea, security-wise, to give away the administrator's password to anyone who needs to connect remotely to this machine.
You did all the work!
If the problem is on the remote host, the server you're connecting to, then I would expect the issue to persist. But I don't think it would share the same settings either way. The Gnome shell used to power the desktop environment has its own internal drivers for networking; A separate third-party client would likely use its own settings.
Did you restore to a previous snapshot through Timeshift, maybe?
For SMB, I would recommend setting an entry in the /etc/fstab file which controls the rules for mounting drives, partitions and network shares. You can see an example in the thread below, where you can create a file with the credentials to use, which shouldn't be overwritten by any update or anything.
Thank you. I did see that post. I'll be waiting to finally read how more experienced users are successfully using os 18 with both Samba and vnc. I currently don't have the patience to try all the possible solutions...