Windows is notifying me that there is an IP conflict with the address 192.168.1.2 (the IP of my domain controller), with a device with hardware address corresponding to my Linksys WRVS4400N v1.1 wireless-n router.
This device's LAN IP is 192.168.1.1. No problems there.
I can't find any trace of 192.168.1.2 anywhere in its GUI config, except for port forwarding rules. This is just a small-business level wireless router; not a heavy Cisco device with the option to assign multiple interface addresses.
However, that's just what it seems to be doing: when I dump its config and look ctrl+f for the IP in question, I find this line:
lan_ifnames=etho0 wl0 wl_chip_ip=192.168.1.2 wlan_mgr_enable=1 wl0_ssid-linksys-n
Of course, my real SSID isn't "linksys-n", but that's what the config file shows.
So without changing the IP of my domain controller, is there a way to change this obscured "wl_chip_ip" address?
Viewing the arp table for the network shows that the router is squatting on both IPs:
Internet Address Physical Address 192.168.1.1 00-1c-10-f6-8d-2c 192.168.1.2 00-1c-10-f6-8d-2d
But pings are replied to by the server (determined by turning windows firewall on/off).
The only impact of this issue is that Windows keeps logging IP conflicts; nothing else seems to be impacted.