The credentials that were used to connect to did not work

RDP: «The credentails that were used to connect to did not work.»

When trying to RDP into a server, login box gives error that «The credentails that were used to connect to did not work. Please enter new credentials.»

A workaround involves entering the following line into one’s default.rdp, which bypasses local authentication and lets it happen directly on the server:

However, users normally ‘remoteapp’ into this server, which gives the same error. Where should this change be made then? I tried putting it in the server’s Public Documents folder, but no change.

I do not know where this issue came from, but the reports appear to have started this weekend. Server is internal, on a domain. Same issue on any W7+ clients.

The server’s firewall is off.

Server has been rebooted multiple times.

Thanks for any guidance.

Popular Topics in Windows Server

9 Replies

Are the users coming from a different domain?

If yes are they putting in domain\username

However, users normally ‘remoteapp’ into this server, which gives the same error. Where should this change be made then? I tried putting it in the server’s Public Documents folder, but no change.

You can either edit the Registry on the RDWeb server. Which is where the properties of the Remoteapp web page icons are stored.

Or use powershell

I would be more interested in why you are getting the credential error. When did this start? Are you disallowing saved logins? That may be causing it. Or there may be an issue with NLA.

Selfstudy is an IT service provider.

Do you have enough RDP licenses? You need 1 for each device or one for each user.

Do you have enough RDP licenses? You need 1 for each device or one for each user.

Are you thinking about terminal server?

RDP allows 2 remote connections, and if a license was exceeded it would say this, not password errors.

The answer was found in the experts-exchange link. In TS Configuration, I changed the secure layer setting from ‘Negotiate’ to ‘RDP Secure Layer’. Tested fine immediately.

I had read the first link already before posting, but just now realized that I haven’t seen that second one.

No clue as to why that changed. Very glad it’s fixed. Thank you.

The answer was found in the experts-exchange link. In TS Configuration, I changed the secure layer setting from ‘Negotiate’ to ‘RDP Secure Layer’. Tested fine immediately.

I had read the first link already before posting, but just now realized that I haven’t seen that second one.

No clue as to why that changed. Very glad it’s fixed. Thank you.

Specifically, this began happening when we went from an internal LAN connection to the server over VPN, and on domain, to an external connection from a public IP. For some reason we were seeing intermittent issues with authentication, where 1 in 5 or 10 connections wouldn’t negotiate properly. We saw the issue on Windows 10 Enterprise and Server 2008 R2.

«the credentials that were used to connect to» [server] «did not work.» was the specific error.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Snap! UEFI bootloaders, SOVA Android banking trojan, Black Hat, Excel Champions

Your daily dose of tech news, in brief. Welcome to Monday! I’m unsure how accurate this date is but supposedly, on August 15, 1994, Microsoft engineer Ben Slivka sent an email message suggesting to his colleagues that a World Wide Web browser shoul.

Spark! Pro series – 15th August 2022

