Table of Contents

Ports and firewall

This page lists every connection SharpDay Deploy makes, so you can open the right ports.

"PCs" means the PCs you are setting up, while they start from the network.

Connections to the server

From Port Used for Can you change it?
Console TCP 15156 The Console connection (encrypted) No
PE client TCP 15155 The PE client connection (encrypted) Yes, ClientPort in config.xml
PE client TCP 445 Reading drivers and Windows images from the Drivers and Operating Systems shares (SMB) No
PCs UDP 69 TFTP, to download boot files No
PCs UDP 4011 Proxy DHCP, which tells some PCs and iPXE where to get boot files No
PCs TCP 80 and 8080 HTTP, to download boot files, iPXE scripts and Linux install files No
PCs with Broadcom iPXE TCP 4433 Broadcom's own iPXE script request No
Linux installers TCP 445 Reading Linux install files from the SDDLinux share (SMB), if you use SMB No
Linux installers NFS Reading Linux install files over NFS, if you use NFS No
Linux installers UDP and TCP 514 Sending install logs to the server. Off unless you turn it on Yes, in the Console

The HTTP server is plain HTTP. There is no HTTPS boot.

If the HTTP ports are taken by another program, such as IIS, the server cannot send files over HTTP. Stop the other program or move it to another port.

Connections from the server

To Port Used for
The internet TCP 443 Licence checks, updates, driver catalogs and packs, Linux install files, iPXE files
The internet TCP 80 The Dell driver catalog
Deployment Node servers TCP 4333, or the port you set Running scripts on other servers
Domain controllers TCP 389, or 636 for LDAPS Signing in with Active Directory, Active Directory sync, domain joins
Your mail server TCP 587, 465 or 25 Email alerts

Internet addresses

The server uses these addresses. If you use a web proxy or an allow list, let them through. The server uses the Windows proxy settings.

What Address
Licence and updates sharpdaydeploylicense-btfhg3efetcjbqbc.uksouth-01.azurewebsites.net, and the download links it gives out
Dell drivers downloads.dell.com
HP drivers hpia.hpcloud.hp.com, ftp.hp.com
Lenovo drivers download.lenovo.com
Acer drivers global-download.acer.com
Microsoft Surface drivers download.microsoft.com
iPXE and wimboot github.com
Linux install files The Linux makers' own sites, such as releases.ubuntu.com and download.rockylinux.org
NixOS api.github.com and GitHub's download addresses for the netboot files, and channels.nixos.org for the ISO
Microsoft sign in login.microsoftonline.com
Google sign in accounts.google.com, oauth2.googleapis.com

Driver packs download from the links inside each maker's catalog, so the exact addresses can change.

PCs that install NixOS

Most PCs only talk to your server while they are set up. NixOS is different. Its installer builds the new system from NixOS's own servers, so PCs that install NixOS need internet access while they install.

Windows Firewall

Each time the server starts, it adds its own rules to Windows Firewall. They are named SharpDayDeployService - ... and cover:

  • Proxy DHCP (UDP 4011)
  • TFTP (UDP 69)
  • HTTP boot files (TCP 80, 8080 and 4433)
  • PE clients (TCP 15155, or your ClientPort)
  • Console (TCP 15156)
  • Linux installer logs, only while that is turned on
Important

These rules only cover the Domain and Private network types. If Windows has marked the server's network as Public, the rules do nothing. Change the network type, or add your own rules.

The server does not add a rule for file sharing (SMB, TCP 445). Make sure Windows Firewall allows File and Printer Sharing from the PCs you set up.

If there are other firewalls, switches or VLANs between the PCs and the server, you need to open these ports there too.