There are a few thing that could give that appearance, and likely you are not banned.
The strongest one is if you carry a connected ‘private node’ whos node number is the same as the node number connected to your intended conectee.
If this is the case, renumber your private node to something arbitrary (out of the blue) like 1066
Or, if you are using NNX, use one of the exansion nodes unregistered for it, so it will be private and unique.
There is a loopback protection that creates these results and the check does not differentiate between public(registered) and private(unregistered) nodes.
I think I recall that you said you fixed it in the ticket you opened, but I can’t remember. If not, I believe the BANNEDCONNECT error is generated from the Permit/Deny list in the ClearNode. Best to check your settings there.