vncserver too many security failures

I have installed Win7 and Ubuntu both on this machine.

When I try to connect to my vncserver running on CentOS from my home computer behind a firewall, I get an error:

VNC conenction failed: vncserver too many security failures

... even when loging with right credentials (I reset passwd on CentOS).

Is this caused by attempting to log in as root? I think it is also important to note I have to login to remote Centos through port 6050 - no other port works for me.

Do I have to do something with other ports? I see that vncserver is listening on 5901, 5902 if another added - and I consider connection is established because from time to time (long time) the passwd prompt appears... right?

Even if prompt appeared and I put correct password I get an authentication failure.

How to disable this lockout for testing purposes?

I saw this error even though I only ever login from a single client machine with correct credentials. Looking in the logs, I saw that 0.0.0.0 was being blacklisted rather than specific IPs. My understanding then is that a failure from any IP is counted as a strike against every IP thus leading to the "too many security failures" issue. It seems this bug report describes things similarly. Using the suggestion there to shut down black listing (which if you have setup you server securely is of limited value), I ran this command on an ssh session on the machine running my vnc server replacing 5 with the appropriate display number:

vncconfig -display :5 -set BlacklistTimeout=0 -set BlacklistThreshold=1000000

After running this I was able to successfully connect with my vnc client and login. For me this was great as I had a lot of running processes associated with my vnc server which makes restarting it a pain.

"VNC conenction failed: vncserver too many security failures"

Means that someone tried to log in with incorrect credentials too frequently within a specified period of time. What that number and time is vary depending on what VNC Server you're using.

Someone's probably running a script trying to log into anything it can find listening on the standard VNC ports, and you'll need to find out what ip this is coming from and block it. Either way, this is really off-topic here - ask again over at SuperUser.