While working on some projects at a large financial institution, I had a need to access my Internet Servers for various reasons.  While I had been granted the typical Internet Access (Web Access) through the company's Microsoft Proxy Server to download files and patch updates, the proxy server was not configured to allow me access to the most useful protocol of all, OpenSSH.

After several days of trying various solutions, I settled on a quick and dirty (and yet, surprisingly convenient) solution:  NTLM-Authenticate myself against the Microsoft Proxy Server so it will allow me to make an outgoing connection; and configure OpenSSH on one of my Internet Servers to listen in on one of the "Approved" ports that Microsoft Proxy Server will allow:  Port 80 (http), Port 443 (https), or Port 563 (snews).

With that approach in mind, and not wanting to reinvent the wheel, I took an already excellent SSH Proxy tool written by Shun-Ichi Goto, commonly known as connect.c.  It's a great tool that does the job for getting through most other http-proxy servers.  I simply added some NTLM Authentication support to his work, and was soon able to initiate ssh connections through the Microsoft Proxy Server that was troubling me.