Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2008-10-26
12
Medium Priority
?
491 Views
Last Modified: 2013-11-21
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.
0
Comment
Question by:freeteck
  • 4
  • 4
  • 2
  • +2
12 Comments
 
LVL 4

Expert Comment

by:ltxda
ID: 22809519
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
 
LVL 2

Expert Comment

by:cemal_ozun
ID: 22809541
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
 

Author Comment

by:freeteck
ID: 22809556
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
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
LVL 2

Expert Comment

by:cemal_ozun
ID: 22809590
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
 
LVL 5

Expert Comment

by:lecaf
ID: 22809595
is the firewall off ?

m   a   r   c
0
 
LVL 2

Expert Comment

by:cemal_ozun
ID: 22809596
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
 

Author Comment

by:freeteck
ID: 22809615
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
 
LVL 5

Expert Comment

by:lecaf
ID: 22809639
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
 
LVL 2

Expert Comment

by:cemal_ozun
ID: 22809650
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
 

Author Comment

by:freeteck
ID: 22809691
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
 
LVL 39

Expert Comment

by:ChiefIT
ID: 22810179
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
 

Accepted Solution

by:
freeteck earned 0 total points
ID: 23118946
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

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so. This will be demonstrated using Adobe Premiere Pro CS6.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…

885 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question