Probe changes all IP adresses to 0.0.0.0
Hello,
I noticed that for one probe the database was corrupted. Only 7 servers left out of the 80. Watched error logs and saw that since a specific time all IP adresses from servers are changing to 0.0.0.0
I talked to a Windows colleague, he stated that around that time our DNS server had servicepack 1 for Windows 2003 installed.
Does anyone had this experience or an explanation.
Thanks,
Ari van Asseldonk
See part of log nmsout63.txt:
[06 Apr 2007 22:12:28:122] TOPO: IpAddress for the objecthkv-svr-apps-24.cehave.local.chvlbbprobe has been changed from 100.7.4.93 to 0.0.0.0
[06 Apr 2007 22:12:28:137] TOPO: Invalid network address argument. 0.0.0.0.chvlbbprobe
[06 Apr 2007 22:12:28:137] TOPO: Cannot Update the IpAdddress for the object IF-hkv-svr-apps-24.cehave.local.chvlbbprobe since object with ipAddress 0.0.0.0 already exists
[06 Apr 2007 22:12:28:356] TOPO: Netmask for the objecthkv-svr-apps-24.cehave.local.chvlbbprobe has been changed from 255.255.0.0 to 255.255.255.0
[06 Apr 2007 22:12:28:356] TOPO: Invalid network address argument. 0.0.0.0.chvlbbprobe
[06 Apr 2007 22:12:28:387] TOPO: Cannot Update the IpAdddress for the object hkvvoesapbw3.cehave.local.chvlbbprobe since object with ipAddress 0.0.0.0 already exists
[06 Apr 2007 22:12:28:387] TOPO: Netmask for the objecthkvvoesapbw3.cehave.local.chvlbbprobe has been changed from 255.255.0.0 to 255.255.255.0
[06 Apr 2007 22:12:28:403] TOPO: Invalid network address argument. 100.7.4.0.chvlbbprobe
New to ADSelfService Plus?