Fix SharePoint Sign-In and Access Errors — NetDrive

4 min read troubleshooting sharepoint
Casey
CaseyProduct Manager
SharePoint won't connect in NetDrive? Check expired sign-ins, wrong site URLs, missing site permissions, and tenant restrictions to get your library back.

Monday morning, and the SharePoint drive your finance team relies on shows a failed connection. Or you are setting it up for a new hire and the sign-in window completes, yet the library never appears. SharePoint failures in NetDrive almost always come down to one of four things: a stale sign-in, a site address that points to the wrong place, an account without access to that site, or a tenant policy you cannot see from the client.

NetDrive drive manager showing Google Drive, S3 and pCloud mounted as drive lettersMounted clouds appearing as native drives in Windows File Explorer

Get your SharePoint library back

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

  • Re-authenticate a SharePoint drive without rebuilding it
  • Open document libraries in Explorer or Finder
  • Keep every other cloud in the same drive list
WindowsmacOS
Download NetDrive →

Free trial. Lifetime and subscription plans available.

Match the Symptom to the Cause

What you seeMost likely cause
A drive that worked for weeks now fails to connectThe saved sign-in expired or the Microsoft account password changed
Sign-in succeeds but the library is empty or missingThe site URL points at the wrong site, or the account lacks access to it
”Access denied” style message for one site onlyYour account is not a member of that site
Sign-in window is blocked or asks for admin approvalA tenant policy restricts third-party apps

Work from the top. The first two rows cover the vast majority of cases.

Fix 1: Re-Authenticate the Saved Drive

When a Microsoft password changes, or the organization forces everyone to sign in again, the credential NetDrive saved for that drive stops working. You do not need to delete the drive.

  1. Open NetDrive and go to Drive Manager.
  2. Select the SharePoint drive and click Edit.
  3. Start the sign-in again and complete it in the browser window with the account that owns access to the site.
  4. Click Connect.

NetDrive Drive Manager listing configured cloud drives, where a SharePoint drive can be edited

If your browser is already signed in to a different Microsoft account, the sign-in window may silently reuse it. Use a private window, or sign out of the other account first, so the right identity reaches NetDrive.

Fix 2: Check the Site URL

SharePoint addresses look like https://yourcompany.sharepoint.com/sites/SiteName. Copy the address from the browser while you are viewing the exact site that holds the library, not from a shared link someone emailed you. Sharing links often contain long path fragments that do not describe the site itself.

Common slips:

  • Using the address of a single file or folder instead of the site.
  • Copying a site address from a different team that has a similar name.
  • Leaving a typo in the site name after retyping it by hand.

Paste the corrected address into the drive’s edit dialog and reconnect. If you manage several sites, create one NetDrive entry per site rather than reusing one entry with different addresses.

SharePoint provider logo as shown in the NetDrive provider list

Fix 3: Confirm the Account Is a Member of the Site

If the sign-in completes and NetDrive still cannot list the library, open the same site URL in a browser using the same Microsoft account. If the browser also reports that you do not have permission, NetDrive cannot do any better: it can only reach what the account can reach. Ask the site owner to add the account as a member or visitor, then reconnect.

The reverse test is useful too. If the browser opens the site normally but NetDrive does not, the problem sits in the saved sign-in, which brings you back to Fix 1.

Fix 4: Ask Your Administrator About Tenant Policy

Some organizations limit which third-party applications may sign in to their Microsoft 365 tenant, or require an administrator to approve each one. If the sign-in window shows a message about needing admin approval, or is blocked outright, no client-side change will help. Send your IT contact the message exactly as it appears, along with the name of the app you are signing in from, and ask whether it can be allowed for your account.

Confirm the Drive Is Back

After reconnecting, open the drive in Explorer or Finder and browse a folder with a few files. If an expected document is missing, right-click the folder and use NetDrive’s refresh option to force a fresh read of the directory. SharePoint changes made by colleagues in the last minutes may not have appeared yet.

NetDrive status view confirming a drive connected successfully

Wrap-up

Start with a re-authentication, verify the site address, test the same account in a browser, and only then involve your administrator. For the original setup walkthrough, see Mount SharePoint on Windows with NetDrive or the macOS version. If large sites feel sluggish rather than broken, Fix Slow SharePoint Directory Listing is the better read.

— Casey, NetDrive