> Other serious limitations of Terminal services include: > *) The server only works on NT,2k and XP nothing else not even 98. > > *) Licenses. The client must be using the same version of Windows as > the machine you are connecting to, if not it'll work for 90 days > then crash until you cough up the price of a new copy of windows. > > *) It uses NT logons directly without any extra authentication; > if you have one bad password on your machine it's toast because > Microsoft don't treat 'local root' exploits as a security issue.
...do a google newsgroup search on "teminal services mitm". Just like VNC - run it over a VPN or tunnel it through SSH. > If you're interested in the encoding that terminal services uses there's > an open source client called 'rdesktop'. But I think the only 'encoding' > advantage that terminal services has is that it saves offscreen pixmaps > at the client end; including font glyphs. See the T.128 spec for the encoding. > One thing that can improve the visible performance with VNC on windows > is using a Windows 2k/XP driver that slides in between the GDI and the > physical display driver. This improves the responsiveness and accuracy > of VNC's detection of changes on the screen. The 'UltraVNC' varient > does this. > > In general, before VNC came along terminal services was a niche product > that cost a bomb and sort of worked over a LAN. Now with pressure from > Citrix at the multi-user level and VNC at the single user it's getting > to be a useable feature. Though it still costs a bomb for multi-user > or mixed machines. VNC and Terminal Services aren't the only solutions. There are still Laplink and kin which work on Win 9x as well. Orin. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
