Has anyone out there seen this problem. We are currently installing NCC between two locations. Once the NCC does a force sync it sees the local Symposium server (Site 1) fine, however, the far end Symposium server (Site 2)basically will not communicate with the NCC after the force synch has completed. We know a persistent route is built in each Symposium server by the NCC, but the persistent route built in Site 2 shows a gateway of the servers IP address, not the "gateway" IP address after every force synch. We can delete the persistent route and can ping the NCC, however, when we try again, the gateway is built with the servers IP address not the "real gateway IP address".