<div>
O.K. Next Question:<br />
<br />
I still can't get to the remote server (It happens to be in the same domain). I get the same message.<br />
<br />
I figure it might be local GPO settings. Do you happen to know what GPO settings might cause this problem?<br />
<br />
Thanks
</div>


O.K. Next Question:

I still can't get to the remote server (It happens to be in the same domain). I get the same message.

I figure it might be local GPO settings. Do you happen to know what GPO settings might cause this problem?

Thanks

<div>
How do I give you more points for this?
</div>


<div>
<div class="content wysiwyg-content">
ALL Windows Server OSs have free Terminal Services license for admin purposes (2? 4?).<br />
<br />
In order to use these licenses i.e. logged in as admininstrator and using Remote Desktop, does one have to set up terminal server license services on all machines and at least one terminal services server to manage these &quot;free&quot; accounts?<br />
<br />
Thanks
</div>
</div>


ALL Windows Server OSs have free Terminal Services license for admin purposes (2? 4?).

In order to use these licenses i.e. logged in as admininstrator and using Remote Desktop, does one have to set up terminal server license services on all machines and at least one terminal services server to manage these "free" accounts?

Thanks

Windows 2003 Terminal Services

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).