Abraham Deutsch
asked on
Credentials for remote desktop connection
A mix network environment. Some computers join the Domain some not.
When connecting with Remote desktop to a computer that is not joined the domain.
Credentials.
user name - your credentials did not work.
Computer name\ user name - your credentials did not work.
Workgroup\user name - your credentials did not work.
What are the credentials that will work?
When connecting with Remote desktop to a computer that is not joined the domain.
Credentials.
user name - your credentials did not work.
Computer name\ user name - your credentials did not work.
Workgroup\user name - your credentials did not work.
What are the credentials that will work?
In most cases, you can use the following:
\[username]
where [username] is the username of a local user account, not a domain account. You also need to make sure that local user account has remote access privileges on the target system.
Sometimes the lone backslash isn't good enough and you might have to use [computername]\[username]. I've only ever seen that being necessary once and I never did figure out why.
\[username]
where [username] is the username of a local user account, not a domain account. You also need to make sure that local user account has remote access privileges on the target system.
Sometimes the lone backslash isn't good enough and you might have to use [computername]\[username].
And the account you use must be an administrator ar added to the Remote Desktop Users group.
Also, check System Properties->Remote (tab) that Remote Desktop connections are allowed.
Also, check System Properties->Remote (tab) that Remote Desktop connections are allowed.
The part about adding the user to the Remote Desktop User and Local Permissions is nothing to concern yourself with right away. Neither of those are critical for logging in. They will give you errors after logging in but are not part of your current problems.
It should be ComputerName\Username but as mentioned just username should work since it is not part of a domain. I would take the time to sit at that computer (not RDPing in to it. Actually sit at it.) and try logging in. Once you get the issue resolved when sitting in front of it RDP should just fall in to place.
It should be ComputerName\Username but as mentioned just username should work since it is not part of a domain. I would take the time to sit at that computer (not RDPing in to it. Actually sit at it.) and try logging in. Once you get the issue resolved when sitting in front of it RDP should just fall in to place.
ASKER
Locally by logging in with username and password works great.
The issue is only when logging in using RD and as machined
Credentials already tried;
user name
Computer name\ user name
Workgroup\user name
The issue is only when logging in using RD and as machined
Credentials already tried;
user name
Computer name\ user name
Workgroup\user name
Assuming credentials are correct it is likely that remote access is not properly configured for the account. Check the remote access settings to make sure that:
1. Remote access is allowed
2. The user(s) attempting to log in have been granted remote access permissions
1. Remote access is allowed
2. The user(s) attempting to log in have been granted remote access permissions
ASKER
Administrators are by default allowed to access remotely if remote is allowed to the computer
"The issue is only when logging in using RD and as machined" can you explain "and as machined"?
Can you also tell us the exact error message you get and maybe include a screen shot?
Can you also tell us the exact error message you get and maybe include a screen shot?
ASKER
Sorry typo error "Mentioned"
See attached
PS for testing purposes I joined the computer to the domain, and was able to login.
RD-Credentials.JPG
See attached
PS for testing purposes I joined the computer to the domain, and was able to login.
RD-Credentials.JPG
So from that screen you select "Use another account", type in ComputerName\Administrator for the users, the local administrator password and it won't log in?
ASKER
Correct
I cannot recreate the problem. I have a fresh load of Windows 10 on a computer named "Optiplex3040". Enabled Remote Desktop on it. Connected from my computer and got the same screen up that you posted. For the username I used Optiplex3040\Administrator , used the local administrator account (on that computer) and it logged right in.
The face that you can use a domain account would suggest RDP is working. Are you sure it isn't some kind of caps lock issue with the password or something simple like that?
The face that you can use a domain account would suggest RDP is working. Are you sure it isn't some kind of caps lock issue with the password or something simple like that?
ASKER
See attached maybe will this be a help for clarification on the environment.
Computer-Workoup.JPG
Public-network.JPG
Computer-Workoup.JPG
Public-network.JPG
Based on the screen shots the login should be HP-Laptop\Administrator with whatever password goes with that. You can use another local username but for debug purposes I would use Administrator to start.
IB.local should probably be a "Work" network shouldn't it? It is your company network? That will make a difference in your firewall settings but I don't think it will affect the credentials issue you are having.
Speaking of which.... go in to Credential Manager and see if you have any "Windows Credentials". Delete them if you do. They could be corrupt.
IB.local should probably be a "Work" network shouldn't it? It is your company network? That will make a difference in your firewall settings but I don't think it will affect the credentials issue you are having.
Speaking of which.... go in to Credential Manager and see if you have any "Windows Credentials". Delete them if you do. They could be corrupt.
ASKER
IB.local in the domain name
ASKER
I see I can't ping it!!!!!
ib.local is the domain name but it shouldn't be a public network I don't believe. It should be a work network. You can't ping it? Didn't you just log in to it with your domain credentials and get to it via RDP?
I'd turn off the Firewall(s) temporarily to test. Turn off the windows firewall and any third party firewalls. Hopefully you only have 1 firewall, as having more than 1 is not recommenced.
ASKER
Your username is 8460p but your display name is Frad. They can be different but 99% of the time they are the same for reasons you just experienced. I would suggest shooting the administrator of that computer :)
ASKER
I am the administrator
Is there a way to correct this?
Is there a way to correct this?
You mentioned that you joined that computer to the domain for testing purposes and it worked (I'm assuming you disconnected it from domain now). Is there a reason why you can't leave it joined to the domain?
This question is also for other computers in the "mixed" network that are not currently joined to the domain. Unless there is reasons why not to, save yourself future headaches and get them all joined.
This question is also for other computers in the "mixed" network that are not currently joined to the domain. Unless there is reasons why not to, save yourself future headaches and get them all joined.
You can edit the local user and make the username the same as the display name. If you administer the domain don't you have a set way of creating users? Like firstname.lastname or FirstInitialLastName? Do the same for local users. I do, however, agree with NetAdmin2436. You have a domain. I would make it a "standard" to join all computers to the domain unless there is a really, really good reason not to. There is a lot to be said for picking a standard and sticking to it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You got it correct.
Do you have a link easier to follow than the one provided?
Do you have a link easier to follow than the one provided?
Computer name\Local Username
Also, make sure that remote desktop is enabled and that the local user on the non domain computer has permission.
....all in all a headache to manage domain and non domain computers.