We have a strange behaviour with connect-nacontroller on one controller. I did a test with debug logging turned on. On one controller an ontapi request via https times out. On the partner it works. TLS is on and ssl v3 off on both systems. Any ideas what I can do on the controller to get https working again?
By the way this debug has a lot of text but the most important for me is in German and unfortunately I Couldn't understand it.
$Global:CurrentNaController is the variable in global scope that is used to store your connection to a filler. It will be set at any new call to Connect-NaController.
Reviewing you call, it doesn't matter if you enabled TLS and SSL because you are not using HTTPS, actually you are working with RPC. Once I had a similar problem. It was related to a CIFS setup but I don't remember which was my final solution. But as a workaround you can simply set HTTPS parameter.
I really think you should not use RPC since cluster mode does not make use of this protocol.