Thanks for the prompt reply.
I thought about that, but the thing is is that the change occurs while the system is running, not after a restart.
I just noticed what might be an association between the gateway address getting changed and AD replication. The connection to the remote server was working fine all yesterday evening and night. This morning, I added a user on the Main office server. Just a few minutes after that, couldn't ping the remote office server. When I checked it, sure enough the GW address had changed from 192.168.1.1 to 192.168.0.1. Any idea why AD replication would cause this to happen?
Main Topics
Browse All Topics





by: LilshooterPosted on 2008-01-17 at 18:40:31ID: 20687489
How about using the persistent setting to see if the gateway remains there?
route add 192.168.1.0 mask 255.255.255.0 192.168.1.1 -p
Cheers,
Shooter