I have a three server workflow manager farm. I'm using hardware load balancing across the three servers. I've associated a hostname in DNS with the VIP on the NLB.
When I run Register-SPWorkflowService and point at the hostname for the -WorkflowHostUri parameter, I get the error:
Register-SPWorkflowService The underlying connection was closed An unexpected error occurred on a receive.
If I put that URL into a browser on the SP machine where I'm running this cmdlt, it responds with the correct XML. So I know that the NLB is routing regular http requests to my machines in the quorum.
Also, if I use the actual machine name of one of the three machines in the workflow manager quorum, the cmdlt works.
I know very little about NLB hardware. Is there something I need to tell the guys configuring the NLB to do so that the connection doesn't close?