The other option is to Remote Desktop in to the PC, and at the command
prompt, issue:
TSCON 0 /DEST:console
This will kick you out of your session, and reset it to the console. At
this point, you may now control the console using VNC.
Thanks to "joerg" for this solution. It sure beats rebooting the system...
Alan Watchorn wrote:
>John is right about the incompatibility between Remote Desktop and VNC,
>and VNC not working until you reboot the system after using Remote
>Desktop. If you are working remotely this can be a real pain since Remote
>Desktop does not give you the option of shutting down/restarting the
>machine when you click 'Start' (the only options are 'logoff' and
>'disconnect'). You can get to the 'Shutdown' option (then do a 'Restart')
>by entering CTRL+ALT+END in the Remote Desktop session.
>
>Alan.
>
>Alan Watchorn
>Eshelman Appraisals, Inc.
>[EMAIL PROTECTED]
>Phone (760) 692-4302
>Fax (760) 692-4303
>
>John Aldrich said:
>
>
>>Known issue with RD. VNC (Free Version) cannot connect to a Windows
>>machine
>>until it is rebooted after using Fast User Switching or Remote Desktop.
>>According to Wes with RealVNC, the next freeware version to come out will
>>have that capability, just like the Enterprise version currently does,
>>however, at this point, if you're using the free version, you're out of
>>luck.
>>
>>-----Original Message-----
>>From: Roman Rozinov [mailto:[EMAIL PROTECTED]
>>Sent: Thursday, January 27, 2005 7:28 PM
>>To: vnc-list@realvnc.com
>>Subject: Problem connecting to VNC 4 Service running on Windows 2003
>>server
>>
>>
>>Problem:
>>VNC 4 running in service-mode on Windows 2003 Standard Server.
>>Initially, VNC 4 client/Web client connects to that server successfully
>>and can manipulate the GUI. Then, I've used a tool called Remote
>>Desktops version 5.2.3790.0 and initiated a terminal connection to the
>>2003 server. After closing the terminal connection, any attempts to use
>>VNC 4 client/Web client produces an empty window. Web client produces
>>an empty applet.
>>Note: the server has an error event "HTTPServer, error writing HTTP
>>document:write: Connection aborted (10053)"
>>Looking at the Java Console, it uses Protocol 3.8 and the last entry
>>Cconn: Using ZRLE encoding
>>
>>
>>Anyone else experienced a similar problem?
>>
>>
>>________
>>
>>Roman Rozinov
>>Technology Support Analyst
>>Desktop Systems Technology, Information Technology
>>Arizona State University
>>[EMAIL PROTECTED] <http://www.asu.edu/it/>
>>_______________________________________________
>>VNC-List mailing list
>>VNC-List@realvnc.com
>>To remove yourself from the list visit:
>>http://www.realvnc.com/mailman/listinfo/vnc-list
>>_______________________________________________
>>VNC-List mailing list
>>VNC-List@realvnc.com
>>To remove yourself from the list visit:
>>http://www.realvnc.com/mailman/listinfo/vnc-list
>>
>>
>_______________________________________________
>VNC-List mailing list
>VNC-List@realvnc.com
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
