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
Blank screen after WOL
Blank screen after WOL
I'm using a dell optiplex 380 and once the computer goes into standby I'm having issues connecting to it via UltraVNC. I use ether-wake to wake the computer up from standby and it works just fine. Problem is when I try and connect to the machine it prompts me for a password and once it authenticates it just shows a blank screen. Looks like the display is not being woke up from standby but the computer is. This issue should have been solved a long time ago. I know it works using RDP and I've changed and tested every bios setting there is (S1, S3, etc) and nothing seems to wake up the display once it goes into standby. Anyone know of a fix other than the obvious of using RDP?