| Author | Messages | |
jeremyts
Posts:44
 | | 05/14/2012 2:59 PM |
| Hi All,
I've deployed a new 2008 R2 SP1 Single Domain environment. I've been doing a
lot of DFS health checks and found that when I run the dfsdiag /testreferral
command line (dfsdiag /testreferral /dfspath:\\corp.mydomain.com\data) it
completes successfully. However, the TestSites test has a warning for each
Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the
following: client1
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Success: The site associated with the following host name is consistent on
all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but get
the same results when I run it from the DC's themselves, and Win7 clients.
IPV6 is disabled on all DC's and the RD Host (client1).
Sites are services is correctly configured. There is nothing conflicting.
DNS is all good with no conflicting IPV6 information for the DC's.
But yet the "Host IP address" is not a valid IPV4 address, and therefore the
"Subnet-Site Mapping in AD" is invalid.
The server IP addresses are all in the range of 192.168.65.0/23, but I've
created a subnet of 192.168.0.0/16 and associated it to the
"Central-Server-Internal-DMZ" site. There shouldn't be anything wrong with
that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can't find where I may
have configured something incorrectly, or even if it's a dfsdiag quirk.
Premier Support say that it looks like a subnet binding issue, but I'm
loathed to log a call if it's a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
| DaemonRoot
Posts:178
| | 05/14/2012 3:13 PM |
| I suggest double checking IPv6 since ::1 is the same as 127.0.0.1
Cheers,
~danny
Sent from my Windows Phone
------------------------------
From: Jeremy Saunders
Sent: 5/14/2012 8:00
To: activedir@xxxxxxxxxxxxxxxx
Subject: [ActiveDir] Conflicting Site Associations
Hi All,
I’ve deployed a new 2008 R2 SP1 Single Domain environment. I’ve been doing
a lot of DFS health checks and found that when I run the dfsdiag
/testreferral command line (dfsdiag /testreferral /dfspath:\\
corp.mydomain.com\data) it completes successfully. However, the TestSites
test has a warning for each Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the
following: client1
Warning: *The server has IP addresses with conflicting site associations*
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Warning: *The server has IP addresses with conflicting site associations*
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Warning: *The server has IP addresses with conflicting site associations*
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Success: The site associated with the following host name is consistent on
all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but get
the same results when I run it from the DC’s themselves, and Win7 clients.
IPV6 is disabled on all DC’s and the RD Host (client1).
Sites are services is correctly configured. There is nothing conflicting.
DNS is all good with no conflicting IPV6 information for the DC’s.
But yet the “Host IP address” is not a valid IPV4 address, and therefore
the “Subnet-Site Mapping in AD” is invalid.
The server IP addresses are all in the range of 192.168.65.0/23, but I’ve
created a subnet of 192.168.0.0/16 and associated it to the
“Central-Server-Internal-DMZ” site. There shouldn’t be anything wrong with
that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can’t find where I
may have configured something incorrectly, or even if it’s a dfsdiag quirk.
Premier Support say that it looks like a subnet binding issue, but I’m
loathed to log a call if it’s a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
| jeremyts
Posts:44
| | 05/14/2012 3:28 PM |
| Yes, ::1 is the loopback for IPV6, which you cannot disable, without a hack,
which I don't want to do. The servers and client seem to be binding
localhost to ::1 instead of 127.0.0.1
I'm tempted to create a Subnet 0:0:0:0:0:0:0:1/128 and associate it with the
Central-Server-Internal-DMZ site.
This may address my issue in the main central site, but will mess up
associations in remote sites.
Instead of completely disabling IPV6 using the DisabledComponents, I could
try setting it to FF, which means Prefer IPV4 over IPV6. That may work for
the localhost too.
Has no one come across this before?
Cheers,
Jeremy.
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of daemon Root
Sent: Monday, 14 May 2012 10:09 PM
To: Jeremy Saunders; activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
I suggest double checking IPv6 since ::1 is the same as 127.0.0.1
Cheers,
~danny
Sent from my Windows Phone
_____
From: Jeremy Saunders
Sent: 5/14/2012 8:00
To: activedir@xxxxxxxxxxxxxxxx
Subject: [ActiveDir] Conflicting Site Associations
Hi All,
I've deployed a new 2008 R2 SP1 Single Domain environment. I've been doing a
lot of DFS health checks and found that when I run the dfsdiag /testreferral
command line (dfsdiag /testreferral /dfspath:\\corp.mydomain.com\data) it
completes successfully. However, the TestSites test has a warning for each
Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the
following: client1
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Success: The site associated with the following host name is consistent on
all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but get
the same results when I run it from the DC's themselves, and Win7 clients.
IPV6 is disabled on all DC's and the RD Host (client1).
Sites are services is correctly configured. There is nothing conflicting.
DNS is all good with no conflicting IPV6 information for the DC's.
But yet the "Host IP address" is not a valid IPV4 address, and therefore the
"Subnet-Site Mapping in AD" is invalid.
The server IP addresses are all in the range of 192.168.65.0/23, but I've
created a subnet of 192.168.0.0/16 and associated it to the
"Central-Server-Internal-DMZ" site. There shouldn't be anything wrong with
that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can't find where I may
have configured something incorrectly, or even if it's a dfsdiag quirk.
Premier Support say that it looks like a subnet binding issue, but I'm
loathed to log a call if it's a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
| bijubabuk
Posts:153
| | 05/14/2012 3:52 PM |
| May be I am completely wrong.. But isn't the message saying host ip
address "::1" doesn't have any site-subnet association/ mapping ?
Like
Host IP address Subnet-SiteMapping in AD
------------------------------------------------------------------------
-------
::1 No mapping exists
10.2.23.2 No mapping exists
Rgds
My working hours are from 11:00 to 19:30 IST (00:30 to 09:00 CST)
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of
jeremy@xxxxxxxxxxxxxxxx
Sent: Monday, May 14, 2012 7:56 PM
To: activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
Yes, ::1 is the loopback for IPV6, which you cannot disable, without a
hack, which I don't want to do. The servers and client seem to be
binding localhost to ::1 instead of 127.0.0.1
I'm tempted to create a Subnet 0:0:0:0:0:0:0:1/128 and associate it with
the Central-Server-Internal-DMZ site.
This may address my issue in the main central site, but will mess up
associations in remote sites.
Instead of completely disabling IPV6 using the DisabledComponents, I
could try setting it to FF, which means Prefer IPV4 over IPV6. That may
work for the localhost too.
Has no one come across this before?
Cheers,
Jeremy.
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of daemon Root
Sent: Monday, 14 May 2012 10:09 PM
To: Jeremy Saunders; activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
I suggest double checking IPv6 since ::1 is the same as 127.0.0.1
Cheers,
~danny
Sent from my Windows Phone
________________________________
From: Jeremy Saunders
Sent: 5/14/2012 8:00
To: activedir@xxxxxxxxxxxxxxxx
Subject: [ActiveDir] Conflicting Site Associations
Hi All,
I've deployed a new 2008 R2 SP1 Single Domain environment. I've been
doing a lot of DFS health checks and found that when I run the dfsdiag
/testreferral command line (dfsdiag /testreferral
/dfspath:\\corp.mydomain.com\data) it completes successfully. However,
the TestSites test has a warning for each Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the
following: client1
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
------------------------------------------------------------------------
-------
Host IP address Subnet-SiteMapping in AD
------------------------------------------------------------------------
-------
::1 No mapping exists
------------------------------------------------------------------------
-------
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
------------------------------------------------------------------------
-------
Host IP address Subnet-SiteMapping in AD
------------------------------------------------------------------------
-------
::1 No mapping exists
------------------------------------------------------------------------
-------
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
------------------------------------------------------------------------
-------
Host IP address Subnet-SiteMapping in AD
------------------------------------------------------------------------
-------
::1 No mapping exists
------------------------------------------------------------------------
-------
Success: The site associated with the following host name is consistent
on all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but
get the same results when I run it from the DC's themselves, and Win7
clients.
IPV6 is disabled on all DC's and the RD Host (client1).
Sites are services is correctly configured. There is nothing
conflicting.
DNS is all good with no conflicting IPV6 information for the DC's.
But yet the "Host IP address" is not a valid IPV4 address, and therefore
the "Subnet-Site Mapping in AD" is invalid.
The server IP addresses are all in the range of 192.168.65.0/23, but
I've created a subnet of 192.168.0.0/16 and associated it to the
"Central-Server-Internal-DMZ" site. There shouldn't be anything wrong
with that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can't find where I
may have configured something incorrectly, or even if it's a dfsdiag
quirk.
Premier Support say that it looks like a subnet binding issue, but I'm
loathed to log a call if it's a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
| michael1
Posts:455
| | 05/14/2012 3:54 PM |
| There is only one bit that controls that:
$IPv4PrefBit = 0x20
From: activedir-owner@xxxxxxxxxxxxxxxx [mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of Jeremy Saunders
Sent: Monday, May 14, 2012 10:26 AM
To: activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
Yes, ::1 is the loopback for IPV6, which you cannot disable, without a hack, which I don't want to do. The servers and client seem to be binding localhost to ::1 instead of 127.0.0.1
I'm tempted to create a Subnet 0:0:0:0:0:0:0:1/128 and associate it with the Central-Server-Internal-DMZ site.
This may address my issue in the main central site, but will mess up associations in remote sites.
Instead of completely disabling IPV6 using the DisabledComponents, I could try setting it to FF, which means Prefer IPV4 over IPV6. That may work for the localhost too.
Has no one come across this before?
Cheers,
Jeremy.
From: activedir-owner@xxxxxxxxxxxxxxxx<mailto:activedir-owner@xxxxxxxxxxxxxxxx> [mailto:activedir-owner@xxxxxxxxxxxxxxxx]<mailto:[mailto:activedir-owner@xxxxxxxxxxxxxxxx]> On Behalf Of daemon Root
Sent: Monday, 14 May 2012 10:09 PM
To: Jeremy Saunders; activedir@xxxxxxxxxxxxxxxx<mailto:activedir@xxxxxxxxxxxxxxxx>
Subject: RE: [ActiveDir] Conflicting Site Associations
I suggest double checking IPv6 since ::1 is the same as 127.0.0.1
Cheers,
~danny
Sent from my Windows Phone
________________________________
From: Jeremy Saunders
Sent: 5/14/2012 8:00
To: activedir@xxxxxxxxxxxxxxxx<mailto:activedir@xxxxxxxxxxxxxxxx>
Subject: [ActiveDir] Conflicting Site Associations
Hi All,
I've deployed a new 2008 R2 SP1 Single Domain environment. I've been doing a lot of DFS health checks and found that when I run the dfsdiag /testreferral command line (dfsdiag /testreferral /dfspath:\\corp.mydomain.com<http://corp.mydomain.com>\data) it completes successfully. However, the TestSites test has a warning for each Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the following: client1
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
-------------------------------------------------------------------------------
Host IP address Subnet-SiteMapping in AD
-------------------------------------------------------------------------------
::1 No mapping exists
-------------------------------------------------------------------------------
Success: The site associated with the following host name is consistent on all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but get the same results when I run it from the DC's themselves, and Win7 clients.
IPV6 is disabled on all DC's and the RD Host (client1).
Sites are services is correctly configured. There is nothing conflicting.
DNS is all good with no conflicting IPV6 information for the DC's.
But yet the "Host IP address" is not a valid IPV4 address, and therefore the "Subnet-Site Mapping in AD" is invalid.
The server IP addresses are all in the range of 192.168.65.0/23<http://192.168.65.0/23>, but I've created a subnet of 192.168.0.0/16<http://192.168.0.0/16> and associated it to the "Central-Server-Internal-DMZ" site. There shouldn't be anything wrong with that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can't find where I may have configured something incorrectly, or even if it's a dfsdiag quirk.
Premier Support say that it looks like a subnet binding issue, but I'm loathed to log a call if it's a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
| jeremyts
Posts:44
| | 05/14/2012 4:13 PM |
| Correct. But ip address ::1 is the loopback for IPV6.
If I ping localhost, it returns 127.0.0.1 on all hosts, so IPV4 is being
returned first instead of IPV6, which is exactly what I wanted and would
expect.
Just as a gut feeling I created a subnet of 0:0:0:0:0:0:0:1/128 (or ::1/128)
and associated that with the central site. And guess what? It worked like a
charm. No errors in the dfsdiag output!
Now that I've proven this to myself, I'll have a chat with Premier Support.
Unless anyone can enlighten me further, it's got to be down to the way
dfsdiag works, and is not necessarily a configuration issue on my behalf.
Cheers,
Jeremy.
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of
Biju_babu@xxxxxxxxxxxxxxxx
Sent: Monday, 14 May 2012 10:51 PM
To: activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
May be I am completely wrong.. But isn't the message saying host ip address
"::1" doesn't have any site-subnet association/ mapping ?
Like
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
10.2.23.2 No mapping exists
Rgds
My working hours are from 11:00 to 19:30 IST (00:30 to 09:00 CST)
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of
jeremy@xxxxxxxxxxxxxxxx
Sent: Monday, May 14, 2012 7:56 PM
To: activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
Yes, ::1 is the loopback for IPV6, which you cannot disable, without a hack,
which I don't want to do. The servers and client seem to be binding
localhost to ::1 instead of 127.0.0.1
I'm tempted to create a Subnet 0:0:0:0:0:0:0:1/128 and associate it with the
Central-Server-Internal-DMZ site.
This may address my issue in the main central site, but will mess up
associations in remote sites.
Instead of completely disabling IPV6 using the DisabledComponents, I could
try setting it to FF, which means Prefer IPV4 over IPV6. That may work for
the localhost too.
Has no one come across this before?
Cheers,
Jeremy.
From: activedir-owner@xxxxxxxxxxxxxxxx
[mailto:activedir-owner@xxxxxxxxxxxxxxxx] On Behalf Of daemon Root
Sent: Monday, 14 May 2012 10:09 PM
To: Jeremy Saunders; activedir@xxxxxxxxxxxxxxxx
Subject: RE: [ActiveDir] Conflicting Site Associations
I suggest double checking IPv6 since ::1 is the same as 127.0.0.1
Cheers,
~danny
Sent from my Windows Phone
_____
From: Jeremy Saunders
Sent: 5/14/2012 8:00
To: activedir@xxxxxxxxxxxxxxxx
Subject: [ActiveDir] Conflicting Site Associations
Hi All,
I've deployed a new 2008 R2 SP1 Single Domain environment. I've been doing a
lot of DFS health checks and found that when I run the dfsdiag /testreferral
command line (dfsdiag /testreferral /dfspath:\\corp.mydomain.com\data) it
completes successfully. However, the TestSites test has a warning for each
Domain Controller.
-----------------------------------------------
Starting TestSites...
Validating site associations...
Validating the site associations on every domain controller of the
following: client1
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC1
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC2
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Warning: The server has IP addresses with conflicting site associations
Host name: client1
Site: Central-Server-Internal-DMZ
Domain controller: DC3
----------------------------------------------------------------------------
---
Host IP address Subnet-SiteMapping in AD
----------------------------------------------------------------------------
---
::1 No mapping exists
----------------------------------------------------------------------------
---
Success: The site associated with the following host name is consistent on
all accessible
domain controllers: client1
Finished TestSites.
-----------------------------------------------
I ran this test from client1, which is a Windows 2008 R2 RD Host, but get
the same results when I run it from the DC's themselves, and Win7 clients.
IPV6 is disabled on all DC's and the RD Host (client1).
Sites are services is correctly configured. There is nothing conflicting.
DNS is all good with no conflicting IPV6 information for the DC's.
But yet the "Host IP address" is not a valid IPV4 address, and therefore the
"Subnet-Site Mapping in AD" is invalid.
The server IP addresses are all in the range of 192.168.65.0/23, but I've
created a subnet of 192.168.0.0/16 and associated it to the
"Central-Server-Internal-DMZ" site. There shouldn't be anything wrong with
that, and all other tests show valid and correct site association.
This is bizarre and has been bugging me for days as I can't find where I may
have configured something incorrectly, or even if it's a dfsdiag quirk.
Premier Support say that it looks like a subnet binding issue, but I'm
loathed to log a call if it's a silly configuration error on my behalf.
Any ideas?
Cheers,
Jeremy.
| | | |
|
|