New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft RDP error code 0x4 extended 0x0 #3015
Comments
@superbonaci - which backend are you using? |
Thanks. Also, when the error happens, can you reconnect to your previous session, or when you try, do you get a new session? |
I don't know what means a new session or same session, how can I figure it out? |
Imagine you're logged in and doing stuff. You go away and come back, and you've got the above error. When you log back in, can you pick up where you left off, or does it look as if you're starting again? |
So you're being disconnected from your session. When the error happens, can you do the following:-
Thanks. |
Here are the logs just after the error and reconnecting:
|
Those don't seem to contain anything useful I'm afraid, which is partly my fault.
I think we'll need complete logs. Can you do the following:-
When the problem re-occurs, attach both complete logs to another post. Thanks. |
I had to reboot the computer with xrdp because I was stuck in a black screen with the KDE mouse X icon. After the reboot I logged in fine. |
@superbonaci - thanks for the logs. It's still not clear what's happening. In your
These messages are caused by a regular port scanner, or health test. See #2040 for more details on why. Some questions for you:-
Thanks. |
The test computer which I connect to could be in some kind of corporate network.
|
I can't tell you where the port scan is coming from as you've sensibly replaced the IP address in the log with an underscore character:-
If you've got an IT support organisation in your company I suggest you contact them and ask them. The reason I'm asking about the corporate network is that if you're routing over it, it's possible that idle TCP connections are being dropped. We've got a FAQ about this - see https://github.com/neutrinolabs/xrdp/wiki/Tips-and-FAQ#how-can-i-prevent-connections-being-dropped-by-my-corporate-firewall. The symptoms match your problem description. |
I will try that, but I think that if I connect to a remove Windows instead of xrdp that doesn't happen. Maybe the Windows RDP server automatically does the keep alive thing, or maybe the corporate firewalls can detect something different and don't drop it? This is the value of
|
There's more traffic between a Window RDP server and a Windows RDP client as there are more features supported. |
xrdp version
0.9.25
Detailed xrdp version, build options
I have xrdp installed on Fedora 39, and connect to it from Windows 11. It connects perfectly and works if I have activity. However if I minimize the Windows RDP window, even using Windows 11 normally, after a while I get the error. May be related to some timeout, screen locking, etc.? Doesn't look like a connectivity issue.
Operating system & version
Windows 11 22621.1413
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
No response
What desktop environment do you use?
KDE/Plasma
Environment xrdp running on
No response
What's your client?
No response
Area(s) with issue?
Authentication
Steps to reproduce
connect from Windows to Linux and stop activity.
✔️ Expected Behavior
keep working
❌ Actual Behavior
error
Anything else?
No response
The text was updated successfully, but these errors were encountered: