Microsoft, Server 2003, Remote Desktop/Terminal Services no longer works after cloning drive.

In order to update server hardware, I cloned the drive from the old server and used it to re-build the server with new hardware.  However, the new server will no longer accept Remote Desktop connections.  It will initiate RD sessions to other computers, but will not accept them.  In all other respects, the cloning was successful.  The RD problem is the only issue that has arisen.
freeteckAsked:
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.

ltxdaCommented:
Because there are several ways to approach this problem I'm providing a link which provides many resources for the different approaches:

http://ts.veranoest.net/ts_trouble.htm
0
cemal_ozunCommented:
What does the event log say when you try to RDP on to the server? Have you applied any updates/pathes to the server after the restoring from the image?
0
freeteckAuthor Commented:
I have not found a relevant event log entry, but I may have missed something.  Again, the user who tries to connect via RDP is simply sent a standard message that the session was refused.
No patches/ no updates.
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

cemal_ozunCommented:
A good way to check the event log would be to save all and then clear it. Once you have done this try to RDP and keep an eye on the event log. Would be good  have a copy of the event log after the above is completed.
Can you provide further information on your setup, is the a TS machine for multiple users or just a standard 2003 box? Thanks
0
lecafCommented:
is the firewall off ?

m   a   r   c
0
cemal_ozunCommented:
I am guessing that you configured the new NIC with the same settings as the old one , i.e. static ip, subnet, dns etc. Since its a hardware replacement it could be a diferent brand NIC hence not configured with default settings.
0
freeteckAuthor Commented:
I will check the Event Log as suggested.
Terminal Services Installed, 10 licenses.
It will not accept an RD session from inside the local network, either.  Firewall not an issue.  The Windows firewall is off.
The NIC on the new server has been tried with identical settings from the old server (old server offline) and with different settings.  Same result.  It sees the connection, but refuses it.
 
0
lecafCommented:
10 licenses ??? then its TS...is the licensing server still reachable? was it installed on the cloned disk ?
probably you ll need to reactivate it.

m  a  r   c  

0
cemal_ozunCommented:
As test please try to rdp to localhost when logged on to the server. Also please ensure that the TS is listenting on all NIC's and not bound to the old NIC none existing NIC
0
freeteckAuthor Commented:
Not sure about the licensing server, but I believe it's reachable.  Will try it tomorrow to be sure.
Will definitely look at the re-activation tomorrow..
TS is listening on all all NIC's.  That has been checked.
Will try to RDP to localhost tomorrow.
0
ChiefITCommented:
SP2 has a little problem with RDP:

See the section, "RDP / RWW stop working after installation of SP2:"
http://www.lan-2-wan.com/2003-SP2.htm
0
freeteckAuthor Commented:
Hello all,
Thankyou for your helpful suggestions.
The solution was simple but not easy to track down.
During the transfer of the cloned hard drive to the new server, all hardware-related items are removed/uninstalled from the device manager in order to get the operating system ready to discover and accept the hardware on the new server.  When this was done, the "Terminal Server Device Redirector" was deleted in the Device Manager/System Devices by mistake.  I re-cloned the drive and did not remove "Terminal Server Device Redirector" the second time.
Everything worked like a charm.
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
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
Microsoft Server OS

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.