The cartoon today got me on a Carrot theme for this Spark! So, you get a carrot themed Spark! “What’s up Doc?” Top Ten Band Names Replaced With the Word Carrot 1. My Chemical Carrot (My Chemical Roma.

IT on a budget (school)

Hi all, I am assigned as the IT person to a new school. At this school the budget is completely government regulated and budget for IT is very limited and almost non existent. Although they are receiving new laptops by the end of this year, most comput.

Sometimes only people outside yourself and your family can give you the advice that changes your life in a major way. For Bill Kindle, it happened in a private conversation at a VMware User Group. At the time, Bill, like many others was suffering from a.

What forms of wireless communication couldn’t you live without?

The credentials that were used to connect to did not work

Вопрос

I can access the server from my XP machine, so the problem must be on the windows 7 machine somewhere.

I hope you can help me.

Ответы

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

Все ответы

Please refer to the suggestions from the link below to troubleshoot the issue.

I tried those steps and i still get the samme error. I’m also sure that the server i working as i have no problem accessing it from my xp computer, and i have doublechecked the IP, and it is correct.

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

I encountered the same problem. Remote Desktop worked fine with Windows XP but failed when I tried to run it with Windows 7. The problem turned out to be that the firewal was blocking the Reomote Desktop port. Try the following:

If you’re using Windows Firewall:

Restart Remote Desktop. and everything should hopefully now work.

I have the same problem with original poster.

XP Machines have no problem connecting to Brand New Windows 2008 Terminal Server.

But only Windows 7 Machines can’t.

I tried all kinds of suggestions, but it still does not work.

Windows Firewall on Windows 2008 server has remote desktop already checked.

I even tried to disable Windows Firewall, but still the same problem.

Can someone help?

I know this is way after the fact but I ran into something similar. The RDP from XP would open fine and did not have that initial login prompt. RDP from Win7 failed because I couldn’t get past that extra login prompt.

I placed the following line in it, saved it, and then launched it:

enablecredsspsupport:i:0

Found the info here:

Just had exactly the same problem but the answer was very simple for me.

in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

This error can happen if you generate a «standard» copy of windows server 2008 r2 and try to use it as the base VHD file, for creating other new servers. We did this so we wouldn’t have to keep re-installing 2008 R2 and applying all the service packs, in our virtual environment. If you try this, you have to run the sysprep utility against your base copy of the VHD, before deploying it to other systems, as a Virtual Machine. So, remove the VM that you want to use, from the existing domain and put it in a workgroup. Then run sysprep.

When you re-boot a copy of your now «standard» VHD, you will have to re-join a domain and you’ll have to change the name of the VM, because sysprep will set it to something strange. For more information, see here:

Or simply do what Ray says:

1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
3) Tick the ‘Generalize’ option (this resets the SID)
4) Select ‘Shutdown’ from the Shutdown Options.
5) Once the machine has shutdown, take your image and you are good to go!

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

What was the solution? I have 15 desktops running windows 7, I can’t connect via RDP from a windows XP box when it is using NLA. When I unckeck NLA I can connect without any issues. I can’t go to all 15 systems to physically log in and disable NLA and I don’t have access to the group policies on our servers. Does anyone know a way to disable NLA remotley. or a fix to this RDP authentication issue? I can’t actually start trying to resolve the actual problem these 15 machines are having without being able to RDP in.

Thanks for the advice. Worked like a charm. We have a Windows AD Domain, and I had to specify that the credentials were domain (domain\username) instead of just username.

What do you do when none of these solutions work?

