Overview
Remote file-access problems can come from VPN, SharePoint/OneDrive identity, permissions, synchronization, network shares, or an unavailable source system. First identify where the company files actually live.
Why this happens
Different storage systems use different access paths. SharePoint and OneDrive usually require cloud identity, while traditional network shares may require VPN and domain permissions.
Before you begin
- Identify whether files are in SharePoint, OneDrive, Google Drive, or a network share.
- Record the exact file/folder path.
- Confirm the correct work account.
- Do not grant broad permissions or create personal copies.
Click-by-click troubleshooting
Step 1: Identify the authoritative storage location
Action: Confirm the exact company repository and path from approved documentation or a known-good link.
Why this matters: Troubleshooting a cloud library is different from troubleshooting a network share.
What to look for: Determine whether access uses a browser, sync client, mapped drive, or VPN.
Expected result: You should know the authoritative source before changing anything.
Step 2: Test browser access for cloud files
Action: For SharePoint, OneDrive, or Google Drive, open a private browser window and sign in with the work account, then open the authoritative location.
Why this matters: Browser testing bypasses local sync-client problems.
What to look for: Look for access denied, file missing, wrong account, or successful access.
Expected result: If browser access works, the cloud permission is likely valid and the local client becomes the next layer.
Step 3: Connect VPN for network shares if required
Action: Connect the approved VPN, then open the documented UNC path or mapped drive.
Why this matters: Traditional internal shares are often unavailable from the public internet.
What to look for: Distinguish path not found from Access denied.
Expected result: The network share should be reachable over the approved secure path.
Step 4: Verify the work identity
Action: Confirm the browser, sync client, or Windows session is using the intended work account.
Why this matters: Cached personal or old accounts commonly cause remote access failures.
What to look for: Look for the wrong tenant, personal account, or guest identity.
Expected result: Access should be tested with the identity that actually holds permission.
Step 5: Compare another approved user or device
Action: If possible, verify whether another authorized user can open the same file location.
Why this matters: This distinguishes service-wide problems from one user's permissions or device state.
What to look for: Compare results without changing permissions.
Expected result: The comparison should isolate user-specific versus repository-wide failure.
Step 6: Check sync status only after browser access is proven
Action: If browser access works but File Explorer does not, select the OneDrive cloud icon > Help & Settings > Settings and review the signed-in account and sync status. For Google Drive for desktop, open the approved Drive client and review its sync status.
Why this matters: Local sync should not be repaired until server-side access is known to be healthy.
What to look for: Look for signed-out, paused, red-X, or sync-error states.
Expected result: You should know whether the remaining problem is local synchronization.
What to look for
- Browser access denied: permission/identity issue.
- Browser works, sync fails: local client issue.
- Network share unreachable off VPN: expected secure-path dependency.
- Another user works: user-specific access issue.
When to stop
When to contact IT
Contact J3 Systems Group if the authoritative location is unavailable, permissions are denied with the correct account, VPN connects but shares remain unreachable, or sync errors persist after browser access is proven. Include article code KB-15.011 and the exact repository/path.
Need help with this issue?
J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.
Contact J3 Systems GroupAuthoritative references
Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.