UltraVNC

There seems to be a bug with DNS resolving.

When using the repeater to connect to a client named "PC-Test1", the repeater seems to resolve "PC" and therefore will never get the correct client IP.

Best Regards
tomha

Solved in 1.0.8.0

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 u ...

@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 ...

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 ...

I can not commit that this problem is fixed. I tested again and again when the server is locked all connectivity is lost(not only uvnc, also rdp and telnet). It is a bug in V 1.0.6.4 and 1.0.6.5 because this behaviour does not appear with version 1.0.5.6. I tested with clean install after removing ...

Service mode

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.

very bad thing
would be happy to get informed when the problem is solved
best regards

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 ...