<div>
When you stop by PID you may have stopped more than on services. &nbsp;See the How to restart Terminal services: <a href="http://www.windows-commandline.com/start-terminal-services-command-line/" rel="ugc">http://www.windows-commandline.com/start-terminal-services-command-line/</a>
</div>


When you stop by PID you may have stopped more than on services.  See the How to restart Terminal services: http://www.windows-commandline.com/start-terminal-services-command-line/ [http://www.windows-commandline.com/start-terminal-services-command-line/]

<div>
<div class="content wysiwyg-content">
After stopping and restarting terminal services I can no longer access it remotely or remote desktoping itself. &nbsp;To stop terminal I found the pid and ended the process in task manger. To start I went to services.msc.<br />
<br />
The server hasn't been restarted in 60 days because apprently last time it didn't come back on.<br />
<br />
Any information much appreciated
</div>
</div>


After stopping and restarting terminal services I can no longer access it remotely or remote desktoping itself.  To stop terminal I found the pid and ended the process in task manger. To start I went to services.msc.

The server hasn't been restarted in 60 days because apprently last time it didn't come back on.

Any information much appreciated

Terminal services server 2003

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).