Hi
I have enabled MSlogonV1 (Utra VNC 1.0.4 installed as a service) on several computers (around 300). I was able to connect on each computers.
After few days and on some computers (not all) (windows 2008 server R2 and XP), it's not possible to connect anymore with this authentication scheme.
The only way is to restart the service.
See the mslogon.log during the issue :
6/3/2013 14:03 Connection received from 127.0.0.1 using secretaccount account
6/3/2013 14:03 Connection received from 127.0.0.1 using secretaccount account
7/3/2013 10:41 Connection received from 127.0.0.1 using secretaccount account
Credentials are accepted (can be seen in the connection status window) but the server disconnect the connection (connection closed due to communication error)
This issue seems to be the same as the following link : http://forum.ultravnc.info/viewtopic.ph ... 3895950c75
Do you have any idea ?
Thanks for your assistance.
Regards
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
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- 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
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- 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
not possible to connect after a while
- Rudi De Vos
- Admin & Developer
- Posts: 6867
- Joined: 2004-04-23 10:21
- Contact:
Re: not possible to connect after a while
1.0.4 is an old version.
Could you try if the latest version (1.1.8.3) also has this issue.
For fast test,
rename old server winvnc.exe
copy winvnc.exe
And use the new vncviewer.exe on the other pc.
Could you try if the latest version (1.1.8.3) also has this issue.
For fast test,
rename old server winvnc.exe
copy winvnc.exe
And use the new vncviewer.exe on the other pc.
Re: not possible to connect after a while
Thanks for your answer.
Unfortunately, I'm not able to reproduce this issue by myself and the problem is solved if I restart the service.
I have launched the viewer with the debug log enable. it gives me the following output.
Started and Winsock (v 2) initialised
bufsize expanded to 4352
Registered connection with app
Clipboard changed
Don't send initial clipboard!
Connected to X.X.X.X port 5920
RFB server supports protocol version 3.4
Connected to RFB server, using protocol version 3.4
Command line MS-Logon.
MS-Logon (DH) authentication succeeded.
rdr::Exception (2): rdr::EndOfStream: read
Have your already seen this message ?
rdr::Exception (2): rdr::EndOfStream: read
Unfortunately, I'm not able to reproduce this issue by myself and the problem is solved if I restart the service.
I have launched the viewer with the debug log enable. it gives me the following output.
Started and Winsock (v 2) initialised
bufsize expanded to 4352
Registered connection with app
Clipboard changed
Don't send initial clipboard!
Connected to X.X.X.X port 5920
RFB server supports protocol version 3.4
Connected to RFB server, using protocol version 3.4
Command line MS-Logon.
MS-Logon (DH) authentication succeeded.
rdr::Exception (2): rdr::EndOfStream: read
Have your already seen this message ?
rdr::Exception (2): rdr::EndOfStream: read