TC-1927 Posted September 17, 2015 Posted September 17, 2015 (edited) Morning Hope someone can help with this, I can't see anything relevant on technet! We rebuilt our domain over the summer and, by and large, it's gone well barring this one issue. We have inconsistent delivery of group policies to our clients (mostly ICT suites), resulting in PCs having to be gpupdate/restarted 2-3 times in order for users to receive the correct desktop environment. The event viewer on the clients show the 'Processing of Group Policy failed because of a lack of connectivity to one or more domain controllers' error (1129). The screen grabs below are both from 'DC3 (s2012r2)' - which is the one showing as 'inaccessible' in GPIS. We have three DCs at the moment - one of which was our test DC (s2012) from before summer when the new domain was in testing phase. I've labelled this as DC2 on the first screen grab below - its status shows as one server always processing no matter when I refresh the status report. DC3 also seems problematic, and it showing as a 169.254 address. I have full connectivity to the DC and can ping it from anywhere else on the domain, and I can ping out to other servers and workstations from it. It has Hyper-V installed on it so the adapter shows as vEthernet, but this is the same configuration as our baseline DC (DC1 - s2012r2) which isn't showing any errors in GPIS. The second screen grab shows the list of network adapters. I'm guessing GPMC on DC3 is looking at the wrong adapter for replication? How can I change this? Bit of a frustrating issue - hope someone can shed some light on it! Screen grabs: Thanks in advance! Edited September 17, 2015 by TC-1927
Steve21 Posted September 17, 2015 Posted September 17, 2015 Do you not have your DCs set as static IPs? Or where are they getting that assignment from in the first place? Steve
TC-1927 Posted September 17, 2015 Author Posted September 17, 2015 Yep, all static IPv4 addresses. Other than the above, connectivity between all DCs seems normal and TCP/IP works properly.
TC-1927 Posted September 17, 2015 Author Posted September 17, 2015 Update - I found this article and disabled the second, unused NIC on DC3. It is now showing the correct IP in GPMC. However - the same error messages are present when I run 'detect now' under GPMC > status.
Davit2005 Posted September 17, 2015 Posted September 17, 2015 So you have installed Hyper-V on a Domain Controller?
TC-1927 Posted September 17, 2015 Author Posted September 17, 2015 So you have installed Hyper-V on a Domain Controller? Yes... should I not have?
localzuk Posted September 17, 2015 Posted September 17, 2015 Yes... should I not have? Hyper-V should be on a machine with no other functions. Domain Controllers definitely shouldn't be Hyper-V boxes, that's for sure. 1
TC-1927 Posted September 17, 2015 Author Posted September 17, 2015 Hyper-V should be on a machine with no other functions. Domain Controllers definitely shouldn't be Hyper-V boxes, that's for sure. Thanks both - further googling seems to indicate I have some VMs to move...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now