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

From: Audrius (audver_at_gmail.com)
Date: 08/30/05

  • Next message: Rikard Johnels: "Re: [SLE] Microsoft Terminal Server access from SuSE 9.3" 
    Date: Tue, 30 Aug 2005 15:00:02 +0300
To: suse-linux-e@suse.com

    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

  • Next message: Rikard Johnels: "Re: [SLE] Microsoft Terminal Server access from SuSE 9.3"

    Relevant Pages

    • Re: logon failure with Windows xp client
      ... it is logging on fine at first. ... that in that logon script i map three drives, and in one of my default domain ... a server or shared resource by the same user, using more than one user name ... disconnec all previous connections to the server or shared ...
      (microsoft.public.win2000.setup_deployment)
    • Re: ADMIN SHOW CONNECTIONS ???
      ... > I am running Advanced Server V7.2A for OpenVMS ... > $ ADMIN SHOW CONNECTIONS ... can view license usage using: ... If you're concerned clients aren't getting connected due to license ...
      (comp.os.vms)
    • Re: Unable to remote connect for some users
      ... allows for unlimited connections from that client. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... it's also Terminal service license server. ... Remote connection are not enabled ... ...
      (microsoft.public.windows.terminal_services)
    • Re: Unable to remote connect for some users
      ... allows for unlimited connections from that client. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... it's also Terminal service license server. ...
      (microsoft.public.windows.terminal_services)
    • Re: Cannot connect more then two clients : Partial Answer found
      ... Is it possible that these clients have connected to another TS ... Is there anything in the EventLog on the Terminal Server? ... connections where set to max 2. ... How to override the license server discovery process ...
      (microsoft.public.windows.terminal_services)