nraddatz wrote
I have already taken care to set script-security to 3, which seems to be the most common cause for this problem
--script-security 3 is specifically required. See --
script-security in
The Manual v24x
nraddatz wrote
have also tried invoking a dumb .bat file which returns error code "1". Same thing - user is still allowed to log in.
The batch file is not being called and is not present in your active config, otherwise the client connection would be refused.
You must post your logs at --
verb 4 .. See --
log & --
verb in
The Manual v24x
As per: