I've recently run into a similar issue which has been raised internally - are you attempting to connect to a server with a specific port number, e.g. server.example.com:8443 ?
Edit: looks like this has been confirmed as an issue internally and people are working on it, for now please use the 3.4 client. We'll post an update when there's a fix available or a better workaround.
