Ticket #3487 (closed defect: fixed)
Windows Remote Desktop client fails to connect to VRDP with authentication
|Reported by:||nimdae||Owned by:|
When enabling VRDP with authentication (external or guest), using the latest RDP client from Microsoft will fail to connect.
Host: Ubuntu 8.04 Guest: Windows XP and Vista (all versions)
The problem appears to be that the VRDP service is expecting authentication details to be sent when the client is requesting a session. However, the latest version of RDP client appears to wait for the service to request authentication and does not allow entering of authentication credentials before connection. All you can enter is the user name.
This is what is found in the log:
00:41:56.048 VRDP: New connection: 00:41:56.069 VRDP: Flags 0x0000001b 00:41:56.069 VRDP: Channel: [rdpdr] . Not supported. 00:41:56.069 VRDP: Channel: [rdpsnd] . Accepted. 00:41:56.069 VRDP: Channel: [drdynvc] . Not supported. 00:41:56.069 VRDP: Channel: [cliprdr] . Accepted. 00:41:56.163 VRDP: Client seems to be MSFT. 00:41:56.163 VRDP: Logon: xxxxxxxx (xxx.xxx.xxx.xxx) build 6001. User:  Domain:  Screen: 0 00:41:56.164 VRDPAUTH: User: . Domain: . Authentication type: [External] 00:41:58.203 VRDPAUTH: external authentication module returned 'access denied' 00:41:58.203 VRDPAUTH: Access denied. 00:41:58.203 VRDP: Connection closed: 00:41:58.203 VRDP: Logoff: xxxxxxxx (xxx.xxx.xxx.xxx) build 6001. User:  Domain:  Reason 0x0001.
This is debug information when attempting a connection without entering anything else:
u, d, p init ok Using PAM service: vrdpauth start ok conv: num 1 u p conv: 0 returning password  pam_authenticate failed 10. User not known to the underlying authentication module vrdpauth_pam_close completed
This is debug information when entering the user name, which is all that is allowed to be entered in the client:
u[administrator], d, p init ok Using PAM service: vrdpauth start ok conv: num 1 u[administrator] p conv: 0 returning password  pam_authenticate failed 7. Authentication failure vrdpauth_pam_close completed
It does not prompt for credentials. Instead, I get the following two errors before the RDP client exits:
Your Remote Desktop session has ended. Your network administrator might have ended the connection. Try connecting again, or contact technical support for assistance.
Your Remote Desktop session is about to end. This computer might be low on virtual memory. Close your other programs, and then try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support.
As mentioned, I believe the VRDP server is expecting credentials when establishing a session, and the client does not provide them, while the client is expecting a request for credentials and disconnecting when the server does not make the request and instead ends the session.
Remote Desktop client is 6.0.6001, supporting RDP 6.1.
I didn't see much information on this, but I have this problem on multiple systems with similar fairly basic configurations.
comment:13 Changed 5 years ago by piousminion
- Status changed from closed to reopened
- Resolution fixed deleted
comment:15 Changed 5 years ago by klaus
- Status changed from reopened to closed
- Resolution set to fixed