TCP/IP

TCP/IP is the foundational suite of communication protocols used to interconnect network devices. In MDM environments, TCP/IP is the foundation of all network communication. Devices use TCP/IP to communicate with MDM servers (HTTPS over TCP) and receive push notifications (APNs over TCP).

What to Know

TCP/IP is the universal language of internet communication, enabling devices to send and receive data across networks of any size or complexity. Every MDM operation — enrollment, check-ins, app downloads, profile installations — relies on TCP/IP connectivity. TCP provides reliable, ordered delivery of data packets, ensuring MDM commands arrive intact and in sequence. IP addressing and routing enable devices to locate and reach MDM servers across complex enterprise networks or the public internet. Without functioning TCP/IP connectivity, devices are isolated and cannot be managed remotely.

Network troubleshooting for MDM issues frequently involves diagnosing TCP/IP problems: incorrect IP addressing (DHCP failures), routing issues (devices on wrong VLANs or subnets), firewall rules blocking required ports, or DNS failures preventing hostname resolution. Understanding TCP/IP fundamentals helps IT diagnose whether enrollment failures stem from device issues, network infrastructure problems, or MDM server configuration errors. TCP/IP monitoring and diagnostics (ping, traceroute, packet capture) are essential tools for troubleshooting device connectivity issues.

Common Scenarios

Enterprise IT: Corporate networks use DHCP to assign IP addresses automatically, but misconfigurations can prevent devices from obtaining addresses or reaching critical services. Firewall rules must permit TCP traffic on specific ports (443 for HTTPS MDM communication, 2195/2196/5223 for APNs). Network segmentation via VLANs requires proper routing configuration to allow managed devices to reach MDM servers and external Apple services. IT troubleshooting device check-in failures should verify basic TCP/IP connectivity (can device ping gateway, reach DNS, access internet) before investigating MDM-specific issues.

MSP: MSPs troubleshooting client device issues must understand client network topology, IP addressing schemes, and firewall configurations that affect TCP/IP connectivity. Client network changes (new firewalls, VLAN reconfigurations, ISP changes) can break previously-functioning MDM operations by blocking required TCP ports or preventing routing to MDM servers. MSPs should document client network requirements for MDM traffic and verify TCP/IP connectivity during initial deployment and after any network infrastructure changes.

Education: School networks with aggressive security policies may inadvertently block TCP ports required for MDM communication. Student devices roaming between buildings or using guest Wi-Fi may experience IP addressing issues if DHCP scopes are exhausted or misconfigured. Education IT should ensure TCP/IP connectivity for managed devices across all campus network segments, including wireless networks, wired classrooms, and administrative areas. Port restrictions on student VLANs must permit MDM traffic even while blocking other services for security reasons.

In Addigy

Addigy’s MDM communication relies on standard TCP/IP protocols, with devices connecting to Addigy servers via HTTPS (TCP port 443) and receiving push notifications via APNs (TCP ports 2195, 2196, 5223). Addigy’s network requirements documentation specifies which hosts and ports must be accessible for full functionality. When troubleshooting device connectivity issues, Addigy support helps admins verify TCP/IP connectivity from device networks to Addigy and Apple services.

Organizations should ensure network infrastructure permits TCP/IP traffic to Addigy endpoints and Apple services, with firewall rules allowing outbound connections on required ports. Addigy’s cloud architecture eliminates the need for organizations to configure inbound firewall rules or complex routing — devices initiate outbound TCP connections to Addigy, simplifying network configuration. Addigy’s diagnostics can help identify TCP/IP connectivity issues by testing reachability of required endpoints from problem devices.