I just want to take stock of the situation:
-
"NTLM Proxy-Authorization phase 3 failed: received corrupted data from proxy server" means that ovpn was unable to manage the phase2 decoding the base64 message;
- if nothing happen after
"Attempting NTLM Proxy-Authorization phase 3" than i think that phase 3 message is empty for some reason.
since i do not have access to an isa proxy i'm not able to do more tests.
logs I checked from Dale show that the proxy uses a negotiation step before asking for ntlm:
from IE7 sniffer:
HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy filter is denied. )
Via: 1.1 PROXY NAME
Proxy-Authenticate: Negotiate
Proxy-Authenticate: Kerberos
Proxy-Authenticate: NTLM
Connection: Keep-Alive
then the browser reply with:
GET http://www.mysite.com HTTP/1.1
Accept: */*
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; MS-RTC LM 8)
Accept-Encoding: gzip, deflate
Host: www.mysite.com
Proxy-Connection: Keep-Alive
Proxy-Authorization: Negotiate TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==
openvpn do not support that approach but sends NTLM phase 1 message directly:
CONNECT openvpn.site:443 HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; MS-RTC LM 8)
Proxy-Connection: Keep-Alive
Proxy-Authorization: NTLM TlRMTVNTUAABAAAAB4IIogAAAAAAAAAAAAAAAAAAAAAFASgKAAAADw==
in that case ovpn simply ignore the phase 2 message sent by the proxy.
I think we should go by steps, we could start with NTLM auth first and then looking for NTLMv2.
bye.