Have exactly the same issue with 3.5 client on Windows 10 connecting to a secure server on port 4443. If the cause is really because of not using a standard port 443, then the developers need to be fired. In what world does someone not account for using a non-standard port especially having in mind that the product allows it. Totally unacceptable.