Telnet support - server pc's command prompt?

[akaidiot]

On all my VNC server PCs I always have, other then UVNC, remote administrator installed, as a backup vnc, and it does the job, but worse then UVNC..

Although it has a feature that I think UVNC doesn't have. It can telnet to the server. So when I telnet to the server I get basically the servers command prompt, and can then start up services etc.(like winvnc.exe)..

You can do this by just vncing and starting the command prompt, but that makes the computer un-usable locally and also the telnet is much faster then the graphical command prompt, especially on a slow network(non-broadband internet connection for example..).

[rmoller]

have you considered psexec from the pstools at www.sysinternals.com? That's what I use (provided you can access the server with local admin credentials).

[msheets]

I would also like to see a feature integrated into UltraVNC that is similar in functionality to psexec as used with the "-i" switch (e.g. psexec \\ComputerName -i Command.exe /args).

As an example scenario, take a case where Group Policy is used to lock down a typical end-users access, preventing them from directly accessing things such as My Computer (or other file system browsing), all drives, the command prompt, Run, Internet Explorer, System Tools, Control Panel, etc. However, sometimes when an administrative or support person is working on an end-user's system, it is helpful to be able to launch a program on the user's GUI that the end-user normally cannot access (e.g. individual control panels, iexplore, defrag). Ideally, file associations would be enabled (similar to Run), so that if a specific file is requested (e.g. a saved mmc console), then the default program would launch and open the file.

If integrated into UltraVNC, I would not need an additional additional authentication in order to use this feature (such as is required by psexec under certain situations), though some who might not want this functionality would probably like an option to disable such capabilities on the server side.

The "chat" feature already transfers text. This feature would just need to transfer a single line of command text and then run it in the user environment of the remote system. A text box could possibly even be incorporated into the toolbar to provide easy access to this feature.

I think this is different from the other UltraVNC feature requests to mimic the "Remote Command" and/or "Remote Shell" services, which can be installed on Windows systems after the Resource Kit is loaded. Those services do not interact with the end-user's desktop but instead merely provide a DOS interface to a remote system. One of the services is text redirection based, and the other is supposed to permit the use of DOS programs such as "Edit." I have used the command redirection one from time to time, but again, it cannot interact with the end-user's desktop.