“The server could not be reached” – Issues related to network or DNS preventing SharePoint from authenticating a user.

Loading

“The Server Could Not Be Reached” – Troubleshooting SharePoint Network & DNS Issues

The “The server could not be reached” error occurs in SharePoint Online or SharePoint On-Premises when there are network connectivity issues, incorrect DNS configurations, or firewall restrictions preventing users from authenticating or accessing SharePoint. This guide provides a detailed step-by-step troubleshooting process to resolve the issue.


Step 1: Verify Your Internet Connection

Before proceeding with advanced troubleshooting, confirm that your internet connection is stable.

How to check your internet connection:

  1. Open a browser and try visiting another website (e.g., https://www.bing.com).
  2. If the site does not load, your internet connection may be down.
  3. Restart your router/modem and try again.
  4. If using a VPN, disconnect and check if the issue persists.
  5. If on a corporate network, contact IT to check if SharePoint is accessible.

Step 2: Check SharePoint Service Status (For SharePoint Online Users)

Microsoft SharePoint Online may experience temporary outages.

How to check Microsoft 365 service status:

  1. Visit the Microsoft 365 Service Status page.
  2. Look for any outages affecting SharePoint Online.
  3. If there is an outage, wait for Microsoft to resolve it.

Step 3: Verify the SharePoint URL

Ensure you are entering the correct SharePoint URL.

How to check your SharePoint URL:

  • SharePoint Online:
    • Correct format: https://yourcompany.sharepoint.com
  • SharePoint On-Premises:
    • Contact your IT department for the correct internal server URL.

If the URL is incorrect, try the correct URL and attempt to connect again.


Step 4: Restart Your Device

A simple restart can refresh network settings.

How to restart:

  1. Save any open work.
  2. Restart your computer or mobile device.
  3. After rebooting, try accessing SharePoint again.

Step 5: Try a Different Browser or Incognito Mode

Sometimes, browser-specific issues can prevent access.

How to test with Incognito Mode:

  1. Open a private/incognito window:
    • Chrome: Ctrl + Shift + N
    • Edge: Ctrl + Shift + N
    • Firefox: Ctrl + Shift + P
  2. Try accessing SharePoint.

If it works in Incognito Mode, clear your browser cache and cookies.

How to clear browser cache and cookies:

  1. Open your browser and press Ctrl + Shift + Delete.
  2. Select Cookies and Cached Data.
  3. Click Clear Data.
  4. Restart the browser and try again.

Step 6: Check Network Configuration & DNS Settings

A DNS issue can prevent your system from resolving SharePoint’s address.

How to check if DNS is working (Windows Users):

  1. Open Command Prompt (Press Win + R, type cmd, and hit Enter).
  2. Type the following command: nslookup yourcompany.sharepoint.com
  3. If you receive a DNS error, your system may have incorrect DNS settings.

How to switch to Google DNS (Windows Users):

  1. Open Control Panel → Network and Sharing Center.
  2. Click Change adapter settings.
  3. Right-click your active network and select Properties.
  4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  5. Select Use the following DNS addresses, then enter:
    • Preferred DNS Server: 8.8.8.8
    • Alternate DNS Server: 8.8.4.4
  6. Click OK, restart your PC, and try accessing SharePoint.

Step 7: Check If SharePoint is Blocked by Firewall or Antivirus

Security software may block SharePoint connections.

How to check and temporarily disable firewall/antivirus:

  1. Open Windows Security (or your antivirus software).
  2. Go to Firewall & Network Protection.
  3. Temporarily turn off firewall protection.
  4. Try accessing SharePoint.
  5. If it works, whitelist SharePoint in your firewall settings.

Important: Re-enable your firewall after testing.


Step 8: Check VPN and Proxy Settings

If your organization requires a VPN to access SharePoint, ensure it is connected.

How to check VPN settings:

  1. Open your VPN client and make sure it is connected.
  2. If connected but still unable to reach SharePoint, disconnect and try without VPN.

How to check Proxy settings (Windows Users):

  1. Open Settings → Network & Internet → Proxy.
  2. Disable any manual proxy settings.
  3. Restart your browser and try again.

Step 9: Run Network Troubleshooting Commands (For Advanced Users)

Running network diagnostic commands can help identify the issue.

Command 1: Ping SharePoint

  1. Open Command Prompt.
  2. Type: ping yourcompany.sharepoint.com
  3. If you get “Request Timed Out”, there may be a network issue.

Command 2: Traceroute to SharePoint

  1. In Command Prompt, type: tracert yourcompany.sharepoint.com
  2. If it fails, a network node may be blocking access.

Command 3: Flush DNS Cache

  1. Open Command Prompt as Administrator.
  2. Run the command: ipconfig /flushdns
  3. Restart your browser and try again.

Step 10: Check Corporate Network Restrictions (For IT Admins)

If you are on a corporate network, your IT department may have security policies blocking SharePoint.

How to check with IT:

  1. Ask IT if SharePoint is whitelisted in the company’s firewall.
  2. Request IT to check network logs for blocked requests.
  3. If needed, ask IT to open port 443 (HTTPS) for SharePoint traffic.

Step 11: Check SharePoint Server Health (For On-Premises Admins)

If using SharePoint On-Premises, the server might be down.

How to check SharePoint server status (Admins only):

  1. Log in to the SharePoint server.
  2. Open SharePoint Central Administration.
  3. Navigate to System Settings → Manage Servers in Farm.
  4. Check if any server shows Offline or Unresponsive.
  5. Restart SharePoint services using PowerShell: iisreset net stop SPTimerV4 net start SPTimerV4

Step 12: Contact IT Support or Microsoft Support

If none of the steps resolve the issue, contact your IT department or Microsoft Support.

Information to provide IT support:

  • Your username/email.
  • The exact error message.
  • A screenshot of the error.
  • The troubleshooting steps you’ve already tried.
  • If possible, the output of network diagnostic commands (ping, tracert, nslookup).

Leave a Reply

Your email address will not be published. Required fields are marked *