RDP to Windows 10
-
@momurda said in RDP to Windows 10:
Do you need to turn off NLA requirement for Remote Desktop connections on the Win 10 box?
I think so.
-
Most common thing I saw with my short lived RDSH deployment was CAPS LOCK ON.
So you are getting the error "Your credentials did not work"??
-
Maybe it is NLA, but there is normally some setting on Windows that needs to be disabled for this.
-
@StrongBad from a legacy client (most linux clients) where NLA is enabled and the client doesnt support it, you do typically get an authentication error.
If you allow less secure connections from the remote settings tab it disables NLA, but it also makes the connection less secure.
I dont remember it says "bad username/password" but when I tried this recently I believe it was more of a "connection refused or connection reset error".
-
I'm able to use remmina on fedora to remote successfully to my windows 10 vm and I have NLA enabled too.
-
@black3dynamite what rdp version does remains support??
-
@bigbear said in RDP to Windows 10:
@black3dynamite what rdp version does remains support??
8, I think
-
On your Windows 10 device, do you have this box checked:
-
Have the user or password any "strange" character like "ñ" "ç"...
It could be the problem
-
Are you using a Microsoft Account? If you are, then you may have to logon as
MicrosoftAccount\[email protected] in order for it to work.
-
@bigbear said in RDP to Windows 10:
Most common thing I saw with my short lived RDSH deployment was CAPS LOCK ON.
So you are getting the error "Your credentials did not work"??
CAPS lock is not on.
-
This isn't Remote Assistance - That is unchecked
Allow Remote Connection Checked. Tried with both with and without NLA - both fail.
-
@dafyre said in RDP to Windows 10:
Are you using a Microsoft Account? If you are, then you may have to logon as
MicrosoftAccount\[email protected] in order for it to work.
I dislike using or requiring the use of the MS account. So this is a local computer account only.
-
@iroal said in RDP to Windows 10:
Have the user or password any "strange" character like "ñ" "ç"...
It could be the problem
No odd characters - Other than the user.... me
-
@gjacobse said in RDP to Windows 10:
@dafyre said in RDP to Windows 10:
Are you using a Microsoft Account? If you are, then you may have to logon as
MicrosoftAccount\[email protected] in order for it to work.
I dislike using or requiring the use of the MS account. So this is a local computer account only.
OK along these lines try %computername%\account on that PC
-
@gjacobse said in RDP to Windows 10:
This isn't Remote Assistance - That is unchecked
Allow Remote Connection Checked. Tried with both with and without NLA - both fail.
Yeah that's the window it's on. I don't have that on my personal laptop which is what I was on then... I thought the breadcrumbs I left would get you there, and it did! (even though it didn't resolve your issue)
-
@Dashrender said in RDP to Windows 10:
@gjacobse said in RDP to Windows 10:
@dafyre said in RDP to Windows 10:
Are you using a Microsoft Account? If you are, then you may have to logon as
MicrosoftAccount\[email protected] in order for it to work.
I dislike using or requiring the use of the MS account. So this is a local computer account only.
OK along these lines try %computername%\account on that PC
Yea, did that too.. nope.
-
You need to uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication" if you are using an older version of RDP (typically from a linux client).
Not clear from the thread above whether that is what you are doing though.
-
Different laptop - Pre/post... Was able to connect once I turned on Allow Remote Connections.
-
@bigbear said in RDP to Windows 10:
You need to uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication" if you are using an older version of RDP (typically from a linux client).
Not clear from the thread above whether that is what you are doing though.
Don't think it matters. The Windows 10 system I just connected to still has it turned on. So - can't be the 'difference'
