We had an issue with remote assistance that when the SID's were changed
after ghosting the machines.
You said freshly formatted, but has it been imaged?
It isn't exactly the same as Remote desktop, but maybe this is the
Also I would make sure that you are changing SID's just in case you are
running into an issue where two machines have the same SID, preventing
Remote Desktop. We've been using NEWSID from sysinternals, and it is a
I've fixed odd problems with machines hanging on login by just running
newsid a couple of times until it was successful and then adding it back
to the domain.
Tim Skutt, MCTS, MCSA
Information Technologist I
Eli Broad College of Business
Michigan State University
5 Eppley Center
East Lansing, MI 48824
(517)884-1593 - Direct
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Peter J Murray
Sent: Monday, October 15, 2007 11:20 AM
To: [log in to unmask]
Subject: [MSUNAG] remote desktop puzzler
I'm having a weird problem with remote desktop on a new computer. It's
an Optiplex 745, and what happens is that remote desktop stops answering
after a while, but will always work after a reboot. I've checked the
1) No RD or Terminal Services events in the event log besides the
normal the service has started.
2) Using Windows Firewall, port 3389 open
3) Remote Desktop enabled and user has permissions to use it (it works
until it stops listening).
4) All patches and such have been installed.
5) Freshly formatted machine, no RD problems on other machines.
The same configuration works on a lot of other machines.
Googling isn't very helpful, I get the idea that it either works really
well, or it's a fairly obvious firewall problem when you do have
problems. The lack of entries in the event log regarding a stoppage is
really not helpful.