Is anyone running a domain controller using the private IP addresses of 192.168.0.201 or 192.168.0.202? I have a domain controller that keeps trying to contact those IP addresses over ports 53, 389, 135, and others (DNS, LDAP, Windows). I'm no Windows networking expert, but I think that means that some AD domain controller is advertising itself with those IP addresses. Anyone have any insight? Thanks, Gene