This is the latest:
The Terminal Server and TS Licensing features have been uninstalled from the upgraded server. RDP access is allowed in the Remote tab. (Check out the comments on the first answer for that detail, if necessary.) Still, RDP access is broken.
I found out that the Terminal Server service in the Services MMC is broken. First, it still contains the Windows 2000 description. Second, it points to the old Win2k Server executable. It obviously doesn't work.
I have a Windows 2000 DC that was running Terminal Services in Application Mode. A couple of weeks back, I ran an in-place upgrade to 2003. The server is now running 2003 R2 Standard.
Since then RDP no longer works. We have no need or desire for this to be a Terminal Server anymore other than Administration Mode.
What I am really trying to accomplish is the following:
Place the upgraded 2003 server into Remote Desktop for Administration.
(Interestingly, the "Licensing" setting within the Terminal Services Configuration MMC is not visible.)
At the moment, Terminal Services is installed on the server, but licensing is not. We were trashing around trying to resolve this and that's the state we've left the server. I've since discovered that for a typical configuration, neither the Terminal Services nor the Licensing features should be installed.
If anyone has any thoughts, they are appreciated.
Also: This is a production server. I can reboot it, but must do so off-hours.
Some new details:
RDP is "broken" in the sense that when any client attempts to initiate a connection to the server, they immediately receive a "This Computer cannot connect to the remote computer" error.
Also: There is no "Remote" tab within the Properties sheet for My Computer.