The problem described is only an issue if the session being remoted by VNC is a TS session - this is often the case with the console session when Fast User Switching or Remote Desktop are used under XP.
Under 2K3, running a User-Mode VNC Server process inside a TS session and then disconnecting the TS session is the way to see the problem. VNC Server in Service-Mode will happily remote the console session of 2K3 regardless of whether or not TS is used for other sessions. Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: 08 August 2004 12:54 > To: [EMAIL PROTECTED] > Subject: RE: VNC and RDP 5.0 (Windows 2003) incompatabilities > > I'm following this thread, but I'm missing something. > > I'm operating Windows 2003 standard server (two of them) on > the Intranet and I don't have any problems running an RDP > session and a VNC session at the same time. > > Mind you, I'm operating TS in administration mode on the > server. Maybe the people suffering from the RDP/VNC issues > are running TS in licensed mode? > > At 21:40 03/08/2004, Stewart Castaldi wrote: > >I second this. I first encountered this problem after > upgrading from VNC 3.3.7 to VNC 4.0. Downgrading back to VNC > 3.3.7 did not correct the problem. There is definitely an > interaction between RDP and VNC on Windows 2003 boxes which > render VNC pretty much unusable unless you don't use RDP. > >-- > >Stewart Castaldi Fred Hutchinson Cancer > Research Center > >Email: [EMAIL PROTECTED] 1100 Fairview Ave. N., MS: J4-300 > >Phone: 206-667-6426 P.O. Box 19024 > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
