w32tm /config /syncfromflags:manual /manualpeerlist:192.168.31.174,0x8 /reliable:yes /updatew32tm /config /updatew32tm /resync
w32tm /config /syncfromflags:manual /manualpeerlist:192.168.31.146,0x8 /reliable:yes /updatew32tm /config /updatew32tm /resync
I cannot understand your network scheme; the names you provided, Port 2 - Firewall Management, Port 3 - Server Gateway - I do not see them in the screenshot you have provided?You have two interfaces which has an unique IP adresse on the same subnet?
I might have misunderstood something here.But, do you have three interfaces- all within the same net?YesOr; what is the subnets of these interfaces? Can you post the CIDR notation of each?vFirewall_Network - 192.168.31.128 /27 | 255.255.255.224 | 192.168.31.129 - 192.168.31.158vFirewallP - 192.168.31.146 /27vServer_Network - 192.168.31.160 /27 | 255.255.255.224 | 192.168.31.161 - 192.168.31.190And what is the IP/Subnet of the client (Server?) from where you execute your PowerShell command? .. Is the server on the same subnet as the Gateway?vServerP - 192.168.31.162 /27Yes the server is on the same subnet as the gateway and within the assignable IP range.What does Command prompt: w32tm /query /peers give you?There is no result as such of success or failure, if successful within some seconds the time syncs, if it fails the time remains the same. So when the peers address is of the vFirewallP interface (192.168.31.146) the time syncs, when the peers address is of vServer Gateway (192.168.31.174) the time does not sync at all and remains the sameYou can ping all OPNsense interface addresses from your "Server"?Yes