A Windows server licensed through BinaryLane does not activate against Microsoft's activation servers. It activates against BinaryLane's own Key Management Service (KMS), and checks in automatically once a week. If Windows shows as not activated, or an activation error appears, first check that the server can reach the KMS servers.



TABLE OF CONTENTS



What the server needs to reach


The server needs inbound and outbound access to both KMS servers on TCP port 1688:


KMS1: 150.107.74.10

KMS2: 103.1.184.134

TCP port: 1688


The server keeps running without activation, but it must reach the KMS at least once every 180 days to keep a valid Windows licence. The full list of BinaryLane service addresses is in BinaryLane mPanel service IPs.


Test the connection


Open PowerShell as Administrator and run this for each KMS address:

Test-NetConnection 150.107.74.10 -Port 1688
Test-NetConnection 103.1.184.134 -Port 1688


If TcpTestSucceeded returns True for both, the network path to the KMS is working. If it returns False, work through the next section.


If the test fails


  • Cloud Firewall: Open the server in mPanel, go to Network > Firewall, and check that no rule blocks inbound or outbound traffic between your server and the two KMS addresses on TCP port 1688.
  • Windows Firewall: If you have changed Windows Defender Firewall inside the server, make sure it allows inbound and outbound connections between the server and the same addresses on TCP port 1688.
  • Port Blocking: This is not the cause. It only blocks outgoing TCP ports 22, 25 and 3389.
  • Servers in a VPC: Each Windows server must keep its public IP address and allow inbound and outbound TCP port 1688 traffic over the BinaryLane-provided public network path. KMS connections will not succeed through a customer-managed NAT gateway or router. If the server normally sends internet traffic through a customer-managed router, use Dedicated Interface (Split NIC) mode and route only the KMS addresses through the public interface. See Using KMS with a customer-managed VPC router and VPC Routing Tables and Default Route Troubleshooting.


After upgrading to Windows Server 2025


If you upgraded in place, follow the steps under Activate Windows Server 2025 Standard in Upgrading a Windows Server VPS to Windows Server 2025.


If you require assistance, feel free to submit a support ticket at our helpdesk here: Submit a ticket | BinaryLane