I’ve literally done thousands of PCs and this problem suddenly cropped up on brand spankin- new machines. Verified firewall, password, network settings, tried new profile, checked login credentials (machine\loginname) etc. Still no dice, no remote access. I’ll try to fully patch the Win 7 x64 machine, but this is ridiculous (it works for the other 100+ windows x64 Pro machines, why not these new ones? Is there a difference?

Thanks a million! This worked for me. I would not have thought of that.

regarding AndersSorensens problem, this worked for me:

asuming all settings on the computer you want to connect to (might be your «work PC») are set properly (..connections from computers running any version.. ; allow remote access ; etc.)

The PC with which you want to connect to your PC at Work (might be your «Home PC»):

— «windows security» dialog box: «enter your credentials»

—> klick: «use another account»

—> Login: «your login at Work PC»@»domain name of your work PC» /alternatively: @»complete computer name of your work PC»

—> PW: «your password at work»

You get the domain / computer name of your work PC as follows: (only at your work PC of course, NOT the home PC)

i use to have the same problem, what happen is, sometimes when you change
your user name the computer never reconize it, and remain the same in local disk (c) user folder.

then you will find a folder with a lock on it, then use this folder name for your user name on remote desktop.

We are having this exact problem with few of our Windows 7 workstations. Funny thing is that some Win7 workstations can make the RDP connection to the server with out a problem (like my own) but then some give that «The credentials that were. » error.

We know those accounts work because they function from RDP connection made from my workstation (and when you log on locally from console) but not from my collegues workstation. It does not matter if you try to log on with a domain user account or a local user account. It does not matter if you user domain\user or user@domain type of credentials while connecting. Our RDP settings are identical (we copied my local.rdp to his machine). Funny part is that from the machine that does not work you can still lock the user account by entering wrong password few times in a row. When you use correct user/password it just gives the «The credentials. » error but does not lock the user account.

I have already tried about anything I can imagine (from disabling NLA to all the possible RDP settings in the server side). Though the setting work fine with my Win7 workstation. I cannot figure out what is different in our workstations so that mine work but his doesnt.

If anyone has any suggestions I will gladly take the input 🙂

The credentials that were used to connect to did not work

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I can access the server from my XP machine, so the problem must be on the windows 7 machine somewhere.

I hope you can help me.

Answers

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

All replies

Please refer to the suggestions from the link below to troubleshoot the issue.

I tried those steps and i still get the samme error. I’m also sure that the server i working as i have no problem accessing it from my xp computer, and i have doublechecked the IP, and it is correct.

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

I encountered the same problem. Remote Desktop worked fine with Windows XP but failed when I tried to run it with Windows 7. The problem turned out to be that the firewal was blocking the Reomote Desktop port. Try the following:

If you’re using Windows Firewall:

Restart Remote Desktop. and everything should hopefully now work.

I have the same problem with original poster.

XP Machines have no problem connecting to Brand New Windows 2008 Terminal Server.

But only Windows 7 Machines can’t.

I tried all kinds of suggestions, but it still does not work.

Windows Firewall on Windows 2008 server has remote desktop already checked.

I even tried to disable Windows Firewall, but still the same problem.

Can someone help?

I know this is way after the fact but I ran into something similar. The RDP from XP would open fine and did not have that initial login prompt. RDP from Win7 failed because I couldn’t get past that extra login prompt.

I placed the following line in it, saved it, and then launched it:

enablecredsspsupport:i:0

Found the info here:

Just had exactly the same problem but the answer was very simple for me.

in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

This error can happen if you generate a «standard» copy of windows server 2008 r2 and try to use it as the base VHD file, for creating other new servers. We did this so we wouldn’t have to keep re-installing 2008 R2 and applying all the service packs, in our virtual environment. If you try this, you have to run the sysprep utility against your base copy of the VHD, before deploying it to other systems, as a Virtual Machine. So, remove the VM that you want to use, from the existing domain and put it in a workgroup. Then run sysprep.

When you re-boot a copy of your now «standard» VHD, you will have to re-join a domain and you’ll have to change the name of the VM, because sysprep will set it to something strange. For more information, see here:

Or simply do what Ray says:

1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
3) Tick the ‘Generalize’ option (this resets the SID)
4) Select ‘Shutdown’ from the Shutdown Options.
5) Once the machine has shutdown, take your image and you are good to go!

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

What was the solution? I have 15 desktops running windows 7, I can’t connect via RDP from a windows XP box when it is using NLA. When I unckeck NLA I can connect without any issues. I can’t go to all 15 systems to physically log in and disable NLA and I don’t have access to the group policies on our servers. Does anyone know a way to disable NLA remotley. or a fix to this RDP authentication issue? I can’t actually start trying to resolve the actual problem these 15 machines are having without being able to RDP in.

Thanks for the advice. Worked like a charm. We have a Windows AD Domain, and I had to specify that the credentials were domain (domain\username) instead of just username.

What do you do when none of these solutions work?

