Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Bug in MSRC4Plugin_NoReg.dsm ?

Should you have problems with the DSM plugin, here's the place to look for help or report issues
Post Reply
buzz
Posts: 1
Joined: 2007-05-25 21:58

Bug in MSRC4Plugin_NoReg.dsm ?

Post by buzz »

Hi!
I do have NO problem in using the MSRC4Plugin_NoReg.dsm. But VNC seems to have a problem. When i enabled the server to use the plugin everything works fine. But when a viewer connects to this server NOT using the plugin, VNC hangs showing the message "negotiate protocol version". After that point NO other client is able to connect to the server, doesnt matter if he is using the plugin or not. When i try to stop the service, it fails. Service status is "stop_pending". I do have to kill the process winvnc.exe. When i then start the service again everything is fine. I can connect to the server using the plugin. BUT if i now connect to the server using NO plugin, the story starts at the beginning. I have to terminate winvnc HARD .....

Any solutions or ideas?

Edit: Sorry, its the other way. VNC Server has NO plugin enabled and when i try to connect to the server with a client which has the plugin enabled, the server hangs in the way i mentioned. Sorry, its late :-)

Edit2: This one is solved. Found same behavior in the bugs section of VNC so i have to wait until maybe 1.03 :-D
Last edited by buzz on 2007-05-26 08:23, edited 2 times in total.
jazzaddict
Posts: 4
Joined: 2005-12-29 09:18

Re: Bug in MSRC4Plugin_NoReg.dsm ?

Post by jazzaddict »

hi buzz!

I've exactly the same problem that you've described. could you point us some links, or do you mean that this bug is fixed with 1.0.3 beta? Thank you
Post Reply