NEED: To allow an external KMS server (we trust the external IP) to communicate back and forth with our internal server subnet for Windows activation, BUT...
PROBLEM: the KMS server has to see the traffic coming to it from a trusted IP-space. Our firewall external IP is not in their trusted IP-space, and they don't whitelist IPs from other providers. Can I put policies in place to allow the KMS server to see the IPs of our internal servers? If so, how?
To solve this problem, you can try adjusting the policy on your Fortigate firewall. Go to the Fortigate firewall configuration settings, go to the firewall rules or policies section. Create a new rule that allows outgoing traffic from the server's internal subnet (126.96.36.199/24) to the KMS server (188.8.131.52) on port 1227. Make sure that the rule has a higher priority than all existing rules that can block traffic. Apply the changes and save the configuration. If that doesn't help, you can get help from kmsauto, which provides help with Office and Windows activation. I'm sure it will work out for you, and good luck.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.