UltraVNC

This might explain an issue I have seen with the standard Viewer/Server. With 3D Bronze pointers on the server, if I select Auto the connection crashes. But, if I choose LAN, it works fine. I suspect that SC is using Auto ...

I tried that, and I no longer get the first error, but the Connection window is stuck at "Negotiating Protocol Version ..." and does not advance to logon prompt.

Danke. I'll check it out ...

Tried the 1.1.0.1 versions of server and viewer with 118RC2 ... unfortunately no relief. Get same "invalid protocol" window.

I am running version 1.0.0 ... where is 1.1.01 available? Also, a bit of an update. When I uncheck "New MS Logon (supports multiple domains)" the connect still fails, but I don't get the aforementioned error. The status window gets stuck with the following display, and the viewer locks up ...

Excellent! That would be great! Keep us posted...

Using UVNC 1.0 on XP Pro SP2 as server, clients are 2000 Pro SP4 connecting over WLAN with WPA-PSK AES. Clients also running v1.0 of UVNC. With MSRC4 118, everything works as expected. However, when 118RC2 is used, the server aborts the connection (according to logs ... available from link at bottom ...

I've been told that the DSM architecture doesn't support more than 2 threads (one in and one out) ... so, if the MSRC4 Plugin is used, there can only be one client connected to the server. If a second client attempts connection, both are disconnected. Are there any plans to add multi-threading to ...

As the Incoming Connection Query Window, but for when File Transfer window is initiated. Rational: Currently no way to know when someone is downloading files during VNC session remotely.

lenisham wrote:Don't blame XP for ZoneAlarm's inabilities. It's just a bit falkey.

I ran XP, ZA, and many flavours of VNC (including Ultr@) for years with no issues at all. Give VNC server rights and internet rights, and Bob's your uncle.

Okay.

But it seems that doesn't track with the intent of the feature. If you force "view only" mode, then file transfers do not appear to work on my systems. Seems forcing a Group 3 logon into Read Only mode intends the same thing.

That appears to have sussed it! Thanks! :D Follow up question, though. The user I have specified for Read Only access, while the user cannot move the mouse or interact with the desktop, he still appears to have the ability to initiate a File Transfer! Is there any way to lock down that Group 3 user ...

I've checked the FAQ, and done a search ... nothing seemed to hit upon my issue, or similar questions raised by others remain unanswered. I have, essentually, two issues: I am attempting to set up MSLogon with RC18. As long as the user is in the Administrator group, I can authenticate and log in ...