Upgraded from UVNC 1.0.5.6 to 1.0.6.4(installed as service) on a customers server. The server is reachable via uvnc, rdp and telnet. When connected to the server via uvnc and doing nothing till the server locks itself(Ctrl-Alt-Delete to login again) the connection drops, all clients connected via repeater disconnect also and then the server isnÂ´t reachable anymore. Then rdp and telnet are failing to connect, too. No Connection possible till the server is restarted.

Same behaviour under 1.0.6.5
First remote access via uvnc is ok. After the user is auto-logged off from the server the viewer screen freezes and then i get a socket write failed error. When trying to reconnect there is no access via uvnc or rdp till the server is restarted. Very dissapointing.

1.0.6.5 fixed the problem on my server. But the screen refresh does not always work, I often have to select Request Screen Refresh, or I go to send the Ctrl-Alt-Del, then enter the password and Enter, and the screen finally refreshes...

The refresh problem sometimes happens while logged in and just clicking in a two part window, the window then shows just parts of what it should...

I think there should be no difference between sbs 2003 R2 and Server 2003 R2.
In this especially case it is very hard to test, because i can only do this via remote connection an it is a productive server. If it fails i have to hard reset the server via VPro if remote functionality locks up. Now we went back to 1.0.5.6 an this server which works without problems.
I will set up a new test system next week and will report the results.

In this especially case it is very hard to test, because i can only do this via remote connection an it is a productive server.

You should never test a software on productive computer.
You should use virtual software, then a physical similar to productive computer for try the new software is fullfill your requirement, then install on productive computer especially if a server.

could you tell us the step by step what you doing for help Rudi to find any bug.
vncviewer version and OS, uvnc server version and OS
network type and speed both side.
via internet or only local
you wrote you use via terminal service.

@redge:
of course testing on a productive system is at high risk, but this was the first system showing this behaviour after an upgrade from uvnc 1.0.5.6 to 1.0.6.4 or 1.0.6.5

SBS 2003 R2 x86 is installled on intel Q45 Mainboard. There are three clients(Q45 mobo, too) with Windows XP Pro x86(all SPÂ´s and Patches applied). We connect through DSL with a Zyxel Zywall 2 Plus as HW Firewall. The other site(my office) is equipped with DSL, too.
Initially we installed UVNC 1.0.5.6 (as service, mirror driver installed and working)on the server and the clients. The server is accessed through port 1224, the repeater is listening on port 1225 repeating to the clients on port 1224. In this config there are no problems. The server is accessible via uvnc on port 1224, telnet on port 23 and rdp on port 3389, all the time.
Then we upgraded to UVNC 1.0.6.4 on all machines. Initially all access was ok. We did the upgrade on the physical machine as an update. After going back to my office the server was unreachable via uvnc, telnet and rdp. after a server restart it was accessible again. The standard behaviour of sbs 2003 is to lock the desktop after some minutes of inactivity and then it is unreachable till a restart.
I then uninstalled uvnc complete and reinstalled V 1.0.6.4 with the problem persisting. With V 1.0.6.5 the server gets unreachable after the desktop lock, too. Unfortunately i had no chance to examine the machine physically when its unreachable, so i had to restart it remotely. Then i uninstalled V 1.0.6.5 and reinstalled 1.0.5.6 which is working without problems again.

As i wrote yesterday, i will do further tests with an q45 board and sbs 2003 next week at my office and post the results.

2) Same problem as others with screen saver/lockup. I can use PSKILL (to kill winvnc on remote machine) and PSEXEC (to restart it on remote machine) and it is usable again. Until the next timeout. I'm trying to determine specifically if it's a CLIENT SIDE screen saver or a SERVER SIDE screen saver that causes the problem. I'll post again if I can isolate it to one side or the other.

1) UVNC 1.0.6.5 server locked when i was using the Client machine doing other things, so it was not a Client side screen saver that caused the problem. I went to the remote system (down the hall) and it's screen saver had NOT kicked in on screen, even though it should have.

2) After resetting UVNC, I turned the screen saver off on the remote machine. UVNC has not locked up since.

3) It seems that UVNC prevents the SBS 2003 server from going into the screen saver mode, and when that happens UVNC service locks up, too.

I have no idea if this is related to the "screen does not refresh or update before login" problem.

I tried to reproduce this strange behaviour with an VM with Server 2003 R2 installed.
The system enters the screensaver correctly and there was no lockdown.
So the problem seems hardware/driver related. At the moment iÂ´m to busy to do further tests. On the customers server which is locking up, i unfortunately do not have physical access, so i have to keep UVNC 1.0.5.6 installed and cannot tell how the machine behaves physically when it is not remotely accessible. In my lab i have another Q45 mobo. So i will install Server 2003 for further tests on identical hardware, when i have got a little bit of spare time.

ultravnc server on w2k3 server sbs
you can checkbox on winvnc properties (not admin properties)
Poll full screen
Poll foreground window (that should solve the screen refresh issue on login screen for uvnc 1.0.6.5) it was what a was doing for fixing the issue but with welcome screen FUS (not classic logon)

I have a very similar problem, which happens both with an installation of 1.0.6.5 and after de-installation and re-installation of ver 1.0.8.0

The computer the VNCserver is running on has installed "Windows Server 2003 Enterprise Edition Service Pack 2", and has an activated ScreenSaver with the option enabled to ask for the credentials again after the screensaver kicks in.

The effect is, that after a certain time (POSSIBLY the time necessary for the screensaver to come up, maybe less), the VNCserver freezes, and the entire computer is locked up. Unfortunately I don't have physical access to the computer, but according to the support-guys that DO have access, the computer wasn't even reacting to input on a locally connected keyboard, and they had to do a hardware-reset. What I could see was: no response on ports 22,80,443,3389,5900 all of which SHOULD be open normally.

One thing that might (but probably shouldn't) affect the problem is, that I was also logged in via RemoteDesktop at the time I tried out the configuration of UltraVNC - oh, and UltraVNC was run as a service, when it happend, and the "mirror-driver" was not installed.