<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Remote Desktop Connection in StoreEasy Storage</title>
    <link>https://community.hpe.com/t5/storeeasy-storage/remote-desktop-connection/m-p/363089#M322</link>
    <description>I installed a HP 2000s back in Nov. 2003. at around March 2004 I haven't been able to attach to the Remote Desktop Connection using MS Remote Desktop Connection app. I get the error message that there was no Terminal Service license servers available. This is not true because I do have a TS license server that issues licenses for a terminal server users connect to and I have a a second HP NAS 2000s that I installed in Jan 2004 that I can connect to.&lt;BR /&gt;ON the NAS in trouble, if I connect through iLO and try to run Term Server Licensing, it doesn't find my licensing server on the LAN, but from the working NAS, which is in a remote location connected via WAN, it can find the license server.&lt;BR /&gt;Also, on the NAS in trouble, I cannot login (via iLO Remote Desktop) into the remote desktop using a domain account, even though it's a member server.</description>
    <pubDate>Fri, 30 Apr 2004 16:16:19 GMT</pubDate>
    <dc:creator>CA1124132</dc:creator>
    <dc:date>2004-04-30T16:16:19Z</dc:date>
    <item>
      <title>Remote Desktop Connection</title>
      <link>https://community.hpe.com/t5/storeeasy-storage/remote-desktop-connection/m-p/363089#M322</link>
      <description>I installed a HP 2000s back in Nov. 2003. at around March 2004 I haven't been able to attach to the Remote Desktop Connection using MS Remote Desktop Connection app. I get the error message that there was no Terminal Service license servers available. This is not true because I do have a TS license server that issues licenses for a terminal server users connect to and I have a a second HP NAS 2000s that I installed in Jan 2004 that I can connect to.&lt;BR /&gt;ON the NAS in trouble, if I connect through iLO and try to run Term Server Licensing, it doesn't find my licensing server on the LAN, but from the working NAS, which is in a remote location connected via WAN, it can find the license server.&lt;BR /&gt;Also, on the NAS in trouble, I cannot login (via iLO Remote Desktop) into the remote desktop using a domain account, even though it's a member server.</description>
      <pubDate>Fri, 30 Apr 2004 16:16:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeeasy-storage/remote-desktop-connection/m-p/363089#M322</guid>
      <dc:creator>CA1124132</dc:creator>
      <dc:date>2004-04-30T16:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: Remote Desktop Connection</title>
      <link>https://community.hpe.com/t5/storeeasy-storage/remote-desktop-connection/m-p/363090#M323</link>
      <description>Hey Rob,&lt;BR /&gt;&lt;BR /&gt;The 2000s is trying to use the terminal services to do remote desktop.  The licensing for terminal services changed from the previous versions of NAS OSs and now only has a 120 day license.  Which in your case has expired.&lt;BR /&gt;&lt;BR /&gt;resolution:&lt;BR /&gt;Turn off terminal services, turn on remote desktop.&lt;BR /&gt;Is your case, terminal services has turned itself off so all you need to do is turn on remote desktop.&lt;BR /&gt;&lt;BR /&gt;Right-click on "My Computer"&lt;BR /&gt;click Properties&lt;BR /&gt;Click Remote&lt;BR /&gt;Enable Remote Desktop&lt;BR /&gt;(Add any users that are not administrators of the NAS box that will be using Remote Desktop)&lt;BR /&gt;&lt;BR /&gt;Sorry for the inconvienience.&lt;BR /&gt;</description>
      <pubDate>Wed, 05 May 2004 11:06:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeeasy-storage/remote-desktop-connection/m-p/363090#M323</guid>
      <dc:creator>Jon Paul</dc:creator>
      <dc:date>2004-05-05T11:06:15Z</dc:date>
    </item>
  </channel>
</rss>

