After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome

Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031

Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078

Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
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

[solved] Establishing a connection to Windows 2000 slow

Post Reply
JoeyDE
Posts: 2
Joined: 2009-11-04 15:06

[solved] Establishing a connection to Windows 2000 slow

Post by JoeyDE »

Hi,

since upgrading to 1.0.8.0 the time between "password requested" and "password accepted" when establishing a connection takes up to 30 seconds. We used 1.0.1 before and never experienced this behavior.

When connecting to a Windows XP machine the VNC session is up and running in less than 5 seconds.

Mirror driver is installed and DSM Plugin is not used.

Any ideas what might cause this?
Last edited by JoeyDE on 2009-11-11 19:55, edited 2 times in total.
JoeyDE
Posts: 2
Joined: 2009-11-04 15:06

Re: Establishing a connection to Windows 2000 slow

Post by JoeyDE »

I forgot to mention the we use MS Logon.

Problem solved:

NewMSLogon in ultravnc.ini must be set to 1
Post Reply