It has at least 2 valuable uses on Windows systems running terminal services.
(1) It provides a redundant connection method with different underlying dependencies. (2) You are ensured that you will connect directly to the console whenever you use it. ----- Original Message ----- From: "Beerse, Corni" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, 2002-03-13 04:06 Subject: RE: Problems with WinXP and Terminal Services : > -----Original Message----- : > I'm having a problem with vnc and Windows XP. I know : > it's not supported yet, but VNC actually works pretty : > well unless you logged into the machine via Terminal : > Services (remote desktop) last. In this case a blank : > screen is displayed when vnc makes a connection. It : > would be cool if, at the very least, it came up with a : > login screen. Are there any plans to support this : > scenario? : : : What's the use of using vnc in a terminal server configuration? As far as I : know it's just using an other protocol to get the windows on the desktop. : : If it's for displaying on unix, the terminalserver has an X11 option to get : a X11 display. : If it's for takeover, put the vncserver in userspace and off you go. : If it's for security, What security? : If it's for something else, explain your usage. : : : CBee : --------------------------------------------------------------------- : To unsubscribe, mail [EMAIL PROTECTED] with the line: : 'unsubscribe vnc-list' in the message BODY : See also: http://www.uk.research.att.com/vnc/intouch.html : --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
