Accessing Windows Server from Mac: Complete Connection Guide

To access Windows Server from Mac, install Microsoft’s free Windows App and connect over Remote Desktop, then open the server’s file shares in Finder. A MacBook on the desk, a Windows server in the rack: it’s easier than people expect. Start with Microsoft’s free Windows App. It replaced Microsoft Remote Desktop for Mac in 2024.

Add the server’s name or IP, sign in with a Windows account, and the full server desktop opens over RDP.

For files, Finder connects to Windows shares over SMB. SSH, PowerShell and Windows Admin Center cover the rest. Plenty of admins manage Windows servers from Macs, and the toolkit has become much simpler than it used to be.

Below: what to use for each job, how to set it up, and the three errors Mac users hit most. A wrong username format, blocked ports and certificate warnings.

Five ways to access Windows Server from Mac

The two systems grew up on different foundations. They meet on shared protocols. RDP carries the screen, keyboard and mouse. SMB moves files. SSH carries text sessions. HTTPS carries web consoles.

Most people need one or two rows of that table. Designers opening the company file server need Finder. Admins need the desktop and the command line. Developers testing across environments usually want SSH.

Remote Desktop with Windows App

Microsoft renamed its Mac client to Windows App in September 2024. Had the old app? The App Store updated it in place and kept your saved connections.

It needs macOS 12 or later for Remote Desktop Services and remote PC connections. It runs natively on Apple silicon. And it’s free.

Two things have to be true on the server side. Remote Desktop is enabled, and port 3389 is reachable.

1. Switch Remote Desktop on in the server. Server Manager, Local Server, Remote Desktop. Our guide to enabling RDP on Windows Server covers the GUI, PowerShell and the firewall rule.
2. Install Windows App from the Mac App Store and open it.
3. Click + and choose Add PC.
4. In PC name, enter the IP address or the host name. A custom port goes after a colon.
5. Under Credentials, choose Add Credentials and enter the account.
6. Set a friendly name, the display options and any folder redirection. Click Add.
7. Double-click the new tile. Accept the certificate prompt the first time, and sign in.

For admin accounts you can leave the credentials on “Ask when required”. Then you type the password each time, and we’d do that on shared Macs.

Keys and display

Inside the session the Mac Cmd key acts as the Windows key by default. Fn + Ctrl + Option + Delete sends Ctrl+Alt+Del.

Display settings decide whether the session fills a Retina screen at full resolution, or scales. On slow links we’d lower the resolution and the colour depth.

Windows Server accepts two simultaneous administrative RDP sessions without extra licenses. More users at once need the Remote Desktop Session Host role plus RDS CALs. People who work on the server as a desktop need them too.

Copying files during a session

Turn on folder redirection in the PC’s settings in Windows App. The selected Mac folders then appear in File Explorer on the server. With clipboard redirection on, copy and paste works for text and files.

Other RDP clients for the Mac

• Royal TSX. A connection manager for admins with many servers. RDP, SSH, VNC and web sessions sit in one workspace. There’s a credential vault too. Its free license is limited to a small number of connections.
• Jump Desktop. Paid and Mac-native. It has its own Fluid Remote Desktop protocol next to RDP. Good on unstable networks, and smooth with multimedia.
• Parallels Client. Free, and built for environments that run Parallels RAS. Individual Windows apps open as separate Mac windows there, not as a full desktop.

For one or two servers, Windows App is usually enough. With a large estate, Royal TSX earns its place.

File shares in Finder

You don’t need a remote session to reach a document. Finder speaks SMB.

1. In Finder, choose Go, then Connect to Server. The shortcut is Cmd + K, if you prefer keys.
2. Type the address of the share and click Connect.
3. Choose Registered User and enter the name. A domain account or a local server account, both work.
4. Tick Remember this password in my keychain if you connect often.
5. Pick the share if the server lists several, and click OK.

The address takes one of these forms, by name or by IP:

smb://fileserver01/Projects
smb://192.168.1.100

The account needs both share permissions and NTFS permissions on the server. Once connected, the share appears under Locations in the Finder sidebar, like a local folder.

Making it stick

• Click the + in the Connect to Server window to add the address to Favorites.
• Drag the mounted share to the Finder sidebar.
• Add it under System Settings, General, Login Items, so it reconnects at login.

Finder slow on big folders of a Windows share? Large numbers of small files are typically the cause. The Mac writes hidden files next to them. The ones starting with a dot and an underscore, plus .DS_Store. We’d zip the folder on the server first, or copy it with rsync in Terminal.

Printers on a Windows print server

Printers shared by a Windows print server are added on the Mac side, in Printers & Scanners. No remote session needed.

1. System Settings, Printers & Scanners.
2. Add Printer, Scanner or Fax.
3. The Windows button at the top of the window.
4. Open the workgroup or domain, then the print server, then the shared printer. Sign in with your Windows account if the server asks.
5. Pick the matching driver in Use, then Add.

Printer missing from that list? Apple points at the printer software on the Mac. Some drivers can’t print to a shared Windows printer. An update from the printer maker, then. Full steps: Apple’s Mac User Guide, print to a printer connected to a Windows computer.

Domain accounts and Kerberos

A Mac that isn’t joined to the domain still signs in with the user’s domain credentials. The server checks them against a domain controller.

Kerberos single sign-on takes extra setup. Usually Apple’s Kerberos SSO extension, or a configured /etc/krb5.conf that lists your domain and its KDCs.

Access Windows Server from Mac on the command line

Three tools cover it. The built-in SSH client in Terminal, PowerShell 7 on the Mac, and a command to mount shares.

SSH

The server needs OpenSSH Server. It’s an optional feature on the 2019 and 2022 releases. On Windows Server 2025 it ships preinstalled.

