It’s a long time since my last reply to this issue. But today i found the reason, i think, for this strange behavior.
Only one thing - is this host member of a cluster?
If yes then the cluster is the reason for this.
I found that this bug was fixed in 2.0p23 