Installed 1.0.8.2 on a Win7 laptop (client) and an XP system (server). I've established what port it's listening on (5901). I've had a number of different failure modes:
* One time it gave an error something like "service running as application" or something like that -- only saw it once.
* Frequently it immediately rejects the connection, "Your connection has been rejected."
* Other times it connects successfully, and prompts me for the VNC password, but never accepts the password. ("VNC authentication failed!") I see no pattern behind rejections vs. password failures.
* I've tried the browser (http://host:5801) and I get the same results with IE. In Firefox I can't enter the password.
When I installed the server, the Admin config already showed a VNC password. I don't know what it was. I replaced it with a password that happened to be shorter. When the password failed, I went back to check the Admin panel, and the password had been reset to an 8-char length. I set it to my shorter password (several times) and it keeps resetting to 8 chars. What password is it changing it to? Or is it just displaying 8 splats even if I enter a shorter password? Why can't I get it to accept my password??
The fact that my connections aren't consistent makes me wonder what's going on. These two systems are on a LAN.
Gary
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
Connection problems
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: Connection problems
The password box hide the size, it always show 8 chars.
(also for an empty passwd)
Try this first
1) Copy winvnc.exe to a temp folder, on the desktop this way you are 100% sure that the current user
has full access. Start winvnc.exe from this temp folder as application.
On first run, it will recreate a winvnc.ini in this folder (popup ask for passwd)
Using a desktop folder, we are 100% sure the use has write access, win7 give restricted permissions
to the secure folder "program files". This exclude all permission trouble for testing.
2) Try to connect the viewer
*If this fail in 99% of the cases some firewall or anti virus software is blocking winvnc.exe or vncviewer.exe
*If it works, just copy the ultravnc.ini from the desktop folder to program files ultravnc folder. All settings/passwd are in this file
and you are 100% that the password was correct saved in this file.
Before running it as service, try it also as application from (program files ultravnc) folder.
Win7 has a seperate session for services, isolated from the desktop....some message could be hidden.
For win7 you better use the latest 10961, many bugs solved, but at least you should
be able to enter password and see the server
(also for an empty passwd)
Try this first
1) Copy winvnc.exe to a temp folder, on the desktop this way you are 100% sure that the current user
has full access. Start winvnc.exe from this temp folder as application.
On first run, it will recreate a winvnc.ini in this folder (popup ask for passwd)
Using a desktop folder, we are 100% sure the use has write access, win7 give restricted permissions
to the secure folder "program files". This exclude all permission trouble for testing.
2) Try to connect the viewer
*If this fail in 99% of the cases some firewall or anti virus software is blocking winvnc.exe or vncviewer.exe
*If it works, just copy the ultravnc.ini from the desktop folder to program files ultravnc folder. All settings/passwd are in this file
and you are 100% that the password was correct saved in this file.
Before running it as service, try it also as application from (program files ultravnc) folder.
Win7 has a seperate session for services, isolated from the desktop....some message could be hidden.
For win7 you better use the latest 10961, many bugs solved, but at least you should
be able to enter password and see the server
Re: Connection problems
Hi Rudi,
OK, I killed the winvnc processes, copied winvnc.exe to a temp folder, and ran it. Once I realized it moved from port 5901 to 5901, everything worked fine.
So I copied the ini file to the Program Files folder, and ran winvnc.exe again, and it worked!
This is XP!! Why did it have a problem setting it up in Program Files ??
Thanks!!
Gary
PS: I also ran "winvnc -install" to install it as a service, so now I think it's good to go for future reboots.
OK, I killed the winvnc processes, copied winvnc.exe to a temp folder, and ran it. Once I realized it moved from port 5901 to 5901, everything worked fine.
So I copied the ini file to the Program Files folder, and ran winvnc.exe again, and it worked!
This is XP!! Why did it have a problem setting it up in Program Files ??
Thanks!!
Gary
PS: I also ran "winvnc -install" to install it as a service, so now I think it's good to go for future reboots.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: Connection problems
If it move to port 5901, something is using port 5900.
winvnc check the used ports and use the first available...
We use runas to make changes to ultravnc.ini.
The default MS behaviour for runas is to refuse this program to make file changes
The runas popup
[v] Do NOT ALLOW
This is a very confusing runas option.....with the[v] you deny write permission.
The runas is only used when you install it as service, in application mode the default desktop user permissions are used.
winvnc check the used ports and use the first available...
We use runas to make changes to ultravnc.ini.
The default MS behaviour for runas is to refuse this program to make file changes
The runas popup
[v] Do NOT ALLOW
This is a very confusing runas option.....with the[v] you deny write permission.
The runas is only used when you install it as service, in application mode the default desktop user permissions are used.
-
- Posts: 1
- Joined: 2012-07-05 13:31
Re: Connection problems
Hello, long time user first time on this forum.
I have a spam new HP with a fresh installation of Win7 x64 Enterprise. I have downloaded the new 1.0.9.2 x64 version of UltraVNC. After it is all installed I edit the setting to give it a password to "view" and a "service" password. I also disable the Tray Icon. When I try to connect to the new computer I sometimes get a message that says "Your Connection has been rejected". Other times it lets me through to the password promt, but when I enter the password, i get an "Authentication Rejected" error message. The computer that I am using to connect to the spam new computer has always worked with all other computers in the company. The only difference is that the new computer is the only one that is x64 bit and that is using an x64 but version of UltraVNC. What can I do to resolve this issue?
I have a spam new HP with a fresh installation of Win7 x64 Enterprise. I have downloaded the new 1.0.9.2 x64 version of UltraVNC. After it is all installed I edit the setting to give it a password to "view" and a "service" password. I also disable the Tray Icon. When I try to connect to the new computer I sometimes get a message that says "Your Connection has been rejected". Other times it lets me through to the password promt, but when I enter the password, i get an "Authentication Rejected" error message. The computer that I am using to connect to the spam new computer has always worked with all other computers in the company. The only difference is that the new computer is the only one that is x64 bit and that is using an x64 but version of UltraVNC. What can I do to resolve this issue?
Re: Connection problems
I had the same problem. Hopefully I resolved the issue. I hope it works for you too.
If both computers (those running the uvnc server and the client) are in the same domain, they both should be synchronized with the same time server (which is probably the domain server). Otherwise you will get "VNC authentication failed!" error.
If both computers (those running the uvnc server and the client) are in the same domain, they both should be synchronized with the same time server (which is probably the domain server). Otherwise you will get "VNC authentication failed!" error.