How do I solve invalid credentials or usernames when connecting to Remote Desktop on Windows 10?
up vote
1
down vote
favorite
It works on my local account but not when I connect my Microsoft Windows Account.
Remote Desktop Settings:
Port 3389 is open:
Tried both my Local IP as well as my public IP for the PC Name.
MicrosoftAccountgoogle@gmail.com for the (DOMAIN/user)
I've even reset my Microsoft account password and have verified it's the correct one.
I verified my Windows Firewall Inbound Rules.
When I use the Microsoft Remote Desktop Assistant it just gives my local IP/username info which is what I tried above.. same as the whoami output.
My network is indeed set to private.
I tried to connect via my Phone/laptop both ON the Wi-Fi using my local IP and disconnected from WiFi (LTE) using the public IP. Just says, "The user name or password did not work" or "Invalid Credentials."
Any ideas?
remote-desktop remote windows-10
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
migrated from serverfault.com Mar 26 '17 at 19:54
This question came from our site for system and network administrators.
add a comment |
up vote
1
down vote
favorite
It works on my local account but not when I connect my Microsoft Windows Account.
Remote Desktop Settings:
Port 3389 is open:
Tried both my Local IP as well as my public IP for the PC Name.
MicrosoftAccountgoogle@gmail.com for the (DOMAIN/user)
I've even reset my Microsoft account password and have verified it's the correct one.
I verified my Windows Firewall Inbound Rules.
When I use the Microsoft Remote Desktop Assistant it just gives my local IP/username info which is what I tried above.. same as the whoami output.
My network is indeed set to private.
I tried to connect via my Phone/laptop both ON the Wi-Fi using my local IP and disconnected from WiFi (LTE) using the public IP. Just says, "The user name or password did not work" or "Invalid Credentials."
Any ideas?
remote-desktop remote windows-10
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
migrated from serverfault.com Mar 26 '17 at 19:54
This question came from our site for system and network administrators.
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot thatSelect users...button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.
– Run5k
Mar 26 '17 at 20:39
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
It works on my local account but not when I connect my Microsoft Windows Account.
Remote Desktop Settings:
Port 3389 is open:
Tried both my Local IP as well as my public IP for the PC Name.
MicrosoftAccountgoogle@gmail.com for the (DOMAIN/user)
I've even reset my Microsoft account password and have verified it's the correct one.
I verified my Windows Firewall Inbound Rules.
When I use the Microsoft Remote Desktop Assistant it just gives my local IP/username info which is what I tried above.. same as the whoami output.
My network is indeed set to private.
I tried to connect via my Phone/laptop both ON the Wi-Fi using my local IP and disconnected from WiFi (LTE) using the public IP. Just says, "The user name or password did not work" or "Invalid Credentials."
Any ideas?
remote-desktop remote windows-10
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
It works on my local account but not when I connect my Microsoft Windows Account.
Remote Desktop Settings:
Port 3389 is open:
Tried both my Local IP as well as my public IP for the PC Name.
MicrosoftAccountgoogle@gmail.com for the (DOMAIN/user)
I've even reset my Microsoft account password and have verified it's the correct one.
I verified my Windows Firewall Inbound Rules.
When I use the Microsoft Remote Desktop Assistant it just gives my local IP/username info which is what I tried above.. same as the whoami output.
My network is indeed set to private.
I tried to connect via my Phone/laptop both ON the Wi-Fi using my local IP and disconnected from WiFi (LTE) using the public IP. Just says, "The user name or password did not work" or "Invalid Credentials."
Any ideas?
remote-desktop remote windows-10
remote-desktop remote windows-10
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
edited Mar 26 '17 at 20:49
Run5k
10.5k72749
10.5k72749
asked Mar 26 '17 at 19:18
Supa
613
asked Mar 26 '17 at 19:18
Supa
613
asked Mar 26 '17 at 19:18
Supa
613
613
migrated from serverfault.com Mar 26 '17 at 19:54
This question came from our site for system and network administrators.
migrated from serverfault.com Mar 26 '17 at 19:54
This question came from our site for system and network administrators.
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot thatSelect users...button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.
– Run5k
Mar 26 '17 at 20:39
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17
add a comment |
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot thatSelect users...button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.
– Run5k
Mar 26 '17 at 20:39
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot that
Select users... button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.– Run5k
Mar 26 '17 at 20:39
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot that
Select users... button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.– Run5k
Mar 26 '17 at 20:39
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Step 1: Ensure you have a local account on the computer you are trying to access.
Step 2: Make sure that account is in the list of users (screenshot above)
Step 3: Enabling remote desktop means you must have a password that conforms to 8 characters minimum, one number, one capital and one non-alpha-numeric.
After confirming you have done all that correctly you will be able to login. As you can already see the login screen the problem has nothing to do with your firewall.
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Step 1: Ensure you have a local account on the computer you are trying to access.
Step 2: Make sure that account is in the list of users (screenshot above)
Step 3: Enabling remote desktop means you must have a password that conforms to 8 characters minimum, one number, one capital and one non-alpha-numeric.
After confirming you have done all that correctly you will be able to login. As you can already see the login screen the problem has nothing to do with your firewall.
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
add a comment |
up vote
0
down vote
Step 1: Ensure you have a local account on the computer you are trying to access.
Step 2: Make sure that account is in the list of users (screenshot above)
Step 3: Enabling remote desktop means you must have a password that conforms to 8 characters minimum, one number, one capital and one non-alpha-numeric.
After confirming you have done all that correctly you will be able to login. As you can already see the login screen the problem has nothing to do with your firewall.
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
add a comment |
up vote
0
down vote
up vote
0
down vote
Step 1: Ensure you have a local account on the computer you are trying to access.
Step 2: Make sure that account is in the list of users (screenshot above)
Step 3: Enabling remote desktop means you must have a password that conforms to 8 characters minimum, one number, one capital and one non-alpha-numeric.
After confirming you have done all that correctly you will be able to login. As you can already see the login screen the problem has nothing to do with your firewall.
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
Step 1: Ensure you have a local account on the computer you are trying to access.
Step 2: Make sure that account is in the list of users (screenshot above)
Step 3: Enabling remote desktop means you must have a password that conforms to 8 characters minimum, one number, one capital and one non-alpha-numeric.
After confirming you have done all that correctly you will be able to login. As you can already see the login screen the problem has nothing to do with your firewall.
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
answered Mar 26 '17 at 21:42
JohnnyVegas
2,4231714
2,4231714
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
add a comment |
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
1
1
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
There is no password length or complexity requirement for RDP. There just has to be a password.
– Twisty Impersonator
Mar 26 '17 at 23:01
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1192606%2fhow-do-i-solve-invalid-credentials-or-usernames-when-connecting-to-remote-deskto%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There are two important factors to consider. First of all, the machine that you are trying to access via RDP is utilizing Windows 10 Pro and not the Home version, correct? Last but not least, in your first screen shot that
Select users...button is crucial. Essentially, the account you are using to RDP into the distant-end machine needs to either be a member of one of two groups on the remote machine: either the Administrators group or the Remote Desktop Users group.– Run5k
Mar 26 '17 at 20:39
I've suffered the same. I know there is a problem logging into Win10 from Win7 and visa versa. If no one else chimes in, late tonight I'll look to see if I figured it out. Can't remember if I broke through or gave up a year ago.
– ejbytes
Mar 26 '17 at 21:57
Oh, and all machines have to be on the same Work Group, in Win 10 it's something similar different name.
– ejbytes
Mar 26 '17 at 22:03
So I logged into RDP as a local user.. then switched back to my microsoft account and it worked. Not sure why.. :/
– Supa
Mar 27 '17 at 2:17