Got this message when updating Sophos Home Edition for Mac: Could not contact Primary Server. URL Error: 3 July 2015. Mac OS X 10.10.4.
- Could Not Connect To The Primary Server Fatal Password Authentication Failed For User
- Could Not Connect To The Primary Server Postgresql
To check if you have a PDC Emulator do this lot: Start Run ntdsutil This brings up a lovely black screen with the ntdsutil prompt. Typing the following will tell you where all the FSMO roles are (including the PDC emulator): Roles Connections Connect to Server Quit Select Operation Target List Roles for Connected Server And you get a screen full of data telling where each of the roles are, the line you want looks something like this: PDC - CN=NTDS Settings,CN= Followed by the rest of the ADS path (which you don't need to worry about too much). Make sure that server exists though - the PDC Emulator is quite important. If the server is the right one then just type Quit until NTDSUtil exits. If not post again and it can be fixed. To check something is a Global Catalog open Active Directory Sites and Services and find your server in the tree.
Underneath it you should see NTDS Settings, right click on there and select properties and there will be a little tick box for Global Catalog. That's all you have to do to make somehting a GC.
Hope this helps so far. This bit: 0ADEL:8daa7e71-2851-4a59- ab91-b97 Doesn't look too helpful - did you have a domain controller fail at some point? Are any of the other FSMO roles displaying like that? To make sure your CCIDC is the PDC do: Start Run ntdsutil Roles Connections Connect to Server CCIDC Quit Then first try: Transfer PDC If that fails try: Seize PDC We're pretty safe doing this with the PDC without making absolutely sure that the server that holds it is never coming back. But most of the other roles seizing is a pretty serious step.
I get a lot of test failures when I run DCDIAG. When I run DCDIAG it also seems to still be holding that 0ADEL:8daa7e71-2851-4a59- ab91-b97 as the domain controller instead of the name. That no longer shows up during a check of the PDC in the NTdiagUtil. Here are some of the errors. Warning: CCIDC is not advertising as a time server. CCIDC failed test Advertising Starting test: KnowsOfRoleHolders Warning: CN=NTDS Settings 0ADEL:8daa7e71-28 51-4a59-ab 38b97,CN =CCIDC,CN=Servers,CN=Defa ult-First- Site-Name, CN=Sites,C N=Configur ation,DC=u s,DC =ccius,DC=com is the Rid Owner, but is deleted. CCIDC failed test KnowsOfRoleHolders Starting test: RidManager Warning: FSMO Role Owner is deleted.
Warning: attribute rIdSetReferences missing from CN=CCIDC,OU=Domain Co ntrollers,DC=us,DC=ccius,D C=com The last one says: Warning: DcGetDcName(PDCRequired) call failed, error 1355 A Primary Domain Controller Could not be located. The server holding the PDC role is down. I wish I could offer more help, but this problem still exists. I have made all of the changes suggested and the problem persists. I think they have had a machine that did not get demoted properly setup as the same name in the past (ccidc) I think that is may be where the 0ADEL:8daa7e71-2851-4a59- ab91-b97 characters are coming from.
Could Not Connect To The Primary Server Fatal Password Authentication Failed For User
I can't understand why handing all of this off to the Backup DC hasn't resolved it either though. The timer server is running. I checked that after reading the dcdiag.
Still shows as not running in the diag though. No problem Chris, I understand the Holiday, I appreciate the help you've given so far.
I read the document yesterday and it reported the correct DC and all of the correct machines, nothings seems wrong using that article, but from it I decided to do a few things. I transfered the PDC role to Jedi (the BDC) last week. I verified that DcDiag saw Jedi as the PDC. I then Demoted CCIDC (the current DC) to a stand a lone server and then shut it down.
Could Not Connect To The Primary Server Postgresql
I reran the commands in the document you suggested and it still reported correctly, CCIDC was now gone from the list and just Jedi showed up, authentication was fine, DCDiag still reported no PDC: (Starting test: FsmoCheck Warning: DcGetDcName(PDCREQUIRED) call failed, error 1355 A Primary Domain Controller could not be located. The server holding the PDC role is down.) I brought up a new Server (also Server 2003) and promoted it to a DC and then transfered PDC roles to it. The above document and Dcdiag verified the successful transfer but still reported that a the server holding the PDC role is down. So my question is this: If it is being seen as the PDC by DNS, Ntdsutil, most of the tests in DCdiag, where is it looking when it does the FsmoCheck.
If I know where that is, maybe I can change that. It seems to have the PDC role correct in most of the locations it should, but whatever the Trust uses and the FsmoCheck uses, it is still advertising an incorrect setting. Thanks again, Eric.