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
After more 2 000 000 (two million) views on forum for 1.5.0.x development versions... and 1.6.1.0, 1.6.3.0-dev versions
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
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
A new stable version, UltraVNC 1.6.4.0 and UltraVNC SC 1.6.4.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38095
Feedback is always welcome
2025-12-05: Celebrating the 23th anniversary of the UltraVNC (26th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38130
2025-12-03: Could you please complete our poll/survey? Renaming UltraVNC files and service to be more clear: https://forum.uvnc.com/viewtopic.php?t=38128
There was a problem to vote, it is solved now! Thanks in advance!
2025-12-02: We need help: English Wikipedia UltraVNC page has been requested to deletion: https://forum.uvnc.com/viewtopic.php?t=38127
Any help is welcome to improve the UltraVNC page and/or to comment on the Wikipedia Talk page
2025-05-06: Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
2023-09-21: Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Development: UltraVNC development is always here... Any help is welcome
Feedback is welcome
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: 6978
- 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.
UltraVNC links (join us on social networks):
- Website: https://uvnc.com/
- Forum: https://forum.uvnc.com/
- GitHub sourcecode: https://github.com/ultravnc/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
- uvnc2me: https://uvnc2me.com/
- Website: https://uvnc.com/
- Forum: https://forum.uvnc.com/
- GitHub sourcecode: https://github.com/ultravnc/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
- uvnc2me: https://uvnc2me.com/
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