Windows 7

[SickPup404]

I'm using UVNC 1.0.8.2 on several machines.

My main client install is my Windows 7 64-bit desktop and it connects fine to all the XP machines and Server 2003 machines.

I have a new server install on a Windows 7 64-bit Dell (new out of the box) and installed 1.0.8.2 as a service, configured all the security the same way as my other machines and connected the first time as expected. However, EVERY time I try to connect now I get the "server closed connection, the server running as application" message after I type in my login credentials.

This Dell has Windows 7 Home Premium 64-bit, Microsoft Security Essentials, and the Windows Firewall. Nothing else is installed as of yet.

To resolve this, I have already tried:
- Searching Google
- Searching this (and other VNC) boards/forums
- Disabling the Windows Firewall
- Running UVNC as an application instead of service
- Removing and reinstalling UVNC

I need help and ideas as this machine is to be delivered to the customer site Saturday...

TIA
SickPup404

[supercoe]

My google for "Microsoft Security Essentials vnc" shows many resuts that it doesn't like VNC software.

The solution here is to uninstall the program.
http://social.answers.microsoft.com/For ... 794c30f95b

Get yourself better security software, I prefer Avira.

[SickPup404]

Thanks for the reply. MSE was a request from the customer since they also use Forefront at his office. I will talk with him about other options, but I doubt there will be much if any movement...

I have now tried:
- Uninstalling MSE.
- Reinstalling UVNC.

Same result, as I expected ("server closed connection, the server running as application" message). Nothing is happening with the UVNC executables - they are all there and accounted for. Logins happen as expected.

Other ideas/sugggestions?

[supercoe]

Is it possible for you to run UltraVNC as an application?
Many users are having problems with 7 64bit installed as a service.

Are you using an encryption plugin? Just for testing try without.

[SickPup404]

FYI - I am not using any encryption plugins yet, it's all on my local LAN for now. Also, I already tried running as application with the same result (the message after login).

The strange thing for me is that it worked successfully one time, then after a reboot I started getting this problem...

When I've uninstalled and reinstalled, all the prior settings have been kept. Is there a cleanup utility or something to prune out the branches from the registry that might be left behind after the uninstall? Trying to go for a completely clean environment...

Thx again for the help so far!

[Rudi De Vos]

+Does the viewer close after you enter the vnc passwd or after you logon
in windows ?

If it disconnect after logon, you need to activate the autoreconnect option ( viewer). In win7 the server reset on session change, without this viewer parameter the viewer close, else it reconnect in background.

All ultravnc settings are in the ultravnc.ini file, no registry is used.
If you erase this file, the file is recreated with defaults.

Do you see 2x winvnc.exe running ( show all users)
1x service
1x is winvnc started in the user session

[SickPup404]

OK, I tried changing the auto reconnect from the default of 0 to 5 and I still have the message.

The sequence of events:
- I connect in the client connect dialog to the server
- I get the UVNC Authentication dialog
- I enter my credentials and click logon
- I get the message popup "server closed connection, the server running as application"
- When I click Close in the message dialog, all UVNC windows on the client close.

When I check the system tray on the server side after a failure, there are two UVNC icons there, but when I mouseover one it disappears leaving just one. Task Manger shows just one "winvnc.exe" in the Processes tab, and one "uvnc_service" in the Services tab.

[EDIT]
Actually, forgot to click on "all users". Just went back and did. There ARE two instances of "winvnc.exe" that are running on the server side.
[/EDIT]

[SickPup404]

Would ChunkVNC help any in this situation?

[supercoe]

Would ChunkVNC help any in this situation?

ChunkVNC is just a wrapper that sets up UltraVNC, if your unsuccessful with Ultravnc, you'll more than luckily be the same with ChunkVNC.

They biggest difference in your current setup would be the inclusion of the repeater.

Test out one of the ready to run (RTR) versions that use a public repeater.
If it works then setup a repeater of your own!

[SickPup404]

Well, I'll not have a remote solution for now. I think I'm going to set up an additional Windows 7 machine and do some experiments to see if I can find a solution that works for me.

One other piece - the install of Windows 7 on the server is x64... I don't think it should make a difference, but I thought I would add it....

Thx to all who tried to help.

[santonoff]

I was getting the same message when running UltraVNC as an application under Win7 until I started it as Administrator (using runas).

Try turning off the service, use runas to start the app as an application as administrator: not a long term solution but it might get you started

runas /user:{machine_name}\administrator {path}winvnc

You will be prompted for the Administrator password, so this doesn't work before login.

This worked better than any configuration I had tried before.

Steve

Well, I'll not have a remote solution for now. I think I'm going to set up an additional Windows 7 machine and do some experiments to see if I can find a solution that works for me.

One other piece - the install of Windows 7 on the server is x64... I don't think it should make a difference, but I thought I would add it....

Thx to all who tried to help.

[santonoff]

I discovered that the problem returns after the UVNC server machine goes into a "locked" state (password protected screen saver, UVNC disconnect, etc). Once that happens, UVNC running as an app will not allow connections.

I was getting the same message when running UltraVNC as an application under Win7 until I started it as Administrator (using runas).

Try turning off the service, use runas to start the app as an application as administrator: not a long term solution but it might get you started

runas /user:{machine_name}\administrator {path}winvnc

You will be prompted for the Administrator password, so this doesn't work before login.

This worked better than any configuration I had tried before.

Steve

Well, I'll not have a remote solution for now. I think I'm going to set up an additional Windows 7 machine and do some experiments to see if I can find a solution that works for me.

One other piece - the install of Windows 7 on the server is x64... I don't think it should make a difference, but I thought I would add it....

Thx to all who tried to help.