Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
SC to work with DSM Plugin
SC to work with DSM Plugin
I already stated here, that I got SC working with plugin v1.1.4...
Now I just forced to eat my own words...
The thing is that other machine, where SC executable was launched, had VNC installed at one time and obviously had some traces of it in system.
Now I tried to get the same executable to work in other machine, where has never been any traces of VNC, then... the old problem was back - when launching SC executable, error message "cannot find rc4.key file-blablabla" was displayed and on viewer side this "Connection failed" text popped up...
I'm understanding what to do when using full VNC server and got most of plugin problems solved, but with SC there's not much to do on server side...
The thing, that SC worked on the machine once had VNC installed is suggesting, that there is something about registry or directories/locations even with SC if plugin is used...
Almost back to square one...
Now I just forced to eat my own words...
The thing is that other machine, where SC executable was launched, had VNC installed at one time and obviously had some traces of it in system.
Now I tried to get the same executable to work in other machine, where has never been any traces of VNC, then... the old problem was back - when launching SC executable, error message "cannot find rc4.key file-blablabla" was displayed and on viewer side this "Connection failed" text popped up...
I'm understanding what to do when using full VNC server and got most of plugin problems solved, but with SC there's not much to do on server side...
The thing, that SC worked on the machine once had VNC installed is suggesting, that there is something about registry or directories/locations even with SC if plugin is used...
Almost back to square one...
Last edited by tim71 on 2005-02-18 21:55, edited 2 times in total.
try dsmplugin 1.1.5 some bugs are fixed ! (can be used as guest level security !
more detail_
http://home.comcast.net/~msrc4plugin/ms ... noreg.html
more detail_
Trouble-shooting
http://home.comcast.net/~msrc4plugin/ms ... noreg.html
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Now it finally seems to be resolved - it was the wrong plugin in generating script. This caused the wrong plugin to be included in executable. Tested with computer with no traces of VNC on it.
Is 1.1.5 backwards compatible?
Is 1.1.5 backwards compatible?
Last edited by tim71 on 2005-02-19 12:15, edited 1 time in total.
MSRC4 plugin 1.1.5 is backward compatible only with UltraVNC RC19.5 or higher !
MSRC4 Plugin Release Notes
MSRC4 Plugin Release Notes
Last edited by redge on 2005-02-19 12:18, edited 1 time in total.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Did you manually compile your exe or did you do it from the website? I have read the threads on how to do it myself, but was wondering if the website is including the right plugin now?tim71 wrote:Now it finally seems to be resolved - it was the wrong plugin in generating script. This caused the wrong plugin to be included in executable. Tested with computer with no traces of VNC on it.
Is 1.1.5 backwards compatible?
All executables with plugin were made by myself. I don't know, what online script does at the moment...
But you can find it out simply - generate the executable online and then extract it with 7-zip and find out yourself
Just too tired at the moment for this - four long nights at remote assistance (and solving this plugin problem almost on same time) now that SC is discovered is just a bit too much considering that my fulltime job is elsewhere...
But now thing works like charm with the plugin - except for File Transfer (crashes always).
But you can find it out simply - generate the executable online and then extract it with 7-zip and find out yourself
Just too tired at the moment for this - four long nights at remote assistance (and solving this plugin problem almost on same time) now that SC is discovered is just a bit too much considering that my fulltime job is elsewhere...
But now thing works like charm with the plugin - except for File Transfer (crashes always).
Understood on the job thing... we all got bills.. and without them we wouldnt have jobs, and vise-versa.
I will try to unpack the exe and see whats in it, and put in what I need / want for the new plugin. Thats probably all i need to do
thx for the info.
And I think they are working on FT for multiple files, single files should work??? (Yes this is a question more than an answer)
I will try to unpack the exe and see whats in it, and put in what I need / want for the new plugin. Thats probably all i need to do
thx for the info.
And I think they are working on FT for multiple files, single files should work??? (Yes this is a question more than an answer)
folder driverRC19 and SC include dsmplugin 1.1.0
source:
http://doc.uvnc.net/singleclick.html
If you don't have the plugin on your system, the plugin can be downloaded from http://ftp.erm.tu-cottbus.de/ultravnc/D ... Plugin.dsm
source:
http://doc.uvnc.net/singleclick.html
Last edited by redge on 2005-02-20 16:42, edited 1 time in total.
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Current SC is pre RC195.
The plugin included was a special compilation. I removed all registry rederences in the plugin and replaced it by fix name
and winvnc runpath.
Use viewer RC193 or RC194.
As plugin you can use the same plugin as for RC18 or just extract the plugin (using 7zip) out of the SC exe.
The plugin included was a special compilation. I removed all registry rederences in the plugin and replaced it by fix name
and winvnc runpath.
Use viewer RC193 or RC194.
As plugin you can use the same plugin as for RC18 or just extract the plugin (using 7zip) out of the SC exe.
Hi all,
I can't seem to get mine to work. I always get the "Connection Failed - Invalid Protocol" error. I'm running RC19.5 release and used multiple dsmplugins with no luck. I've tried 112MSRC4Plugin_noreg.dsm and msrc4plugin_noreg.dsm (1.1.5) so far.
helpdesk.txt
[HOST]
Internet support encryption
-plugin -connect 165.xxx.xx.xxx:5500 -noregistry
Viewer Setting:
check USE dsmplugin box and selected the matching dsm
generated my own rc4.key and it's on both ends. Any suggestions? Any ideas?
Thanks.
I can't seem to get mine to work. I always get the "Connection Failed - Invalid Protocol" error. I'm running RC19.5 release and used multiple dsmplugins with no luck. I've tried 112MSRC4Plugin_noreg.dsm and msrc4plugin_noreg.dsm (1.1.5) so far.
helpdesk.txt
[HOST]
Internet support encryption
-plugin -connect 165.xxx.xx.xxx:5500 -noregistry
Viewer Setting:
check USE dsmplugin box and selected the matching dsm
generated my own rc4.key and it's on both ends. Any suggestions? Any ideas?
Thanks.
Last edited by sklim1 on 2005-03-03 02:05, edited 2 times in total.
Yes. I also uncompress the executable to verify. This is all done through Creator. I don't have a exe compiler locally to play with which I think would be more ideal. I wonder if the the Creator is somehow using a different MSRC4plugin which is causing the invalid protocol error.
Anyone know which verison of the plugin is being used?
Anyone know which verison of the plugin is being used?
Last edited by sklim1 on 2005-03-04 00:58, edited 2 times in total.
for testing purposes
for testing purposes, if you can set and enviroment variable before SC runs, the plugin should generate a log for you.
set dsmdebug=1
It should create rc4.log in the same directory as the plugin. The enviroment variable should work on plugin versions 112 and up of the NoReg plugin.
Sean
set dsmdebug=1
It should create rc4.log in the same directory as the plugin. The enviroment variable should work on plugin versions 112 and up of the NoReg plugin.
Sean