Armitage318
asked on
Cannot connect the remote desktop after rename
Hi, today I renamed a Windows 2012 R2 server (joined to active directory).
After that, I am not able anymore to access with Terminal server (even with Administrator).
I tried with dns name and with IP address, same error.
Server has been restarted, of course
How can I troubleshoot this?
After that, I am not able anymore to access with Terminal server (even with Administrator).
I tried with dns name and with IP address, same error.
Server has been restarted, of course
How can I troubleshoot this?
Verify that the DNS entry is updated. If not, delete the old DNS entry and manually create a new one pointing to a new name.
and don't forget to update the reverse lookup .ptr record
ASKER
Hi Seth, the error is:
Remote Desktop Connection
This computer can’t connect to the remote computer.
Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
ASKER
Hi Hello there, hi David.
DNS is fine (even PTR)
DNS is fine (even PTR)
I would reboot the remote computer.
ASKER
Hi Hello There,
after reboot, same behavior.
Anyway, I noticed some issues in DNS.
I will open a new question for this.
after reboot, same behavior.
Anyway, I noticed some issues in DNS.
I will open a new question for this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi hecgomrec ,
with /admin I am able to access Remote Desktop... but what can I do to restore the "original" behavior?
Now I also removed this PC from AD domain, and tried to access with local administrator account.
It didn't worked (but it worked with /admin as I wrote)
Thank you
ASKER
Sorry, I wasn't aware initally: this server is linked to another License Server (for Remote Desktop service).
Anyway, even after renaming this machine, it is still able to see licenses available from the other server (License Server):
it seems I regularly have my 10 licenses available!
Anyway, even after renaming this machine, it is still able to see licenses available from the other server (License Server):
it seems I regularly have my 10 licenses available!
By default, once you activate any of the remote desktop services roles, the remote connections to that server will limited. I noticed this years ago when deployed this feature for the first time in my organization.
I don't know if you can change it by GPO or registry, I never play with it as I like the way it is for added security. All my other servers in the organization can be signed in without this extra line on the computer name.
And of course, if you others servers for Broker, License, etc., changing the name of this server won't change the rest of the configuration.
Good Luck!
I don't know if you can change it by GPO or registry, I never play with it as I like the way it is for added security. All my other servers in the organization can be signed in without this extra line on the computer name.
And of course, if you others servers for Broker, License, etc., changing the name of this server won't change the rest of the configuration.
Good Luck!
ASKER
Hi hecgomrec ,
sorry, I don't fully understand your answer.
Could I remove/reinstall again remote desktop services roles?
I confirm that I renamed the "client" PC, not the one with the Remote Deskop Licensing role.
Thank you
sorry, I don't fully understand your answer.
Could I remove/reinstall again remote desktop services roles?
I confirm that I renamed the "client" PC, not the one with the Remote Deskop Licensing role.
Thank you
what is the error?