Could not remote into Server 2008 R2

Dear Experts, we could not use remote Desktop service into a Win server 2008 R2, it said that "Your credential did not work"; some steps were performed but could not help:
1. Open all Firewall profiles, disable Antivirus
2. Changing password
3. Create a new local user and add to Remote Desktop Group
4. Change remote port
5. Restart RDP service
6. Allow remote desktop service

Any idea please?
LVL 4
TjnoNetwork AdministratorAsked:
Who is Participating?
 
TjnoConnect With a Mentor Network AdministratorAuthor Commented:
Sorry guys, my bad. This is duplicate IP problem. I turned off a host with the same IP and RDP on this server worked again.
0
 
CESNetwork AdministratorCommented:
So by the server saying "Your credentials did not work" that means that it's not a connection issue;  you're successfully getting to the server it's just the username or password is wrong or the account is not part of the RDP users group.

This means that it is not #1,4,5 or 6.

Can you RDP using the local admin account?
0
 
TjnoNetwork AdministratorAuthor Commented:
No I could not, I tried both Local Admin as well as a new local user but did not help!
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
TuliTaivasConnect With a Mentor server adminCommented:
- just to make sure: when you say "local user" you mean local to the server, right?
- any special characters in the password? can you type the password somewhere where you can actually SEE what gets wirtten? (e.g. in the username field). same keyboard layout on server and client?
- no blanks before or after the username (happens here more often than expected)
1
 
Neil RussellTechnical Development LeadCommented:
Ensure that user does not have "Must change password at next logon"  set
1
 
TjnoNetwork AdministratorAuthor Commented:
@Tuli:
just to make sure: when you say "local user" you mean local to the server, right?
---> YES, it is local user on that server

- any special characters in the password?
----> No
can you type the password somewhere where you can actually SEE what gets wirtten? (e.g. in the username field). same keyboard layout on server and client?
-----> Yes, I tried copy paste from txt file but no luck

- no blanks before or after the username (happens here more often than expected)
------> No, it does not have

@Neil: the user had "Password never expired " setting, but no luck
0
 
CESNetwork AdministratorCommented:
what about local logon?  does that work?
0
 
TjnoNetwork AdministratorAuthor Commented:
Yes, it worked.
0
 
TjnoNetwork AdministratorAuthor Commented:
@CES IT: I reviewed the EE link but could not find this option, can you help?

.... on the general tab I changed Security layer from 'Negotiate' to 'RDP Security Layer' and I no longer need to enter credentials to start an RDP session.
0
 
JohnCommented:
If it works as a local logon, but not RDP, then it is the permissions on the listener.  

Generally, add the user to the Remote Desktop Users group and that will do the trick.  If this has been messed with, then you may want to check the permissions on the listener itself.
0
 
JohnConnect With a Mentor Commented:
go to Remote Desktop Session Host Configuration in Admin Tools

Under connections, right click the listener in question (most servers only have one) and select properties

On the security tab, add/remove users and groups.  (Add the user you want to log in as)
0
 
TjnoNetwork AdministratorAuthor Commented:
Hi John, thank you but still no luck, could not remote into that server :(
0
 
JohnCommented:
There are two layers of authentication in 2008 and upwards.  There's authentication with the server (NLA) and then RDP authentication for the session.  

Which one is it failing on?

Have you tried disabling NLA?  

To do this, right click 'My Computer' and select properties

Click on the remote settings link

When system properties comes up, click on the Remote tab

There are 3 selections at the bottom.  pick the middle one (Allow connections from computers running any version of Remote Desktop (less secure))
0
 
TjnoNetwork AdministratorAuthor Commented:
@John: Yes, that middle one option was configured but still no luck
0
 
JohnConnect With a Mentor Commented:
In a command prompt, try

Netstat -ano

Do you have this:?

  Proto  Local Address          Foreign Address        State           PID

  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1176

There will be lots of lines.  It needs to match the line above.  The PID is not important, but the rest is.
0
 
JohnCommented:
did you not get a duplicate IP address warning?
0
 
JohnCommented:
The authentication problem was that you were logging in to serverB with a username and password for serverA due to the IP conflict.  

ServerB must have responded to the ARP request last and got it's MAC address in your ARP cache
1
 
TjnoNetwork AdministratorAuthor Commented:
No, I did not have a warning in the Desktop notification, I only realized this problem when typed: "ipconfig /all"

Many thanks for your support!
0
 
TjnoNetwork AdministratorAuthor Commented:
Problem solved after removed duplicated IP issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.