VNC to Unity taking a long time or being dissallowed

[shane.orr]

CSA is dissalowing VNC connections on a timely fashion with a message:

The Process c:\program files\realvnc\vnc4\winvnc4.exe is attempting to capture keystrokes. Do you wish to allow this?

I assume something has changed in the later CSA versions or possibly the combination of VNC 4, CSA, and Windows 2003. I have been using the same version of VNC for quite some time.

Anyone have any ideas?

[tsteger1]

Later versions of CSA separated the Trojan Detection rules into different rule modules.

The rule that tracks keystroke trapping in CSA 5.2 is a "System API control - All Applications, Trap keystrokes" and you'll need to create a separate exception for that.

Tom

[shane.orr]

Well unfortunately I typically just use the standalone CSA with Call Manager and Unity but this is helpful information so thank you!!

[tsteger1]

You are welcome and good luck!

Tom