Same thing happened to me once, with no reason server stopped accepting
Go to the terminal services configuration, delete tcp-rdp listener and then
restart server. After booting go again to the TSconf and create a new rdp
listener, restart server once again and that's it. This happened to me once,
and it helped me.
> I have a number of 2003 Servers. One server returns a message:
> "Remote Desktop Disconnected
> The Client could not connect to the remote computer"
> I have run netstat -a -o on the failing server and found that the RDP-TCP
> port 3389 is not listed as a listening port.
> Terminal Services is started in services
> The server is part of a workgroup and does not receive domain policies.
> The other partners in the same workgroup are aon the same subnet - Remote
> Control works properly on the partners.
> The Server has SP1 installed.
> Remote Desktop is enabled in the Remote tab of System Properties.
> Disabling and then Enabling Remote Desktop does not start teh RDP-TCP
> In Terminal Services Manager I see the Comupter with Console linked to it
> but RPC-TCP Listener is not there. All symbols are green. Disconnecting and
> reconnecting the computer does not restore the RDP-TCP listener.
> The DRP-TCP port is correctly defined in the Registry.
> There are no events in the event log that relate to the RDP-TCP listener or
> Terminal Services.
> As far as I can see all the servers are configured the same.
> The server where Remote Desktop does work is our SQL Server and is not an
> machine to reboot with sever impact to the user community.
> Besides rebooting (which I personally do not consider a fix for anything)
> what else can be done to get the RDP-TCP Listener running again. This machine
> did work properly up until about two or three weeks ago. As far as I can tell
> no one has made any changes to the server at that time. It was last rebooted
> on a weekend 1 1/2 weeks ago.