On Wed, Apr 15, 2015 at 11:31 AM, Michael Tavares <[email protected]>
wrote:

>  What happens if you edit the host file and remove the entry for ::1 on
> the server that is having the issue?
>


The hosts file has that line commented out already ...

I suppose I can enable it ...



>
>
> Mike
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Michael Leone
> *Sent:* Wednesday, April 15, 2015 10:57 AM
> *To:* [email protected]
> *Subject:* [NTSysADM] DFSDIAG warnings - IP with conflicting site
> associations
>
>
>
> I am about to demote another Win2008 R2 DC, so I ran "dfsdiag /testdcs"
> first. And on this server, it starts to validate the site associations of
> this server. And it says:
>
>
>
> The server has IP address with conflicting site associations.
>
>
>
> Host IP address                         Subnet-SiteMapping in AD
>
> ::1                                                No mapping exists
>
>
>
>
>
> Now, isn't ::1 the IPv6 equivalent of 127.0.0.1? I'm not using IPv6, and
> in fact it is unchecked in the network connection properties. And I don't
> see this error when I do that command on the 2 other servers (which also
> don't have IPv6).
>
>
>
> I'm guessing that it thinks I need a subnet in Sites and Services, but I
> don't know why (or where) it's finding that ::1 at all ... Nor why the 2
> other servers in this same site are *not* showing this error, even when
> querying the problematical server. There's just the 1 NIC, and I am not
> using a VPN (which might be assigning an IP).
>
>
>
> Web searches have been less than fruitful ... Event log of this server
> shows nothing about DFS warnings or errors.
>
>
>
> I don't want to create an IPv6 subnet, as I don't plan on using IPv6. Is
> it safe to just ignore this? (most especially since I am about to demote
> it, and since there are no other DFS namespaces besides Domain System
> Volume, and the 2 other servers don't show the error)
>
>
>
> ADDENDUM: now DFSDIAG /testreferral is telling me there are stale entries
> and to restart the service on all DCs. Yet that same command does *not*
> show stale entries on the other DCs in the domain ...
>
>
>
> <SIGH>
>
>
>
> Oh, well. It's still just the test domain, I will restart all 3 DCs, and
> do something else for a few minutes while they come back up and hopefully
> sync ...
>
>
>
>
>
>
>

Reply via email to