Re: [SLE] Microsoft Terminal Server access from SuSE 9.3

From: John Scott (praiserock_at_gmail.com)
Date: 08/30/05

  • Next message: Sid Boyce: "Re: [SLE] USB audio questions" 
    Date: Tue, 30 Aug 2005 10:21:47 -0400
To: Audrius <audver@gmail.com>

    On 8/30/05, Audrius <audver@gmail.com> wrote:
    > On 8/30/05, Stephen Carter <stephen@retnet.co.uk> wrote:
    > >
    > > >>> Audrius <audver@gmail.com> 08/30/05 11:52 AM >>>
    > > >On 8/30/05, IntegraGen <suse-ml@integragen.com> wrote:
    > > >I was sure that my server comes with 5 clients... It is OEM server with 5
    > > >clients... But maybe it is "client license" not "RDP client license"? How
    > > >can I now that? Where I can find in MS Server 2003 what type of licences
    > > do
    > > >I have?
    > > >Sorry for questions about MS products... I have SuSE SLES and SLOX
    > > servers -
    > > >with them I do not have such troubles...
    > > >
    > > >Audrius
    > >
    > > I thought OEM should be fine, although if it wasn't a volume license
    > > version that was installed, the server will need to be activated with
    > > Microsoft.
    > > A pop-up with a key icon in the system tray would have warned you of this
    > > condition every time you logged into it. You can confirm if this is the
    > > problem by logging on locally and checking the event logs for license
    > > errors.
    > >
    > > For Terminal Services, by default Windows 2003 server comes with 2 Remote
    > > Administration licenses built-in, which allows 2 concurrent licenses for
    > > remote connections, as the name suggests, for administration purposes.
    > >
    > > If after connecting to the box you clicked the x to close down the session
    > > instead of logging off, it may be that the connection is still in a
    > > 'disconnected' state which you should be able to see by running the Terminal
    > > Services Manager when logging onto the box locally, and from there you can
    > > clear the 'dead' connections.
    > >
    > > Your password may also have simply expired? Trying to log on would tell
    > > you this though, and you would have received warnings, by default, within 14
    > > days of your password expiring.
    >
    >
    > Just my friend came to visit me and with his laptop with Windows XP I
    > connected with RDC to my server with my name and passw without trouble...?
    > Why...? What the hell...! No complains about expiration or other things...
    >
    > Audrius

    As has been said, you need CALs for the Terminal Server (TSCAL), these
    are seperate/different than the CALs used to access the Windows 2003
    server. Man what a racket, a license to access Windows as a fat
    client and a license to access it as a term client. The exception, if
    you have the Terminal Server setup as remote admin access, then you
    get 2 TSCALs for access, for remote admin only of course.

    As for your friend's XP box, there are certain versions of XP that can
    access Windows 2003 Terminal Server without need for the TSCAL.
    Microsoft grandfathered them in as having the TSCAL already because
    they shipped before Windows 2003. Newer versions of XP are suppossed
    to require the TSCAL.

    As for the timeout, check out the settings on the Windows 2003 box.
    It's kicking you out probably due to what it sees as an inactive
    session or expired logon.

    BTW, this app, are you the only one who needs to use it? If so, then
    look at Win4Lin, VMware, or wine and see if you can do away with the
    Term Server and CALs issue.

    John 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Sid Boyce: "Re: [SLE] USB audio questions"

    Relevant Pages

    • Re: How to add a user with very limited rights
      ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
      (microsoft.public.windows.server.sbs)
    • RE: RWW problem on one Client machine
      ... Welcome to SBS newsgroup. ... services licensing service on a Windows 2000 domain controller. ... terminal license successfully. ... messages in the event log saying that "A terminal license server cannot be ...
      (microsoft.public.windows.server.sbs)
    • Re: Anonymous connections.
      ... Windows Server 2003 Licensing Server can control ... you may use the New External Connector License option. ... Microsoft Partner Support ...
      (microsoft.public.windows.terminal_services)
    • Re: Connecting to SQL Without Windows Authentication
      ... This is why the "license group" concept was introduced - to account ... Also note that you not only need SQL CALs but also Windows CALs in case the ... > Domain and our Windows 2000 server in another domain. ...
      (microsoft.public.sqlserver.security)
    • RE: RWW problem on one Client machine
      ... I think we are looking for something on his client. ... > services licensing service on a Windows 2000 domain controller. ... > terminal license successfully. ... > messages in the event log saying that "A terminal license server cannot be ...
      (microsoft.public.windows.server.sbs)