Hi, i have not used ultravnc in over 1 yr. I just installed RC20.2 on Windows 2003 server remotely via remote desktop. I can't get the password to set. From years ago I remember this being an issue with the orig vnc and tightvnc. I searched the Net for over 1 hour and found nothing on this.
Is this possible? I don't have access to the physical server. Here is what i did:
- I made sure that Ultravnc is started as a service.
- I rebooted the server after install.
- I stopped and started the service several times.
- I tried the realvnc 4.1.1 client in addition to uvnc 20.2 client, it ultravnc keeps complaining that the password is not set
- I made sure the server is listening on port 5900
- I changed the password several times
- I noticed that I don't have a registry entry called
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default\Password
but I do have one called HKEY_CURRENT_USER\Software\ORL\WinVNC3\Password
Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
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
- 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
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
- 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
installing remotely via MS remote desktop - set password??
This is one of the administrators
This is one of the administrators. This is actually the Administrator local account. I'll try to copy the registry entry as suggested and see how that goes, hopefully later on today. I've copied entire trees of registy entries from one pc to another pc before, but i never copied over one specific entry from one part of the registry to another on the same pc before. So I will look into doing that.
Two more pieces of info that I forgot to pass on:
1) There is no AntiVirus software on the server running
2) Windows 20003 Standard on this box is updated with all the latest Critical OS Patches from Microsoft
thanks for your help - Jim
Two more pieces of info that I forgot to pass on:
1) There is no AntiVirus software on the server running
2) Windows 20003 Standard on this box is updated with all the latest Critical OS Patches from Microsoft
thanks for your help - Jim
Jim Stroud
Still no luck - I copied registry entry over
All, I still cannot log in via Ultra VNC since I installed it via remote desktop
I copied the Password value and data from
HKEY_CURRENT_USER\Software\ORL\WinVNC3\
to
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\
I made sure that when I created the Password Value under
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\
that I created a "new binary value" and I carefully entered in the data in this registry value.
I stopped and restarted the UltraVNC service via Windows services and via UltranVNC's tools.
I also rebooted the server and to no avail. When I try to connect to it via the UltraVNC View or RealVNC Viewer I get "
The server does not have a valid password enabled. Until a password is set, incoming connections cannot be accepted".
I copied the Password value and data from
HKEY_CURRENT_USER\Software\ORL\WinVNC3\
to
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\
I made sure that when I created the Password Value under
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\
that I created a "new binary value" and I carefully entered in the data in this registry value.
I stopped and restarted the UltraVNC service via Windows services and via UltranVNC's tools.
I also rebooted the server and to no avail. When I try to connect to it via the UltraVNC View or RealVNC Viewer I get "
The server does not have a valid password enabled. Until a password is set, incoming connections cannot be accepted".
Jim Stroud
Same problem
I have the same problem with getting the service to use the password. I have a Windows 2000SP4 server, to which I have no local access. In order to be able to perform some other stuff (which plain refuse to run via Terminal Services), I tried installing UltraVNC. When connecting, it says I haven't set a password.
I've tried with MSLogon (both new and old), but it still complains about the password.
Copying the HKCU registry password to HKLM does not help (tried restarting the service afterwards, and also removing and re-registering it). Are there any other reg settings that could be of use under HKLM?
I've tried with MSLogon (both new and old), but it still complains about the password.
Copying the HKCU registry password to HKLM does not help (tried restarting the service afterwards, and also removing and re-registering it). Are there any other reg settings that could be of use under HKLM?
I think I've found something to get around the problem. I created the registry value AuthRequired under HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3 and set it to 0 (a DWORD value). That enabled "passwordless" VNC access, which isn't that bad in my case since I limited it to loopback only anyway (and I can keep the VNC service stopped when not needed). Also, MSLogon seems to work when I enabled that in the registry as well.
-
- Posts: 1
- Joined: 2006-08-03 18:49
Re: installing remotely via MS remote desktop - set password
What ended-up working for me, after much hair pulling:
Follow jstack's advice to create a no-auth required by setting AuthRequired dword to 0.
Immediately log in with VNC and start it as a service.
Now since VNC is hooking video as if we were sitting in front of a console rather than RDP's session stuff, we can attach to the newly started vnc service. Go to start->program files->Ultra VNC->Ultra VNC Server [folder]->Show Default Settings (Assuming everything is in the default places/names at least...)
Now set your password. Do a save and get outta there. Exit VNC client locally, and reconnect - now it prompts for password. Remove the authrequired key.
Hope that helps someone else lose less hair!
--- Adrenalynn
Follow jstack's advice to create a no-auth required by setting AuthRequired dword to 0.
Immediately log in with VNC and start it as a service.
Now since VNC is hooking video as if we were sitting in front of a console rather than RDP's session stuff, we can attach to the newly started vnc service. Go to start->program files->Ultra VNC->Ultra VNC Server [folder]->Show Default Settings (Assuming everything is in the default places/names at least...)
Now set your password. Do a save and get outta there. Exit VNC client locally, and reconnect - now it prompts for password. Remove the authrequired key.
Hope that helps someone else lose less hair!
--- Adrenalynn
-
- Posts: 1
- Joined: 2007-03-29 16:07
- Location: Italy
- Contact:
Re: installing remotely via MS remote desktop - set password
Hello,
I'm trying to solve the same problem on a new, different scenario.
The scenario is Vista as UVNC Server, Windows 2003 Server as repeater, Vista as Viewer.
I'm testing the 1.03 Beta of UVNC with Vista compatibilities.
The Viewer is on the Internet, Repeater and Server (of course) on the same LAN.
The problem is the one of ever: authentication failure when UVNC config is made within a Remote Desktop session.
The repeater works pefectly and it's not a problem.
I tried to put "AuthRequired=0" as an added line to the UltraVNC.ini file (finally, we're back with *.ini files..... not so bad a bit of Linux style....).
No positive effect achieved.
If I'm not logged on with RD, Authentication fails if I leave "MSlogon=1" on the .ini file.
If I set it to "0" and use the password that I originally set up directly to the server machine, I can load the login page of Vista....
But when I input the password to log on Vista, VNC disconnects.
The same happens if I'm already logged on with Remote Desktop and I launch a UVNC session to reach the same machine....
I load the Vista login page (with an advice that an open session is established), but when I put the password to log on, both Remote Desktop and UVNC are disconnected.
The RD error message back, told me that another user has logged on.
So, I didn't succeed in configuring UVNC within a Remote Desktop Session addind "AuthRequired=0" on the new ultravnc.ini file that avoid problems in Vista Registry.
Of course (as before), if a regular, local Windows user is logged on and working on the machine, I can easily access the machine with UVNC.
The problem, it seems to me, is in the authentication procedures and in some voided privileges that "Remote Desktop Users Group" suffers from.
It could be useful to identify which of these privileges are altered analyzing a normal administrator profile and an administration session launched through Remote Desktop.
A question of Policies, as ever, in the end....
I'm trying to solve the same problem on a new, different scenario.
The scenario is Vista as UVNC Server, Windows 2003 Server as repeater, Vista as Viewer.
I'm testing the 1.03 Beta of UVNC with Vista compatibilities.
The Viewer is on the Internet, Repeater and Server (of course) on the same LAN.
The problem is the one of ever: authentication failure when UVNC config is made within a Remote Desktop session.
The repeater works pefectly and it's not a problem.
I tried to put "AuthRequired=0" as an added line to the UltraVNC.ini file (finally, we're back with *.ini files..... not so bad a bit of Linux style....).
No positive effect achieved.
If I'm not logged on with RD, Authentication fails if I leave "MSlogon=1" on the .ini file.
If I set it to "0" and use the password that I originally set up directly to the server machine, I can load the login page of Vista....
But when I input the password to log on Vista, VNC disconnects.
The same happens if I'm already logged on with Remote Desktop and I launch a UVNC session to reach the same machine....
I load the Vista login page (with an advice that an open session is established), but when I put the password to log on, both Remote Desktop and UVNC are disconnected.
The RD error message back, told me that another user has logged on.
So, I didn't succeed in configuring UVNC within a Remote Desktop Session addind "AuthRequired=0" on the new ultravnc.ini file that avoid problems in Vista Registry.
Of course (as before), if a regular, local Windows user is logged on and working on the machine, I can easily access the machine with UVNC.
The problem, it seems to me, is in the authentication procedures and in some voided privileges that "Remote Desktop Users Group" suffers from.
It could be useful to identify which of these privileges are altered analyzing a normal administrator profile and an administration session launched through Remote Desktop.
A question of Policies, as ever, in the end....
Stefania Castelli
EU Customers +44 (70) 05978124
US Customers: +1 (215) 253-3706
Fax +44 (70) 05808124
stefania.castelli@hotmail.com
VoIP (Skype): stefania_castelli
Messenger: stefania.castelli@hotmail.com
ICQ: 10592354
EU Customers +44 (70) 05978124
US Customers: +1 (215) 253-3706
Fax +44 (70) 05808124
stefania.castelli@hotmail.com
VoIP (Skype): stefania_castelli
Messenger: stefania.castelli@hotmail.com
ICQ: 10592354
I'll confess to ignorance
I'll confess to ignorance as much of this discussion is well beyond mny grasp.
I am curious though, if the issue is installtion via RDP, could the install be added as a run once registry entry for install?
I can't really experiment much as I am in Oregon and my servers are in Dallas.... But maybe someone with a local server can try?
Thanks.
I am curious though, if the issue is installtion via RDP, could the install be added as a run once registry entry for install?
I can't really experiment much as I am in Oregon and my servers are in Dallas.... But maybe someone with a local server can try?
Thanks.