On 8/30/05, John Scott
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...? 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? 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...? Thank you all for kind answers!!! Audrius