Mac can't connect to a Windows server: "There was a problem connecting to the server"

Published Sources checked By helps.wiki editorial team

When a Mac can't open a Windows file share, the cause is often a sign-in or protocol mismatch, not a dead network. Check the basics, connect with an smb:// address using the server's name instead of its IP, and ask the administrator to confirm the share isn't SMB1-only.

Applies to:macOSApple's own article covers Mojave and earlier; newer versions are not covered by the sourcesWindows ServerServers updated June 2019 or later (Apple article)
On this page

What it means

"Windows server error on Mac" is not one specific error. The most common version is this: in Finder you choose Go > Connect to Server, type the address of a Windows file share, and macOS answers "There was a problem connecting to the server" and asks you to check the server name or IP address.

Despite the wording, the network is often fine. The Mac and the server may not agree on how to sign in, or the share may be offered only over an old protocol, so the fixes below are about sign-in method and protocol rather than cables or Wi-Fi.

Scope matters here. The only Apple article that describes this exact alert is archived and covers macOS Mojave and earlier. It deals with NTLM sign-in to CIFS/SMB1 shares on Windows servers updated in June 2019 or later. SMB1 is generally switched off on current Windows Server, so that specific cause probably does not apply to a current macOS and a current server. I found no official Apple or Microsoft page that covers newer macOS versions against Windows Server, so treat the steps below as sensible first checks, not a confirmed diagnosis.

Microsoft's SMB signing page describes Windows clients connecting to third-party SMB servers, which is the reverse of this situation. It does not cover Mac clients, so it is not used here to explain Mac failures.

Symptoms and causes

You are likely dealing with this problem if:

  • The alert "There was a problem connecting to the server" appears even though the username and password are correct.
  • Finder asks you to check the server name or IP address, but the server is switched on and reachable.

The usual causes, most common first:

NTLM against an SMB1/CIFS share on a patched server (older macOS)
Apple documents that a Mac running Mojave or earlier can fail to use NTLM to connect to a CIFS/SMB1 share on a Windows server that received updates from 11 June 2019 or later. This is version-limited and probably does not apply to current macOS or current Windows Server.
Connecting by IP address
An IP address prevents Kerberos and forces NTLM. Microsoft also advises against connecting to shares by IP.
File sharing off or wrong sign-in details
Apple says the Windows computer needs file sharing turned on, a valid login or guest access, and sometimes the right workgroup name.
Share offered only over SMB1
If the share is available only over SMB1, the problem Apple describes can occur. This is for the administrator to check.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Check the basics and reconnect with smb://

Easy

Wrong login details, file sharing switched off, or a wrong workgroup name cause many of these failures. Apple also documents connecting with an smb:// address as the way to use SMB2/SMB3 (Mojave and earlier).

  1. On the Windows server, confirm file sharing is turned on and that your account may access the share.
  2. Confirm the username, password and, if needed, the workgroup or domain name.
  3. On the Mac, open Finder and choose Go > Connect to Server.
  4. Enter the address in this form, then click Connect.
    Text
    smb://servername/share
  5. Choose Registered User and sign in. Choose Guest only if the server allows guest access.

2.Use the server's DNS name, not its IP address

Easy

A hostname lets Kerberos be used. An IP address forces NTLM, which is the method Apple documents as failing on older macOS.

  1. In Go > Connect to Server, replace the IP address with the server's hostname.
    Text
    smb://servername/share
  2. If it still fails, ask your administrator whether Kerberos is set up for Macs. Apple points to its deployment guide for that, which I did not read, so I can't give exact steps.

3.Ask the administrator to check that the share is not SMB1-only

Advanced

Apple's documented failure involves CIFS/SMB1 shares. If the share is reachable only over SMB1, a Mac may not connect.

  1. On the Windows server, open PowerShell as administrator and check whether the server offers SMB2/SMB3. Read-only command, nothing is changed.
    PowerShellrun as administrator
    Get-SmbServerConfiguration | FL EnableSMB2Protocol
  2. If the share turns out to be SMB1-only, ask the administrator to move it to SMB2/SMB3 rather than re-enabling SMB1 for the Mac.

4.Review SMB signing on the server

AdvancedChanges settings

Apple lists enabling SMB signing on the server as a fix for the NTLM problem on Mojave and earlier. This is for the server administrator and is not confirmed for current macOS.

Before you start: Changing server security settings affects every client. On an SMB1 server, requiring signing can reduce performance. Get your administrator's approval first.

  1. On the Windows server, open PowerShell as administrator and check the current setting. True means signing is required.
    PowerShellrun as administrator
    Get-SmbServerConfiguration | FL RequireSecuritySignature
  2. To require signing, run this command.
    PowerShellrun as administrator
    Set-SmbServerConfiguration -RequireSecuritySignature $true
  3. Alternatively, use Windows Admin Center (File Shares (SMB server) > SMB signing).
  4. Try connecting from the Mac again.

Check that it worked

  • Finder opens the share after Go > Connect to Server with no alert.
  • The share appears in the Finder sidebar under Locations and you can open a file.

If it still fails

  • Restart the Mac and retry. Community reports say this sometimes helps temporarily, but it isn't an official fix.
  • Don't turn SMB signing off or re-enable SMB1 as a general fix. Microsoft says it doesn't recommend disabling signing as a workaround for third-party servers.
  • Ask your server administrator to check the server's event logs and sharing settings, or contact Apple Support or Microsoft support.
  • If a Windows PC (not a Mac) shows signing or guest-access errors such as 0xc000a000 when reaching a non-Windows share, that is a different case. Microsoft covers it on its SMB signing page.

Sources

  1. If your Mac can't use NTLM to connect to a Windows serverOfficial · Apple
  2. Connect to a Windows computer or file server (Mac User Guide)Official · Apple
  3. Control SMB signing behaviorOfficial · Microsoft Learn

Browse