Remote Desktop Connect

Hi Experts,

I am using my desktop (Win7) to access my servers (Server 2008 R2) and other desktops.
I had to reimage one of my workstations (Win7) and reset it up with the domain controller.

Everything seems to be working fine except that I cannot access the reformatted computer via “Remote Desktop Connect” anymore. All the other connections are working fine.  I did use the same computer name that it was previously called.
 
Is there a way to reset the “Remote Desktop Connect” or clear a cache to get this working?
I am at a total loss.

Thanks in advance!
bmw040Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

buhuhuCommented:
try to connect with:

mstsc /admin (in win 7 and vista)

mstsc /console (in win XP)
0
bmw040Author Commented:
That is what I am using for everything.

I am getting the standard message that it can not be connected.

I did enable remote desktop connection on the reimaged computer.
0
jayaram13Commented:
Did you enable remote desktop for the newly imaged computer?

System Properties -> Remote -> Allow connections...
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

bmw040Author Commented:
Yes I did.

I did all the steps to set it up like all my other computers (that work).

That is why I was thinking that there may be a cache or something that is stopping it from working.

I also was thinking that naming it the same convention may be at fault.

I am just lost.
0
ConUladhCommented:
Is the user you're connecting as an administrator on the detination machine? If not you will need to  go to System Properties -> Remote -> Select Remote users
0
ConUladhCommented:
The only cache that springs to mind is DNS, on the machine you're connecting from go to the command prompt and type ipconfig /flushdns.

May be necessary casue you used the orginal computer name
0
bmw040Author Commented:
Yes, I am logging in as Admin on all machines.

There is a Reset in "Remote Desktop Service Manager" in Server 2008 R2. Unfortunately I can not find anything in Window 7.

0
bmw040Author Commented:
Good Idea however did not work.

I flushed the cashe on both the host and the remote with no success.
0
pascaldeghellCommented:
have you checked the incoming connections on the firewall
try once with the firewall off
0
ConUladhCommented:
Launch gpedit.msc on target machine

Local Computer Policy -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Deny Log on through remote desktop service

Make sure thats empty

There's a few other policies in there that might be relevant as well
0
ConUladhCommented:
and of course make sure that "Allow log on through Remote Desktop service" includes Administrators
0
bmw040Author Commented:
The Local policies all match up and incluses administrator

I am just guessing here: It appears that I am not getting through to my server for this particular computer to verify the admin credentials.

Does that soud possible? If so would flushing the server dns help?
0
ConUladhCommented:
What happens if you try connect to the IP address instead of the computer name?
0
ConUladhCommented:
One more for the target machine, verify or create the following registry value:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server]
"fDenyTSConnections"=dword:00000000
0
bmw040Author Commented:
The reg value was already in place.

Now connecting with the IP does do something.

I get the terminal screen but receive the following message:

"The trust relationship between this workstation and the primary domain failed"
0
athomsfereCommented:
Sounds like when you rebuilt tit it did not rejoin the domain correctly.

I have found that just to be safe I delete the old machine from AD before renaming a machine to the same name. (I give an hour to replicate betweeen delete and adding again if the same name.)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ConUladhCommented:
Following on from athomsfere Remove the target machine from domain (if you get an error you may need to do it while disconnected and delete from AD manually), rename then rejoin to domain
0
bmw040Author Commented:
Solved

I ended up doing the following:

Deleted the computer from the Active Directory.
Unjoin the domain (Joined a WORKGROUP)
Renamed the computer
Rejoined the domain
Ensured it replicated in the AD
I am not sure but I think the renaming of the computer to something other than the first name was the key (I do not know why though???)

Thanks Everyone!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.

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.