But in Lightroom CC, I have a message in the top right corner telling me "Network Disconnected". Nothing happens. Failed at step 1. I can't see any settings relating to proxy behaviour and I can only guess that "network disconnected" means that Lightroom CC can't find its way out through the proxy.
Is this for real? Lightroom CC is 100% "cloud-native", but can't work with a corporate proxy? Tell me I'm doing something wrong...
Can you share more info about the type of proxy configuration your company uses? For example, Kerberos, PAC+Kerberos, NTLM, WPAD, etc.
Do you happen to know if your proxy allows port 80 through?
If you need to sign into your network proxy, can you confirm the Creative Cloud app displays its own proxy login screen (see attachment; if you didn't see this, can you try quitting and re-launching the Creative Cloud app)
We use port 8080 for the proxy server and block port 80 because otherwise people can bypass the proxy server.
The thing to note is that every other Adobe CC product works absolutely fine with my setup. The screen you provided showed up just once when I had to first inform CC of my CNTLM setup, and that's it - all CC products worked seamlessly thereafter.
But not Lightroom CC. It just flat out doesn't work. It also doesn't challenge me for proxy information / passwords. It just says "Network Disconnected".
Oh, and the corporate proxy operates on 8080. CNTLM is able to translate port 80 on the application side to 8080 on the proxy side.
After some discussion with the team, I don’t have much news to share...
I previously neglected to share Creative Cloud’s stated
requirements for proxy support: https://helpx.adobe.com/creative-cloud/kb/proxy-authentication-support-creative-cloud.html
This does say NTLM is not supported for Creative Cloud. After raising your issue with the team, I still can’t say if or when support for NTLM will be enabled in Creative Cloud. Please check back on the page above periodically for possible updates. Sorry I don't have something more helpful for you at this time.
I have performed traces with Wireshark and I can see that when the proxy is set to auto, most connections do go through the proxy but the application tries to contact servers within Amazon's cloud directly on port 443. This of course fails because of the firewall. So it seems that the application does not support automatic proxy configuration.