C:\>tscon 0 /dest:console Could not connect sessionID 0 to sessionname console, Error code 7045 Error [7045]:The requested session access is denied.
C:\> -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 25, 2006 5:33 PM To: Peter White Cc: Rob Hoerning; echovnc-users@lists.sourceforge.net Subject: Re: [Echovnc-users] Black blank screen - Peter: Heya. My understanding of the RDP/TermServ "black-screen" problem is that...it's supposed to be that way. That is, when you RDP into a Windows server, something called "console 0" gets "taken away" from the user session. When you then connect with VNC, it can't attach to "console 0" anymore, and you see the black screen. The workaround is to disconnect your RDP session in an unusual way, using the "tscon" command: tscon 0 /dest:console This, as I understand it, forces your "user session" to re-connect to "console 0" -- causing the RDP session to disconnect -- but enabling VNC to attach to it again. More info on "tscon" is here: http://www.robvanderwoude.com/termserv.html#TsCon A VNC thread about this issue is here: http://www.realvnc.com/pipermail/vnc-list/2005-June/051483.html I hope that helps! -Scott On Wed, 25 Oct 2006, Peter White wrote: > Thanks for that part, Rob. > > > > My big problems is this. If I have a windows RDP connection open on > the server my EchoVNC session is fine. If I "x" okut of my RDP session > my EchoVNC window turns black. I need to work with EchoVNC without an > RDP session open. If I log out of my RDP session my EchoVNC will not > connect at all. > > > > Thanks > > Peter White > > > ________________________________ > > From: Rob Hoerning [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 25, 2006 4:01 PM > To: Peter White > Subject: RE: [Echovnc-users] Black blank screen - > > > > just use the echo enabled Ultra with your own echoserver and it's all > good. Been using it for weeks and it's flawless. > > > > ________________________________ > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter > White > Sent: Wednesday, October 25, 2006 2:42 PM > To: echovnc-users@lists.sourceforge.net > Subject: [Echovnc-users] Black blank screen - > > Hi, > > > > I am making some progress, but have a new problem. > > > > We want to use EchoServer to replace some of the ras connections we use > to support customers. > > > > I found a customer willing to test this with us and I ras'd in and used > a windows RDP connection to set up her EchoClient with your Echo-aware > UltraVNC Server and Viewer. The site uses Echo client to connect to > the EchoServer. (I'll test the UltraVNC built-in echo connection later). > > > I can make an Echo connection from my PC to their server fine as long as > I keep the RDP (remote desktop connection) open. If I close the RDP > session I can still connect my PC to the server with Echo, but I just > get a blank black screen. > > > > What can I try to change that so I get a full VNC screen even with the > RDP session closed? > > > > Thanks > > > > Pete White > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Echovnc-users mailing list Echovnc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/echovnc-users