I’ve literally done thousands of PCs and this problem suddenly cropped up on brand spankin- new machines. Verified firewall, password, network settings, tried new profile, checked login credentials (machine\loginname) etc. Still no dice, no remote access. I’ll try to fully patch the Win 7 x64 machine, but this is ridiculous (it works for the other 100+ windows x64 Pro machines, why not these new ones? Is there a difference?

Thanks a million! This worked for me. I would not have thought of that.

regarding AndersSorensens problem, this worked for me:

asuming all settings on the computer you want to connect to (might be your «work PC») are set properly (..connections from computers running any version.. ; allow remote access ; etc.)

The PC with which you want to connect to your PC at Work (might be your «Home PC»):

— «windows security» dialog box: «enter your credentials»

—> klick: «use another account»

—> Login: «your login at Work PC»@»domain name of your work PC» /alternatively: @»complete computer name of your work PC»

—> PW: «your password at work»

You get the domain / computer name of your work PC as follows: (only at your work PC of course, NOT the home PC)

i use to have the same problem, what happen is, sometimes when you change
your user name the computer never reconize it, and remain the same in local disk (c) user folder.

then you will find a folder with a lock on it, then use this folder name for your user name on remote desktop.

We are having this exact problem with few of our Windows 7 workstations. Funny thing is that some Win7 workstations can make the RDP connection to the server with out a problem (like my own) but then some give that «The credentials that were. » error.

We know those accounts work because they function from RDP connection made from my workstation (and when you log on locally from console) but not from my collegues workstation. It does not matter if you try to log on with a domain user account or a local user account. It does not matter if you user domain\user or user@domain type of credentials while connecting. Our RDP settings are identical (we copied my local.rdp to his machine). Funny part is that from the machine that does not work you can still lock the user account by entering wrong password few times in a row. When you use correct user/password it just gives the «The credentials. » error but does not lock the user account.

I have already tried about anything I can imagine (from disabling NLA to all the possible RDP settings in the server side). Though the setting work fine with my Win7 workstation. I cannot figure out what is different in our workstations so that mine work but his doesnt.

If anyone has any suggestions I will gladly take the input 🙂

The credentials that were used to connect to did not work

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I can access the server from my XP machine, so the problem must be on the windows 7 machine somewhere.

I hope you can help me.

Answers

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

All replies

Please refer to the suggestions from the link below to troubleshoot the issue.

I tried those steps and i still get the samme error. I’m also sure that the server i working as i have no problem accessing it from my xp computer, and i have doublechecked the IP, and it is correct.

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

I encountered the same problem. Remote Desktop worked fine with Windows XP but failed when I tried to run it with Windows 7. The problem turned out to be that the firewal was blocking the Reomote Desktop port. Try the following:

If you’re using Windows Firewall:

Restart Remote Desktop. and everything should hopefully now work.

I have the same problem with original poster.

XP Machines have no problem connecting to Brand New Windows 2008 Terminal Server.

But only Windows 7 Machines can’t.

I tried all kinds of suggestions, but it still does not work.

Windows Firewall on Windows 2008 server has remote desktop already checked.

I even tried to disable Windows Firewall, but still the same problem.

Can someone help?

I know this is way after the fact but I ran into something similar. The RDP from XP would open fine and did not have that initial login prompt. RDP from Win7 failed because I couldn’t get past that extra login prompt.

I placed the following line in it, saved it, and then launched it:

enablecredsspsupport:i:0

Found the info here:

Just had exactly the same problem but the answer was very simple for me.

in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

This error can happen if you generate a «standard» copy of windows server 2008 r2 and try to use it as the base VHD file, for creating other new servers. We did this so we wouldn’t have to keep re-installing 2008 R2 and applying all the service packs, in our virtual environment. If you try this, you have to run the sysprep utility against your base copy of the VHD, before deploying it to other systems, as a Virtual Machine. So, remove the VM that you want to use, from the existing domain and put it in a workgroup. Then run sysprep.

When you re-boot a copy of your now «standard» VHD, you will have to re-join a domain and you’ll have to change the name of the VM, because sysprep will set it to something strange. For more information, see here:

Or simply do what Ray says:

1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
3) Tick the ‘Generalize’ option (this resets the SID)
4) Select ‘Shutdown’ from the Shutdown Options.
5) Once the machine has shutdown, take your image and you are good to go!

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

What was the solution? I have 15 desktops running windows 7, I can’t connect via RDP from a windows XP box when it is using NLA. When I unckeck NLA I can connect without any issues. I can’t go to all 15 systems to physically log in and disable NLA and I don’t have access to the group policies on our servers. Does anyone know a way to disable NLA remotley. or a fix to this RDP authentication issue? I can’t actually start trying to resolve the actual problem these 15 machines are having without being able to RDP in.

Thanks for the advice. Worked like a charm. We have a Windows AD Domain, and I had to specify that the credentials were domain (domain\username) instead of just username.

What do you do when none of these solutions work?

