RDP to Windows 10
-
@scottalanmiller said in RDP to Windows 10:
User definitely has RDP access rights?
User (me) is machine admin. But worth a check
-
@gjacobse said in RDP to Windows 10:
@scottalanmiller said in RDP to Windows 10:
Firewall is definitely open?
turned it off, for both private and public, no different. Reports username/pass is incorrect.
You either have to be apart of the administrator group or Remote Desktop group.
Is this machine part of a domain environment?
-
@black3dynamite said in RDP to Windows 10:
@gjacobse said in RDP to Windows 10:
@scottalanmiller said in RDP to Windows 10:
Firewall is definitely open?
turned it off, for both private and public, no different. Reports username/pass is incorrect.
You either have to be apart of the administrator group or Remote Desktop group.
Is this machine part of a domain environment?
Not a domain member.
-
In Remmina, what Security are you choosing under the Advanced tab?
-
what other windows type are you trying to RDP from?
-
@Dashrender said in RDP to Windows 10:
what other windows type are you trying to RDP from?
Windows 10
iOS
Fedora using Remmina -
@gjacobse are you trying access a vm on your laptop?
-
@black3dynamite said in RDP to Windows 10:
@gjacobse are you trying access a vm on your laptop?
No, I remote to my laptop from my NTG box, in the past I have been using VNC and that works. But I have run into an issue with Tiger VNC in that I can't access the Work Space(s) or adjust the window size. This prevents me from working in Workspace 1 and having my laptop in WS2
-
Do you need to turn off NLA requirement for Remote Desktop connections on the Win 10 box?
-
@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.
