I have the server 1.01 installed and routed properly, I then use the viewer 1.01 to connect. I get the password prompt and then type it in and submit and it disappears and nothing else. Also, I tried the java connection and it comes up with an error after login that the server has closed connection or the connection has been rejected error.
What is happening?
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
viewer quits right after entering password
-
TheNETCoder
- 8
- Posts: 8
- Joined: 2005-10-23 02:45
- Location: Germany
specs
the server is running on a small business server 2003 system. I'm on XP for viewer. I've done this before with an earlier version and had no problems. recently I had to rebuild the sbs machine and stuck on 1.01 of UVNC and now this problem. I was needing this as it would allow me to finish the service pack installs from home rather than sitting in the office.
The service is obviously still running as I can repeatedly get the logon screen from home. OVER AND OVER.
The service is obviously still running as I can repeatedly get the logon screen from home. OVER AND OVER.
everyone,
Did you start with classic authication only to see if everything is setup properly. I had some issues with windows 2003 server and that is how I connect to them..
If you use Mslogon you have to make sure that the userid has logon rights to the server. If they don't you will lock up the ultra vnc server and need to restart the application or restart the service..
Did you start with classic authication only to see if everything is setup properly. I had some issues with windows 2003 server and that is how I connect to them..
If you use Mslogon you have to make sure that the userid has logon rights to the server. If they don't you will lock up the ultra vnc server and need to restart the application or restart the service..
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
I'm using classic....
I found the issue... the screen had gotten locked on the other end. once i had somebody move the mouse and login there I could login here.
BUT, now I rebooted the server and try to login and I get a message that This server does not have a valid password enabled. What is that about?
I found the issue... the screen had gotten locked on the other end. once i had somebody move the mouse and login there I could login here.
BUT, now I rebooted the server and try to login and I get a message that This server does not have a valid password enabled. What is that about?
Are you using the same version of Ultra VNC on all the computers ???
If you are dealing with work networks you want to make sure that the company doesnt have a policy against what you guys are trying to do. A lot of companies IT departments will not like this.. but if you are the IT department then nevermind. I just dont want to see anyone in trouble for using vnc when their company has rules against it nothing more.
If you are dealing with work networks you want to make sure that the company doesnt have a policy against what you guys are trying to do. A lot of companies IT departments will not like this.. but if you are the IT department then nevermind. I just dont want to see anyone in trouble for using vnc when their company has rules against it nothing more.
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
-
gabr1ele
I AM THE IT :-)
Yep, I am the IT dept. These are small businesses that I use this on so I can do server maintenance alot better than remote web workspace and I think nicer than remote desktop ( I don't need to print or sound so no difference). Anyway, I think I've found some specific things to help. \
1) To finally get logged in initially I had someone wake up the monitor and login from there.
2) I then turned off the "Turn off monitor after xx minutes" option in power and ALSO turned off the "On resume, Password Protect" option on Screen Saver.
Still had to ctrl-alt-del to get into server once VNC logged in, but that is fine...
3) Now for the no password error... That happened because I had the VNC setup to run as service but had NOT rebooted since setting it up. I just ran it from the icon on desktop and then proceeded to be frustrated for a day or so.
When you reboot the system after setup the service will say something about no default password set so that properties dialog will now start. This allows you to set the admin password for VNC and the options permanently.
SO, this lesson: turn off password protect and blank monitor ( i usually set screen saver to blank though).
install VNC as service and REBOOT..
THEN set default password and maybe even reboot the system one more time to make sure service starts..
THEN connect and all should work.
1) To finally get logged in initially I had someone wake up the monitor and login from there.
2) I then turned off the "Turn off monitor after xx minutes" option in power and ALSO turned off the "On resume, Password Protect" option on Screen Saver.
Still had to ctrl-alt-del to get into server once VNC logged in, but that is fine...
3) Now for the no password error... That happened because I had the VNC setup to run as service but had NOT rebooted since setting it up. I just ran it from the icon on desktop and then proceeded to be frustrated for a day or so.
When you reboot the system after setup the service will say something about no default password set so that properties dialog will now start. This allows you to set the admin password for VNC and the options permanently.
SO, this lesson: turn off password protect and blank monitor ( i usually set screen saver to blank though).
install VNC as service and REBOOT..
THEN set default password and maybe even reboot the system one more time to make sure service starts..
THEN connect and all should work.
enrahl,
I know what it is like to be the IT dept. I have been it myself for over 6 years now. Before that I built university computer labs for 4 years. Once you get that baby working on Ultra VNC with basic settings look into the MSRC4 plugin for encyption. I found it best to start with only basic settings at first. No MSLongon I or New only classic vnc authenication and have your sever setup to speed auto. And no dsm plugin at first.
In case you havent found the following documents they may help
For the UltraVNC settings and registry locations:
[topic=4684][/topic]
For a Single Click document:
[topic=4606][/topic]
I always found it best to do testing if possible in a LAN environment first before you switch to a WAN enviroment. If it doesn't work in a LAN it will not work in a WAN. That way you are not fighting several problems at once..
I know what it is like to be the IT dept. I have been it myself for over 6 years now. Before that I built university computer labs for 4 years. Once you get that baby working on Ultra VNC with basic settings look into the MSRC4 plugin for encyption. I found it best to start with only basic settings at first. No MSLongon I or New only classic vnc authenication and have your sever setup to speed auto. And no dsm plugin at first.
In case you havent found the following documents they may help
For the UltraVNC settings and registry locations:
[topic=4684][/topic]
For a Single Click document:
[topic=4606][/topic]
I always found it best to do testing if possible in a LAN environment first before you switch to a WAN enviroment. If it doesn't work in a LAN it will not work in a WAN. That way you are not fighting several problems at once..
Bevtech
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
Windows XP Home, Pro SP2, Windows 2003 SBS server SP2(EN), Windows Media Center Editon 2005,Windows Vista Home Prem.,Fedora Core 6,Win9X, PChelpware Rel 1.0,
UVNC V 1.0.8.2
User not developer..
it worked before in the same WAN before the system crashed and had to be reinstalled, but the server had already been setup before I added the VNC and it could've had locking already off. all same settings and it's working now that I turned off the settings I mentioned above. I think this is a bug. This program should be able to connect even when the system is locked after a period of time.