I’ve literally done thousands of PCs and this problem suddenly cropped up on brand spankin- new machines. Verified firewall, password, network settings, tried new profile, checked login credentials (machine\loginname) etc. Still no dice, no remote access. I’ll try to fully patch the Win 7 x64 machine, but this is ridiculous (it works for the other 100+ windows x64 Pro machines, why not these new ones? Is there a difference?

Thanks a million! This worked for me. I would not have thought of that.

regarding AndersSorensens problem, this worked for me:

asuming all settings on the computer you want to connect to (might be your «work PC») are set properly (..connections from computers running any version.. ; allow remote access ; etc.)

The PC with which you want to connect to your PC at Work (might be your «Home PC»):

— «windows security» dialog box: «enter your credentials»

—> klick: «use another account»

—> Login: «your login at Work PC»@»domain name of your work PC» /alternatively: @»complete computer name of your work PC»

—> PW: «your password at work»

You get the domain / computer name of your work PC as follows: (only at your work PC of course, NOT the home PC)

i use to have the same problem, what happen is, sometimes when you change
your user name the computer never reconize it, and remain the same in local disk (c) user folder.

then you will find a folder with a lock on it, then use this folder name for your user name on remote desktop.

We are having this exact problem with few of our Windows 7 workstations. Funny thing is that some Win7 workstations can make the RDP connection to the server with out a problem (like my own) but then some give that «The credentials that were. » error.

We know those accounts work because they function from RDP connection made from my workstation (and when you log on locally from console) but not from my collegues workstation. It does not matter if you try to log on with a domain user account or a local user account. It does not matter if you user domain\user or user@domain type of credentials while connecting. Our RDP settings are identical (we copied my local.rdp to his machine). Funny part is that from the machine that does not work you can still lock the user account by entering wrong password few times in a row. When you use correct user/password it just gives the «The credentials. » error but does not lock the user account.

I have already tried about anything I can imagine (from disabling NLA to all the possible RDP settings in the server side). Though the setting work fine with my Win7 workstation. I cannot figure out what is different in our workstations so that mine work but his doesnt.

If anyone has any suggestions I will gladly take the input 🙂

The credentials that were used to connect to did not work

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I can access the server from my XP machine, so the problem must be on the windows 7 machine somewhere.

I hope you can help me.

Answers

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

All replies

Please refer to the suggestions from the link below to troubleshoot the issue.

I tried those steps and i still get the samme error. I’m also sure that the server i working as i have no problem accessing it from my xp computer, and i have doublechecked the IP, and it is correct.

I suggest you create a new admin account and login on the machine with new created account to check the result. If the issue persists, please restart the machine with the original user account and collect the following log file for research.

Collect Event log

a. Click «Start», input «eventvwr» (without quotation marks) in the Start Search bar and press Enter.

b. Right click on «Application» on the left frame, choose «Save Log file As»; in the pop-up window, click to choose the Desktop icon on the left frame, input «app» in the «File name» blank, and then click save.

c. Right click on «System», with the same method, save it as «sys».

I encountered the same problem. Remote Desktop worked fine with Windows XP but failed when I tried to run it with Windows 7. The problem turned out to be that the firewal was blocking the Reomote Desktop port. Try the following:

If you’re using Windows Firewall:

Restart Remote Desktop. and everything should hopefully now work.

I have the same problem with original poster.

XP Machines have no problem connecting to Brand New Windows 2008 Terminal Server.

But only Windows 7 Machines can’t.

I tried all kinds of suggestions, but it still does not work.

Windows Firewall on Windows 2008 server has remote desktop already checked.

I even tried to disable Windows Firewall, but still the same problem.

Can someone help?

I know this is way after the fact but I ran into something similar. The RDP from XP would open fine and did not have that initial login prompt. RDP from Win7 failed because I couldn’t get past that extra login prompt.

I placed the following line in it, saved it, and then launched it:

enablecredsspsupport:i:0

Found the info here:

Just had exactly the same problem but the answer was very simple for me.

in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

This error can happen if you generate a «standard» copy of windows server 2008 r2 and try to use it as the base VHD file, for creating other new servers. We did this so we wouldn’t have to keep re-installing 2008 R2 and applying all the service packs, in our virtual environment. If you try this, you have to run the sysprep utility against your base copy of the VHD, before deploying it to other systems, as a Virtual Machine. So, remove the VM that you want to use, from the existing domain and put it in a workgroup. Then run sysprep.

When you re-boot a copy of your now «standard» VHD, you will have to re-join a domain and you’ll have to change the name of the VM, because sysprep will set it to something strange. For more information, see here:

Or simply do what Ray says:

1) Run Sysprep (on Windows Server 2008 this is located in c:\Windows\System32\Sysprep\Sysprep.exe)
2) Ensure ‘System Out-of-Box Experience (OOBE)’ is selected
3) Tick the ‘Generalize’ option (this resets the SID)
4) Select ‘Shutdown’ from the Shutdown Options.
5) Once the machine has shutdown, take your image and you are good to go!

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

