Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Black screen when connecting to win2k server machine

Post Reply
eomer

Black screen when connecting to win2k server machine

Post by eomer »

Hi all,

I am trying to connect to a win2k server sp4 machine with VNC, using a local user.

Connection seems ok, but when I connect while there is no user logged on the machine, I get a black screen...

If I connect with the local user, being connected on the machine with my regular user, everything works fine...

Any clue on what I have done wrong? (I am using v1.0.0 RC11 viewer on my xp desktop, and RC17 on the win2k server machine)

Thank's in advance,

Nicolas
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6838
Joined: 2004-04-23 10:21
Contact:

Post by Rudi De Vos »

Could be that is has to do something with
[topic=58][/topic]

Is it a Terminal server ?
eomer

don't think so

Post by eomer »

No I don't think it is the source of the problem, both default and user settings are aligned.

Actually when I use password auth en both user and default settings, it works fine, having someone logged on the server or not. I only have that black screen using the mslogon mode. But I can for example use the file transfer ... :shock:
RobH
Former moderator
Former moderator
Posts: 113
Joined: 2004-05-03 18:04
Location: Chicago, IL

Post by RobH »

Could the different version of viewer and server cause this?
UltraSam
Admin & Developer
Admin & Developer
Posts: 462
Joined: 2004-04-26 20:55
Contact:

Post by UltraSam »

This problem is typically caused by a Terminal/Remote Desktop server running on the same machine than Ultra WinVNC.
Users have to make a choice on the server:
- Remote Desktop access
OR
- UltraVNC access
UltraSam
prandal
20
20
Posts: 36
Joined: 2004-06-08 15:24

Post by prandal »

I've seen that once on a Win 2003 server and I can't for the life of me remember what I did which solved it. I haven't seen it happen at all with the Test 18 WinVNC, mirror drivers, and latest viewer, even with RDP enabled on the server.

Phil
eomer

Correct!

Post by eomer »

UltraSam wrote:This problem is typically caused by a Terminal/Remote Desktop server running on the same machine than Ultra WinVNC.
Users have to make a choice on the server:
- Remote Desktop access
OR
- UltraVNC access
Can be the cause! I do have a remote admin server running on that machine as well...

I'll do some tests and come back!
Post Reply