Add it under Settings, System, Optional features. Or with PowerShell, and then start the sshd service:

Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

Then connect from Terminal on the Mac:

ssh administrator@winserver01

Domain accounts work in either of these forms:

ssh user@domain.com@winserver01
ssh 'DOMAIN\user'@winserver01

The default shell is the classic Command Prompt. Type powershell to switch. Or set PowerShell as the default shell in the registry on the server.

PowerShell 7 remoting

PowerShell 7 runs natively on macOS. Install it with Homebrew, or with the package from Microsoft:

brew install --cask powershell

Start it with pwsh. From a Mac, remoting over SSH is the reliable route:

Enter-PSSession -HostName winserver01 -UserName administrator

The server needs PowerShell 7 too, and a PowerShell subsystem line in its sshd_config.

Classic WinRM remoting with -ComputerName and Negotiate authentication isn’t dependable from macOS. So we’d stick to SSH. Windows-only modules such as ActiveDirectory run on the server side of the session. They work once you’re connected.

Mounting a share in Terminal

Make a folder for it, then mount:

mkdir ~/WindowsShare
mount_smbfs //username@servername/sharename ~/WindowsShare

The command prompts for the password. That’s safer than putting it in the URL. To unmount:

umount ~/WindowsShare

For copying files over SSH, scp and sftp work against the same OpenSSH Server.

Access Windows Server from Mac in a browser

Windows Admin Center is Microsoft’s free browser-based console for Windows Server. You install it on a gateway server. From the Mac you open it at https://gatewayname.

It manages a lot without RDP:

• Roles and updates.
• Storage and networking.
• Certificates.
• Hyper-V virtual machines.
• A PowerShell console.

Microsoft supports Edge and Chrome for it. Safari isn’t officially supported. A bookmark to the gateway is all the setup the Mac needs.

Other web consoles fill specific roles. The Exchange admin center for on-premises mail. The SharePoint admin center. The Microsoft 365 admin center for hybrid identity and licenses. None needs software on the Mac, and none cares whether it’s Apple silicon or Intel.

The trade-off: browser consoles can’t do everything. Low-level tasks, some legacy MMC snap-ins and third-party GUI tools still need a full RDP session. We’d keep Windows Admin Center for routine checks and open Windows App when a console needs the desktop.

Access Windows Server from Mac over the internet

Connect to the office network through a VPN first. Or publish RDP through a Remote Desktop Gateway on HTTPS, port 443. With the VPN up, Windows App, Finder and SSH work exactly as on the local network.

Don’t open port 3389 directly to the internet. That invites brute-force attacks.

Working from a café or a hotel? Bring the VPN up before anything else. Windows App and Finder simply time out without it, and the error message won’t mention the VPN.

macOS has a built-in VPN client. System Settings, VPN, Add VPN Configuration. It handles IKEv2, L2TP over IPSec and Cisco IPSec.

Windows Server’s own Routing and Remote Access service supports IKEv2, and the Mac client handles that well. Commercial firewalls typically need their vendor’s client. Cisco Secure Client, FortiClient, GlobalProtect and others all have Mac versions.

• Full tunnel. All Mac traffic goes through the VPN. Most secure, sometimes slower.
• Split tunnel. Only traffic for the company network goes through the VPN. Everything else uses the local internet.
• RD Gateway. In Windows App, add the gateway under the PC’s settings. RDP then travels inside HTTPS.

Changing the RDP port only hides the service from casual scans. It’s no replacement for a VPN, though it can help on internal networks. We wrote up how to change the RDP port in Windows Server.

When the Mac can’t connect

Five things cause nearly all of it. Test them in this order.

1. The server is unreachable. Network, VPN or DNS.
2. A firewall blocks the port.
3. The username is in the wrong format.
4. Remote Desktop or file sharing isn’t enabled on the server.
5. A certificate warning got dismissed.

Two commands in Terminal answer the first two questions:

ping servername
nc -vz servername 3389

The username format

A correct password that gets rejected is nearly always a format problem. Domain accounts take one of these two forms:

DOMAIN\username
username@domain.com

A local server account takes the plain account name.

The certificate warning

Windows Server uses a self-signed RDP certificate by default. That’s why the Mac warns you. Check the fingerprint against the server, then trust it in Keychain Access. Or install a certificate from your internal certificate authority, and the warning stops.

Ports to know

The macOS firewall rarely blocks outbound connections. So a timeout almost always points to the server, or to the network in between.

Apple silicon

Prefer native apps there. Windows App, Royal TSX, Jump Desktop and PowerShell 7 all run natively. Older tools under Rosetta 2 work, with the odd keyboard or display quirk.

Connecting from Windows and Linux clients as well? Our guide to accessing and connecting to Windows servers covers those.

Which Mac tool for which Windows Server task

• Updates and disk space. Windows Admin Center in a browser tab.
• A file from the project share. Finder, straight from the mounted share.
• Restarting a service. A quick SSH session from Terminal.
• A tool that needs the desktop. Windows App, for a few minutes.
• A document to print on the office printer. The shared printer added in Printers & Scanners.

The Mac never needs Windows installed for any of it. Each job uses its own protocol, and the server only needs the matching feature switched on.

Licenses for more sessions

Two admin sessions are free. More people at once need RDS CALs. We sell the Windows Server 2022 Remote Desktop Services 50 User CAL, genuine licenses for multi-user RDP, with delivery instant to email. Server licenses for every version are in our Windows Server category.

Windows Server and Mac versions this guide covers

The remote desktop steps follow the current Windows App for Mac from the Mac App Store. Microsoft documents its requirements on the Windows App getting started page.

Related guides

• WindowServer on Mac
• Remote Desktop on a Mac with the Windows App