RDP to Windows 10
-
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'
-
Yeah I heard someone else say this but I have never found a linux client to connect to a RDP session with NLM enabled. What is your client software?
Someone mentioned above that Remmina can do it.
-
@bigbear said in RDP to Windows 10:
Yeah I heard someone else say this but I have never found a linux client to connect to a RDP session with NLM enabled. What is your client software?
Someone mentioned above that Remmina can do it.
Yes, Remmina is what I am using.
-
There is only one difference that I can think of here -
Webroot
But that doesn't seem likely as I'm getting the response that the UserID/Password is incorrect. If it was Webroot it wouldn't even get that far.
-
Which I thought uses FreeRDP, which in turn I thought was stalled in terms of modern RDP compatibility. I really wish there was an RDP client that supports RDP 10, or even 8.2
-
@gjacobse said in RDP to Windows 10:
There is only one difference that I can think of here -
Webroot
But that doesn't seem likely as I'm getting the response that the UserID/Password is incorrect. If it was Webroot it wouldn't even get that far.
disable it and try again.
-
-
So sitting here,.. I figure, okay, lets change the existing password. Maybe re-entering it will 'clear' the issue.
This is when I read the MS lock screen WORDING.
It doesn't say password. is say PIN. Enter your PIN. So,.. What IS the current password? Very.Good.Question....
This is a simple case of MS trying to make things easier - and thusly making them more confusing. So - lets see if I can't rebuild/ reset the PASSWORD.
