-
Title
Network Ports needed for the KACE Systems Deployment Appliance (SDA) -
Description
This article contains a list of ports that the Systems Deployment Appliance (SDA) uses to communicate to clients that are a target for imaging, and also for processing driver feed updates and automatic updates (kbins ). -
Resolution
Ports needed for Communication between SDA and Clients:
80 -- HTTP (Also needed for SDA ---> RSA)
443-- HTTPS (if SSL
ie enabled, also needed for SDA --> RSA)139 -- SAMBA share
135 -- SAMBA share
445 -- SAMBA share (Direct-hosted SMB traffic without a network basic input/output system (NetBIOS): port 445 (TCP and UDP).
22 -- SSH Outbound only for Tether connections to Kace.
Please Note: That the tether connection uses only 'outbound' port 22, not inbound port 22, since the
kbox makes an outbound connection to the tether.kace.com server and uses the key, above, to accept a handshake and initiate the secure connection to Kace Technical Support.22 -- SSH for syncing to RSA and single sign-on
389 -- LDAP (if using LDAP authentication)
636 -- LDAPS (if using secure LDAP authentication)
67 -- DHCP
69 -- TFTP
4011 -- PXE
52231 -- Sync, upgrade and refresh RSA version
8108 -- Media Manager (Also needed for SDA--->RSA) Kloned Imaging Service
Note: These ports also cover communication between the Systems Deployment Appliance and a Remote Site Appliance.
Ensure routers/firewalls are
setup to allow DHCP to traverse them (BootP protocol) if clients span across them.The SDA does not have a built-in firewall. The SDA is not recommended for DMZ operations, only for operation on the internal network.
Ports and URL access required for SDA to download driver feed and
kbin updates:HTTP (80) and HTTPS (443) access to service.kace.com and servicecdn.kace.com