On 7/8/10 6:56 AM, Adam Tkac wrote: > Sorry for late response, I was away. > > Ah, so you are not connecting to winvnc4 but to Windows RDP server? > Then, from my point of view, we might consider this as intended > feature because I can hardly imagine how winvnc4 and RDP server can > run simulateously on one desktop.
Whenever a user connects to the workstation via RDP, Windows creates a fully virtualized desktop and switches all graphics output to it. Whenever a user logs in locally, the graphics output is switched back to the local desktop and the RDP session is killed. Whenever this transition occurs, it essentially pulls the rug out from under WinVNC, so it doesn't surprise me that it dies (and I seem to remember that same behavior with TightVNC and RealVNC as well.) It might be possible to make WinVNC multi-desktop-aware to prevent this, but I have no idea how much effort that would involve or whether it's really worth it. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
