I often see the "Too many security failures"  message, and wait long time for login. It's terrible. So I decide to change it.

First i want to disable the waiting time. It is simple ,but too dangerous. Then i change to disable the waiting time double effect.

I am using the realvnc 4.1.6

Modify method:

1.Edit the "winvnc4.exe" with HEX editor

2.Search "d1e18948"

3.Change it to "90908948"

After the modify, the waiting time is always no more than 10 second.

Here's my setup and what happened :

I have multiple instances of VNC clients running on a MACintosh (Eggplant from Redstone software).

The MACintosh has a network connection to a RedHat linux machine.

The RedHat linux is running one instance of VNCserver, never ever had any problems with it.

The RedHat linux is configured with IP port forwarding, to forward VNC (:59nn) traffic to several windows XP PCs (:5900) on the other network connected to the RedHat linux box.  And each PC has a ROUTE ADD entry to tell it to reply via the RedHat linux box.

That way, the VNCclient instances on the MACintosh can access the VNCserver on each of the windows XP PCs via the RedHat linux IP by using different port numbers (:59nn).

This has been working just fine for about a month now.

But yesterday,... when attempting to connect to the VNCserver on one of the windows XP PCs for the first time in many days, I suddenly got this error message "Too many security failures". ....... I restarted the MAC and the RedHat and entered the ipforwarding on the RedHat over again, but it made no difference.

Then I attempted to run a VNCclient directly from the RedHat machine to the windows XP machine, and voila, that was working just fine. .... Back to the MACintosh again, but noooop,... still the same error message.  (ping worked fine, nothing wrong with the connections).

Then I remembered that I had several windows XP PCs set up (but not used before),... and yup,..... they were working just fine. .... But the ones I had been using many days ago,... noooop.

Then I left for the day, and came back today.

And suddenly everything was working fine !-) ,.........

I realy don't have a clue as to why ?,.......

But my current logic is asking : could it be it was related to the IP address the VNC server was replying to, and that a timeout cured it ?

I do not know if my Eggplant VNC client software make any pollings towards the connections not in use.  But I've never had any problems with the one I has been using almost every day.

I'm writing this in the hope that some VNC people maybe read it, and make sense out of it, and solve it in a future version.