Replies: 8 comments 6 replies
-
|
Hi @robina80 It's a good question, but the answer is currently 'no'. The right way to fix this is documented in the linked page. I've recently picked up some sesman developments, and I'm hoping to get to this one relatively soon. |
Beta Was this translation helpful? Give feedback.
-
|
hi @matt335672 thanks for the quick reply, do you mean that script kill_xrdp.sh ? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry - not being clear. The correct fix is for sesman to detect when a client is trying to connect to an already connected session, and to disconnect the already connected client. At the moment the links aren't in the software to do that correctly. There are a number of use-cases which need this functionality, including yours. As an example, you might connect to a session at home on a Thursday, but you've already got an active connection open at the office (60km away) from Wednesday. If the workaround script isn't quite working for you, maybe we can refine it. Let me know. |
Beta Was this translation helpful? Give feedback.
-
|
hi @matt335672 tbh i thought the "tcp keepalive" would had sorted it as i thought if the active session is open then the clipboard would still work as the same session is open, but are you saying the active session is still open but when they open up another session (from home) they have two sessions open same time and this is when xrdp gets confused? |
Beta Was this translation helpful? Give feedback.
-
|
The language can be confusing here, so I'll be explicit in what I'm saying.
A keepalive can sort this, but only if it's short enough. If it isn't the user can try to reconnect while the original connection is still active, and then bad things happen. In my example, a keepalive of a few hours would be fine. However, on an enterprise network, a connection can be severed by an internal firewall. If the user immediately tries to reconnect, bad things will happen. |
Beta Was this translation helpful? Give feedback.
-
|
thanks @matt335672 ive found more from the user, he is not opening up a new session from home to the xrdp server, hes accessing the same open session at work as at work hes accessing the xrdp server via his work pc and when he is home he vpns in to his work pc and he finds all of a sudden the clipboard after a few hours just stops working am i making sense |
Beta Was this translation helpful? Give feedback.
-
|
You are making sense to me @robina80 - I hope I'm making sense to you! This is a bit complicated to triage, but I think one of three things is happening:-
A couple of questions for you:-
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
hi @matt335672 the user has no remote drives, ie when they open up rdp on there windows pc and under the "local devices and resources" > more - the "drives" option is not ticked
tbh when the issue happens again with the user i will put the logs here as i think atm the logs arnt really showing any errors apart from the "thin client drive" |
Beta Was this translation helpful? Give feedback.
-
|
For the thinclient_drive error, see #3443 Please post back when it happens. Easiest way to post a log is to place it between triple-backticks, so:- ``` becomes:- HTH, |
Beta Was this translation helpful? Give feedback.
-
|
so it happened again @matt335672 i attach the log I had to edit the actual clipboard file names as we work on sensitive material |
Beta Was this translation helpful? Give feedback.
-
|
That's fine - thanks. The problem seems to be this line, and those like it. Possible reasons are:-
Do any of those sound likely? |
Beta Was this translation helpful? Give feedback.
-
|
hi @matt335672 yes, i do create a new session for the user as the clipboard doesnt work for them anymore, so i kill there session via and they can xrdp into the server again and then the clipboard works for them i dont think i restart sesman as i dont restart the xrdp service on my server? |
Beta Was this translation helpful? Give feedback.
-
|
Well, #3443 definitely applies.
|
Beta Was this translation helpful? Give feedback.
-
|
thank you @matt335672 i have installed fuse3 now so will let you know if it works for the user, if i dont hear anything from him means clipboard is still working :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
hi all,
installed xrdp on alma 9.5 minimum, installed xfce4 as well, the xrdp version is xrdp 0.10.2
i had a problem when an active rdp session timed out and killed the session, resolved this by this link
https://github.com/neutrinolabs/xrdp/wiki/Tips-and-FAQ#how-can-i-prevent-connections-being-dropped-by-my-corporate-firewall
and now my xrdp session and even ssh sessions stay open so all good
but now my users inform me that after a week or so there clipboard stops working, they disconnect there session and log in again but still clipboard isn't working
the only way to solve it is to ssh in, find there active session via "ps -ef | grep vnc" and kill there session, kill the pid or parent pid number
ive found the same issue and work around here
https://github.com/neutrinolabs/xrdp/wiki/Copy-Paste-and-network-drives-don't-work-on-a-reconnect
is there anyway to solve this without having to kill there active session?
thanks,
rob
Beta Was this translation helpful? Give feedback.
All reactions