Fix Google Drive Authentication Errors in NetDrive

A designer opens her laptop on Monday and the Google Drive volume that worked all of last week is gone from Explorer. In NetDrive the drive sits in an error state, and clicking Mount brings up a sign-in failure instead of a drive letter. Nothing changed in NetDrive, but something changed on the Google side: the saved authorization is no longer accepted. This guide sorts the usual causes and gets the drive mounted again.

Google Drive as a native drive

NetDrive lets Google Drive, OneDrive, S3, SFTP, WebDAV and more appear as native drives on Windows and macOS — no syncing, no full downloads.

• Works with personal Google accounts and Google Workspace
• Shared Drives supported by default since NetDrive 3.1.218
• Re-authorize in your browser without deleting the drive

WindowsmacOS

Download NetDrive →

Free trial. Lifetime and subscription plans available.

Why a Working Google Drive Connection Suddenly Fails

NetDrive signs in to Google through a browser-based authorization. After you approve access once, NetDrive keeps the saved authorization and reuses it on every mount. When Google stops honoring that authorization, the drive shows an authentication error even though your internet connection is fine.

The usual triggers:

• Access was revoked. Removing NetDrive from your Google Account’s third-party access list invalidates the saved authorization immediately.
• Security event on the account. A password change or a “sign out everywhere” action can end existing authorizations.
• Workspace admin policy. On a managed Google Workspace account, an administrator can restrict which third-party apps may access Drive data. If the policy changed, a previously working drive can start failing.
• Authorization was granted to a different account. If you were signed in to two Google accounts in the browser during setup, the approval may have gone to the wrong one.

Step 1 — Rule Out Network and Google Outages

Look at your other drives first. If an S3 bucket or an SFTP server in the same NetDrive window also fails, the problem is your connection, a proxy, or a VPN rather than Google authorization. If only the Google Drive entry fails, open drive.google.com in a browser. If the web interface asks you to sign in again or shows a security prompt, deal with that first; the mounted drive cannot work while the account itself is locked.

Step 2 — Re-authorize the Drive

Re-authorizing fixes most cases, and you keep the drive entry and its settings.

1. Open NetDrive and find the Google Drive entry in the drive manager. Do not mount it yet.
2. Open that drive’s settings (the edit option on the drive entry).
3. Look for a re-authorize or sign-in-again option. The exact label can differ between versions.
4. Your default browser opens a Google sign-in page. Choose the correct Google account and approve the access request.
5. Save the changes, then click Mount.

If the browser page never opens, check that you can reach google.com directly from that browser. A corporate proxy or a restrictive default-browser setting is the most common culprit. If you manage several Google accounts, sign in to the intended one in a private window first so the approval cannot land on the wrong account.

Step 3 — Check for Workspace Restrictions

If re-authorizing ends with a message that the app is blocked or that you need administrator approval, the restriction is on the Workspace side. Only an administrator can change it. Send them the specific error text, and ask whether third-party app access to Drive is limited in the Google Admin Console and whether NetDrive can be added to the list of allowed apps. Until that policy is changed, no amount of retrying in NetDrive will help.

It is also worth confirming that a personal account behaves differently. If a personal Google account mounts fine on the same machine while the work account fails, that points straight at policy rather than at NetDrive or your network.

Step 4 — Confirm the Mount and the Folder View

After a clean sign-in, allow a few seconds for the first directory listing. The drive then appears as a drive letter in Windows Explorer or a volume in Finder.

If you can mount but Shared Drives are missing, that is a different problem with its own fix: see Fix Google Shared Drives Not Showing in NetDrive. If files you just saved elsewhere do not appear, use Force Folder Refresh instead of re-authorizing.

Keeping It From Happening Again

• Change your Google password, then re-authorize NetDrive in the same sitting, so the Monday-morning surprise never happens.
• Avoid pruning your Google Account’s connected-app list without checking what each entry is.
• On shared work machines, one person’s Google account per drive entry keeps approvals from crossing over.

If a whole team depends on one Google Drive connection, an administrator can publish it once through Team Drive rather than having each person authorize separately.

Wrap-up

Nearly every Google Drive sign-in failure comes down to an authorization that Google no longer accepts. Confirm the web account is healthy, re-authorize from the drive’s settings, and escalate to a Workspace administrator only if the error mentions a blocked app. For first-time setup, see Mount Google Drive on macOS or on Windows 11.

— Steve, NetDrive