Skip to content
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

Wrong error code when NLA auth fails #2434

Closed
giox069 opened this issue Mar 1, 2015 · 3 comments
Closed

Wrong error code when NLA auth fails #2434

giox069 opened this issue Mar 1, 2015 · 3 comments

Comments

@giox069
Copy link
Contributor

giox069 commented Mar 1, 2015

From remmina issue https://github.com/FreeRDP/Remmina/issues/507

Trying to connect to a Windows 7 machine, using xfreerdp + NLA:

xfreerdp /sec:nla /v:mypc.remotedom.dom:21017 /u:jsmith /d:domain

When I type a WRONG password, freerdp sets the wrong error code to FREERDP_ERROR_CONNECT_TRANSPORT_FAILED [0x2000D]

[20:17:03:515] [30711:1583720192] [ERROR][com.freerdp.core] - freerdp_set_last_error 0x2000D
[20:17:03:516] [30711:1583720192] [ERROR][com.freerdp.client.x11] - Authentication only, exit status 1

The last working xfreerdp is commit eddfee5 of Feb 15, which correctly calls freerdp_set_last_error(FREERDP_ERROR_AUTHENTICATION_FAILED) [0x20009].
Here is the output when I type a wrong NLA password in the older freerdp.

[20:02:41:159] [29131:-501631232] [ERROR][com.freerdp.core.nla] - nla_recv() error: -1
[20:02:41:159] [29131:-501631232] [ERROR][com.freerdp.core] - freerdp_set_last_error 0x20009
[20:02:41:159] [29131:-501631232] [ERROR][com.freerdp.core.transport] - Authentication failure, check credentials.If credentials are valid, the NTLMSSP implementation may be to blame.
[20:02:41:159] [29131:-501631232] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure
[20:02:41:160] [29131:-501631232] [ERROR][com.freerdp.client.x11] - Authentication only, exit status 1

@lemonmojo
Copy link
Contributor

+1
connectErrorCode is always set to CONNECTERROR.

@lemonmojo
Copy link
Contributor

Also, when using a Remote Desktop Gateway, there's currently no way of knowing whether the gateway or destination host credentials have been rejected (apart from looking at the log which isn't feasible in GUI-only applications).

@giox069
Copy link
Contributor Author

giox069 commented Dec 8, 2015

@lemonmojo: I'm closing this issue thanks to PR #2824 merged. For Remote Desktop Gateway, test it and reopen a new one if the problem is still here.

@giox069 giox069 closed this as completed Dec 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants