Proxy with NTLM authentication doesn't workSolved

We'll work on this -- it probably won't be in the 3.2.1 release, but we'll either release a 3.2.2 release or include it in 3.3.

Wyatt we are still waiting here since february for this implementation. Do you have a timeframe for it?

Sorry, we've delayed this to TA 3.3 (instead of 3.2.2) because we haven't had an NTLM proxy server up and running (we don't use that protocol in our company, thus we've had to set it up).

How many customers do you have that use NTLM proxies? In the meantime have they used offline activation?

Sorry, we've delayed this to TA 3.3 (instead of 3.2.2) because we haven't had an NTLM proxy server up and running (we don't use that protocol in our company, thus we've had to set it up).

How many customers do you have that use NTLM proxies? In the meantime have they used offline activation?

Unluckily we had much customers in the situaton cause the Microsoft stack and Active directory are quite famous. They used offline activation with success but it is not quite acceptable when they have an internet connection up and running.

Which is the timeframe of TA 3.3?

We over estimated our ability to figure out how to set up an NTLM proxy. If you want to get a working version that support NTLM in the next couple of days we can do 1 of 2 things:

1. Let us have access to an NTLM proxy at your company. This way we can test to make sure the NTLM authentication works correctly.
2. Or, we can put together a version of TurboActivate that we're 95% sure will work on NTLM proxies, but we don't know for sure (but we don't have a working NTLM proxy up and running yet).

Tell me what you think.

Of course, the unstated 3rd option is that we'll set up our own NTLM test proxy in-house and release NTLM support with TurboActivate 3.3.

The other 2 options were just if you want NTLM support right now.

Did the version I sent you work for your customers?

This has been fixed in TurboActivate 3.3, coming soon.