Dear Rajasekar Kannan,
Thank you for asking the forum community. The HKLM\SOFTWARE\Microsoft\Rpc\Internet setting controls the dynamic RPC port pool for multiple services. Restricting that pool to a single port can prevent Netlogon and other RPC services from registering their endpoints, which fits the behavior you observed. Please restore the previous RPC configuration using your saved settings or registry backup before trying another change. Microsoft’s RPC port guidance.
If this server is a domain controller and you need a fixed port for Netlogon RPC, Microsoft documents a separate setting:
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters → DCTcpipPort (REG_DWORD)
You can set it to 46769 only after confirming that the port is available and permitted through the relevant firewalls. Restart the Netlogon service for the setting to take effect. If you also need to restrict Active Directory RPC, that uses a different setting, TCP/IP Port, under HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters. Give NTDS a different available port; using the same port for both can cause a conflict. Microsoft also notes that other ports may still be required for domain operations. Restrict Active Directory RPC traffic to a specific port.
Because these changes can affect logons and domain connectivity, back up the registry and test during a maintenance window. Could you confirm whether the Windows Server 2016 machine is a domain controller or member server, and which service or connection your firewall requires on port 46769? That determines whether the Netlogon setting applies or whether a different service needs to be configured.
If this helped, I’d appreciate a Like so others can find the answer more easily.