-----Original Message-----
From:
plug-discuss-admin@lists.plug.phoenix.az.us
[
mailto:plug-discuss-admin@lists.plug.phoenix.az.us] On Behalf Of Charlie
Bullen
Sent: Monday, December 20, 2004 10:44 AM
To:
plug-discuss@lists.plug.phoenix.az.us
Subject: Question with practical and ethical considerations.
Happy Holidays,
I do most on my day to day work on a laptop running Redhat 9.0. This
laptop came with Windows XP pro preinstalled. It now dual boots, as from
time to time I have to do some things on a windows system. The most
important is to connect to a windows 2000 server via terminal services.
Inherent within XP pro is a terminal server cal. I would prefer to use
rdestop to connect to the win 2k server, allowing me to connect from
linux and minimizing my need to boot to windows, but in order to do this
I would need to have a terminal server cal on the win 2k server. Cost
considerations prohibit this. All other boxes connecting to the win 2k
server are either XP pro or Windows 2000 pro so the owner of the win 2k
server has not had to buy a 5 pack of terminal server cals.
Given that I own a valid XP pro license, installed on the same box that
I run Redhat on, is there a practical method of having rdesktop announce
itself as either windows 2k pro or XP pro to the server.
If there is a practical way to do this, where does it stand legally and
ethically.
I have also considered putting VMware on my laptop and running XP within
VMware, but this also presents a cost I would rather not incur. Cost
considerations aside, would I then be able to connect to the win 2k
server running XP pro within VMware using it's inherent terminal
services cal?
Any other suggestions to allow a terminl services connection from within
linux?
Regards,
Charlie
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
+++++++++++++++++++++++++++++++
If memory serves, Windows 2000 server allowed NT 4.0 and Windows 2000 Pro to
connect via terminal services without additional licensing. However, Windows
XP pro was not granted this license and neither was any non-MS operating
system.
If you are doing admin work on the Windows 2000 server, I recommend the free
LogMeIn product (
www.logmein.com). There are many things done
administratively that should not be attempted in a terminal services
session. Two such activities are 1) installing or adding a service pack to
MS-SQL 2000, 2) administering Symantec Anti-virus Corporate Edition using
Symantec's MMC.
Thanks,
Bill Wesson
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)