«in the RDP dialog I clicked the Options button to get at the advanced settings and in the general tab I put the username as DOMAIN\USERNAME as when the username and password was being sent to the server it was sending as HP-PC\USERNAME which of course was not the same domain as our server therefore was being rejected.

Check the system logs on the server and see if the logon attempt is 1. getting that far 2. the reason for refusal of the logon.

this was the answer for me.

so simple.. yet my frustration level was so high, i would have never found this on my own. tough to think when angry.. anyway.. thanks.

What was the solution? I have 15 desktops running windows 7, I can’t connect via RDP from a windows XP box when it is using NLA. When I unckeck NLA I can connect without any issues. I can’t go to all 15 systems to physically log in and disable NLA and I don’t have access to the group policies on our servers. Does anyone know a way to disable NLA remotley. or a fix to this RDP authentication issue? I can’t actually start trying to resolve the actual problem these 15 machines are having without being able to RDP in.

Thanks for the advice. Worked like a charm. We have a Windows AD Domain, and I had to specify that the credentials were domain (domain\username) instead of just username.

What do you do when none of these solutions work?

I’ve literally done thousands of PCs and this problem suddenly cropped up on brand spankin- new machines. Verified firewall, password, network settings, tried new profile, checked login credentials (machine\loginname) etc. Still no dice, no remote access. I’ll try to fully patch the Win 7 x64 machine, but this is ridiculous (it works for the other 100+ windows x64 Pro machines, why not these new ones? Is there a difference?

Thanks a million! This worked for me. I would not have thought of that.

regarding AndersSorensens problem, this worked for me:

asuming all settings on the computer you want to connect to (might be your «work PC») are set properly (..connections from computers running any version.. ; allow remote access ; etc.)

The PC with which you want to connect to your PC at Work (might be your «Home PC»):

— «windows security» dialog box: «enter your credentials»

—> klick: «use another account»

—> Login: «your login at Work PC»@»domain name of your work PC» /alternatively: @»complete computer name of your work PC»

—> PW: «your password at work»

You get the domain / computer name of your work PC as follows: (only at your work PC of course, NOT the home PC)

i use to have the same problem, what happen is, sometimes when you change
your user name the computer never reconize it, and remain the same in local disk (c) user folder.

then you will find a folder with a lock on it, then use this folder name for your user name on remote desktop.

We are having this exact problem with few of our Windows 7 workstations. Funny thing is that some Win7 workstations can make the RDP connection to the server with out a problem (like my own) but then some give that «The credentials that were. » error.

We know those accounts work because they function from RDP connection made from my workstation (and when you log on locally from console) but not from my collegues workstation. It does not matter if you try to log on with a domain user account or a local user account. It does not matter if you user domain\user or user@domain type of credentials while connecting. Our RDP settings are identical (we copied my local.rdp to his machine). Funny part is that from the machine that does not work you can still lock the user account by entering wrong password few times in a row. When you use correct user/password it just gives the «The credentials. » error but does not lock the user account.

I have already tried about anything I can imagine (from disabling NLA to all the possible RDP settings in the server side). Though the setting work fine with my Win7 workstation. I cannot figure out what is different in our workstations so that mine work but his doesnt.

If anyone has any suggestions I will gladly take the input 🙂