New Post: SftpClient.Connect - Session operation has timed out.

Hey Tim,

I'm hitting the same issue using a different method, we might have same problem. The previous post I started about PrivateKeyAuthentication works on my dev server. I moved it over to the production server (the key) and it fails on line 3 below with "Operation has timed out":

                var webClient = new WebClient();
                webClient.Headers.Set(Program._key_header_name, Program._key_header_value);
                String sensorKey = webClient.DownloadString(Program._key_url);
                var sensorKeyBytes = new MemoryStream(Encoding.Default.GetBytes(sensorKey));

The DownloadString method returns a "Operation has timed out" after about 30 seconds or so. If you are savvy with Wireshark, that got me going in a direction. I noticed on frame 7 of the handshake exchange that the Production server was returning "Warning, Description: unrecognized Name), Server Hello" while the development server did not. So I started looking at the certificate name of the prod server, and noticed it was using lots of aliases, while the development server was not. This might be the name issue its referring to in the WireShark packet capture. I'm still working the issue, no luck yet, but thought it might josh you into a direction.

Our issues might be completely different too though, since I'm using a WebClient and you are using SftpClient in which case I'll probably start a new thread on it.