Brian M. Godfrey wrote:
> Hi Scott,
> I tried it and yes, VNC does work if I have not used remote desktop since
> a reboot. And my application does run OK on VNC. So I'd be interested to
> learn the strange workaround.
> Thanks!
>
> --Brian M. Godfrey
> [EMAIL PROTECTED]
>
OK, here it it, but it ain't pretty... Good luck.
Step 1
First, you need to RDP into the box (or log on to the actual console
locally).
Then, bring up a DOS command prompt, and enter:
qwinsta
This will present a list of "sessions" and their status. If you plan to
use VNC to log onto the console with a User account other than any users
listed under the USERNAME column, then you may skip to Step 3. If the
corresponding ID column for the required USERNAME is 0 (zero), then you
may also skip to Step 3.
Step 2
You will need to log off the required User account from their existing
Session. Based on the output of the "qwinsta" command, locate the value
for the ID column in the corresponding row of the required USERNAME.
Execute the command:
rwinsta /<ID value>/
/<ID value>/ refers to the value of the ID column for the appropriate
USERNAME. For example:
rwinsta 3
*NOTE*: Executing this command will log off (not disconnect) the
specified User.
Step 3
You will need to reconnect Session 0 (zero) to the console device by
entering the command:
tscon 0 /dest:console
*NOTE*: Based on the output of the |"qwinsta"| command, if there is a
row with a STATE of "Active", then executing this command may disconnect
(not log off) that user. This is because XP only allows one active
session at a time.
You should now be able to use VNC to control the console.
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
