On 8/30/05, Audrius wrote:

On 8/30/05, Stephen Carter wrote:

...

...

...

...

Audrius 08/30/05 11:52 AM >>> On 8/30/05, IntegraGen 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

On 8/31/05, Audrius wrote:

On 8/30/05, John Scott wrote:

...

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.

Well, I was thinking about that too, but today I bring my NB with SuSE 9.3on it to work and with rdesktop I can connect to server with my name and passw...!!! I don't get it...? How the hell W2003 server are managing CAL licences? Where I can find what is wrong to connect from my PC...?

Microsoft Terminal Server will issue a temporary license to a client when it first connects (any OS), and several weeks later (I think its 90 days, can't remember right now) that temporary license will expire and that client will no longer be able to connect until licenses are purchased and applied to the system. You can't really remove an expired client license, but you can stop the service, delete the registry key and the db file that holds all the info, and reboot the server (at least under W2k Term Server) and get a new clean slate for clients. I've had to do this a cople of times on my Citrix/W2K Term Server due to corrupt db and/or registry key. However, use at own risk statement as it isn't officially supported by either Citrix or MS even though they reference in their respective KBs.

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.

Where I can find that info?

There's a MMC snap-in called Terminal Services Configuration, or something like that, that you can use. You should bring up the RDP-Tcp properties and click on the session tab and set the limits. You should also use the Local Security Policy snap-in to check the policy that defines idle limits also. If this server is in an AD or other directory infrastructure, you might have a policy that defines idle timeouts for the server and user accounts. If that's the case you'll have to get with the admin, if it isn't you, to persuade them to change this.

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.

Yep. I will try VMware. I have Codeweavers CorssOver Office but my app do not work there. Main problem is that my PC is not so new, PIII 700 with 512MB SDRAM. I care how VMware will perform...?

You should be ok with your specs to run vmware, if all you run is a single vm. Your box is better than the minimum requirements.

Thank you all for kind answers!!!

Audrius

Your welcome. John Scott