After connecting with RDC (Remote Desctop Connection) a VNC or alike programs (PCAnywhere) failed to show the desktop screen.
Did any of the software find a work around this issue?
Looking forward to a solution,
Thank you...
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
RDC and VNC...
NEVER use MSTSC /CONSOLE /V:server , that is, never connect RDP to console. You thereby disconnect session 0 from console. Not only you disrupt programs like VNC og PCAnywhere; you also disrupt some backup programs running as service (like our backup program). Note that it is perfectly safe to use Terminal Services / RDP as long as you DON'T connect to console, that is DON'T use /CONSOLE parameter.
All Windows services run in session 0. Check with
QWINSTA /server:servername
how your sessions are - if session 0 shows up on the same line as console, you are OK. If you have been connected to console with RDP, console will be connected to, say, session 3, and session 0 will be disconnected.
There are two ways to resolve this situation:
1: reboot server
2: reset all sessions (which will log them off) with the command
for %a in (4 3 2 1 0) do reset session %a /server:servername <nul
Of course you may have more/less sessions than the above 5. The only advantage of solution 2 is that it avoids downtime.
Good night and good luck
Rasmus Moller
All Windows services run in session 0. Check with
QWINSTA /server:servername
how your sessions are - if session 0 shows up on the same line as console, you are OK. If you have been connected to console with RDP, console will be connected to, say, session 3, and session 0 will be disconnected.
There are two ways to resolve this situation:
1: reboot server
2: reset all sessions (which will log them off) with the command
for %a in (4 3 2 1 0) do reset session %a /server:servername <nul
Of course you may have more/less sessions than the above 5. The only advantage of solution 2 is that it avoids downtime.
Good night and good luck
Rasmus Moller