Drive for Desktop and Password-Protected Proxies

Google’s administrator documentation states that Drive for desktop does not support proxies authenticated with a password. If that is the intermediary’s requirement, repeatedly changing the Google account password will not supply a supported proxy login.

Ask the network administrator to arrange an approved route compatible with the desktop client. Use Google’s published Drive connectivity requirements when deciding which destinations the policy must permit; allowing only the browser’s initial Drive page may be insufficient for synchronization.

A decrypting proxy introduces a separate requirement. Google documents the Drive-specific TrustedRootCertsFile setting for trusting its certificates. That setting does not add password-based proxy authentication.

The same documentation lists DNS and DHCP proxy discovery on Windows, and DNS discovery on macOS. Verify the deployment method and the desktop client itself rather than treating a successful browser session as a complete sync test.