Need to meet organization standards and need to set 15 digit passwords for all servers

Hi, Richard.

I'm not sure where to post question so i'll ask it here and you can tell me if you want me to ask it somewhere else. I have a domain named, lets say, foo.bar. Using Multi-valued Distinguished Name With Security Principal Editor i want to add another member to some object. When I select user or user group, lets say MyGroup, from that domain (after clicking 'Add Windows Account...' button), In the members window I see MyGroup@FOO as if FOO is domain. I'm not sure why I see selected group in that format and if it is expected or not. I expected MyGroup@foo.bar. Do you know what has happened? Thank you in advance.

Kind regards,

Hey Everyone,

I'll be assisting an entrepreneur to build out a Managed Service Provider. We plan on assisting different clients(domains). What are the possible ways to manage different domains from one domain without needing to have a trust relationship?

Hi,

I have two domain controller in my network. Any of these domain controllers every 5 minutes encountered the following error:

Security policy cannot be propagated. Cannot access the template. Error code = 3

I ran the following command on all of the computers in order to sync their times with domain controllers.

net time \\(domain controller name) /set /y

And when I Stop the File Replication Services I got the following error:

Any help would be appreciated.

Thanks

I have a question?? Is there any way to clean up Active directory other than Meta data clean up?

I have network shared drive (hosted on my file server) that I would like to audit. On my DC I have set up group policy called "My auditing policy". 

Then under In “Group Policy Management Editor” under  “Computer Configuration” - “Policies” - “Windows Settings” - "Security Settings" -  “Local Policies” and under "Audit Policy" I defined policy to audit "Success" and Failure". Then On my DC I run "gpupdate /force" which gave me warning that some policy will involve re-directed drives and that I needed to log off in order for policy to take effect which I did.

I then proceeded to my file server where this network shared drive is located. This drive has sub directories...

    my shared drive

• directory 1
• directory 2
• directory 3
• ..............
• ...............

    

   I right click directory 2 and then "Properties" - "Security" - "Advanced" and enabled auditing of this folder (where Principal was  "Everyone").

I went as a regular user (usernameA) on different computer (all machines are domain members) and opened file within directory 2 and when I went into my file server machine and looked in Event Viewer under security I could not find any logs  for "usernameA". So I have 2 questions...

1. How does the policy know which directory needs to be audited?
2. Why am I not seeing any logs in Event Viewer on my file server?

 

We got some issues with Applocker and Adobe XD CC, when we block open Windows Store via GPO it works windows store can't open but when we install Adobe XD CC it also cannot open too it alert "This app has been blocked by your system administrator." "Contact your system administrator for more info." 

What should we do for these issues?
We using Windows Server 2012 R2 and Windows 10 Enterprise 1803.

--Samdy

Hello Everyone

Recently i Start migrating 700 users and computers with admt after that we going to migrate servers manually with Disjoin and join to new domain and without ADMT . 

So the problem is ( in some servers ) after we join them to new domain the Domain admins not automaticlly add to administrators group ! and in some of them after some while days or two it disapear from administrators group ! and we cannot connect via new domain account !

i must say that , i try to change some servers to workgroup and join them again , for now these servers are ok ! but the ones that join to new domain for the first time have above problem .

i cant find any solution for it and i dont even find what is the problem i know i can use GPO to force domain admins to join administrator group but i dont want do that ,  i want to know what is the problem and i dont have any gpo for my servers or OU that contain these Servers . 

in the old domain we have gpo for all computers to add administrator for local Computer ( windows server 2008)

in new domain we dont have this ( because its windows server 2016 and this policy is gone ) and we dont want it either

but i mentioned that if it can help .

please help me i want to have clean AD with Healthy servers not just apply some GPO to FIX the problem by Force

Hi, Recently our network team runs vulnerability test in our network. In the result we got SSL V3 Vulnerability error in windows server 2008 r2 in the ports 3269 and 636. I have read out some documents, articles and i did some security patches for this issue but it couldn't resolve. I need some clarification and also a solution for this issue. 

I appreciate your help. 

 

Hi,

I think this question has been asked for many times in Technet by other users. I read related posts but I'm not sure it will work or not. I delegate a user in ADUC to rename a computer and I gave full access permission to that user for the computer objects. When I log in to a client machine with the created and delegated help desk user account and type sysdm.cpl and enter it asked me domain user credentials. If delegating in active directory work or not?

Thanks

Hello TechNet,

One of my customers are experiencing issue with GPO executions during logon, especially the map network drive.

My GPO settings are set to await network connectivity before running.

The network drive GPO, is set up with the update action, and reconnect enabled.

As an example, one PC is connected wired to the network.

It's a flat layer 2 network, no subnet segmentation and no firewall in-between. 

When the user logs on, it takes a while. After, the network drives are not loaded (even though I have my settings as mentioned).

When I look the event log, I see warnings and alerts with DNS towards the domain controllers, and GPO not being able to run due to no connection to DC

But if I execute an NSLookup and as for the domain or domain controllers, it resolves. Also after an IPCONFIG /FLUSHDNS and reboot.

If I clock on the "disconnected network-dive" I get connection the the drives. 

I've been searching the web for troubleshooting steps and where to start. But I havn't found a solution that works yet.

A bit more info:
Domain controller are 1 2003 server and 1 2008R2 server. Both are internal DNS server as well, pointing towards each other as primary DNS.

They are virtual

The PC is connected to one access switch, with an 1Gb/s uplink to the core switch. The hyper visor are connected to the core witch as well with several 1Gb/s uplinks. 

Network speed test show close to 1Gb/s internal with both down-and upload from PC to server

Looking forwards to hear some suggestions.

Kind regards

Jonas 

HI I have problem with  some users, when user logon on webapplication on IIS. Webrowser on header return lower case samaccountname example.

User logon integrated, header return DOMAIN\user.

on the other header return DOMAIN\USER.

I think is the problem on AD, but where ?

Thank's for suggestions.

Greetings,

I am trying to use the following Powershell code to bulk import DNS A records into Windows 2008 DNS:
Import-Csv .\thosts.csv | foreach{Add-DnsServerResourceRecordA -Name $_.name -ZoneName xxxxx.com -AllowUpdateAny -CreatePtr -IP $_.ip 

-Computername xxxxxxx} 

My CSV file looks like this:
Name, IP
ABQVMP01, 130.77.129.237

It runs successfully, but the DNS name ends up being ABQVMP01.xxxxx.com.xxxxx.com, instead of ABQVMP01.xxxxx.com. I have looked for something to control this in the command syntax, but do not see anything: https://docs.microsoft.com/en-us/powershell/module/dnsserver/add-dnsserverresourcerecorda?view=win10-ps

We are running AD and DNS at the 2008 level. Powershell is version 5.1. I am running this as a domain admin.

Thanks in advance and happy to answer any more questions,
Rick

Hi,

I've configured the Account Lockout Policy in windows server 2012 domain controller for a specific OU. After deleting the GPO the policy still applying on the user. How can I disable the Account Lockout Policy?

Thanks

Hi

We are looking for event ids specific to join & disjoin any new PCs / Servers to domain. Event ID 4741 is generating while we add any new Systems, but didn't find any specific IDs while disjoin any systems from domain. Can some one help on this topic

Thanks in advance

---

LMS

Hi,

I am trying to use linked server to query AD to fetch all users from domain.There are no filters except that Object class=User and our directory has over 7000 users.The problem is ,the top limit set up at Ad that just lets me fetch 7000 rows and I cant change that.Please help me with solution that will enable me to query users beyond the limit.I am aware of a concept called paged search but not sure how to implement it via linkedserver.I dont want to use powershell.I tried to seek answers in msdn sql server forums,but no luck.They suggested to loop through the search,but it didnt work.

I tried the following but couldnt get more than 7000 rows:

 SELECT SAMAccountName, displayName,userPrincipalName
FROM OpenQuery (ADSI,  
                'SELECT SAMAccountName, employeeID, displayName, givenname, sn, 
                        scriptpath, distinguishedName,userPrincipalName,mail
                 FROM ''LDAP://abc.com/DC=abc,DC=com'' 
                 WHERE objectClass =  ''User''
                 ') AS A 

I reset my password and my account began to lock out. I set my password back to the original, but the account continues to lock out. Using accountlockoutstatus from Sysinternals I was able to determine the domain controller that is receiving the failed attempt (it's always the same DC). I parsed through the typical security events on the the DC receiving the failures and the PDC, but the offending computer is just showing as LOCALHOST and I can't find an IP address. I used Netwrix Account lockout examiner, but I receive the exact same information... I can't find the offending device. I ran a script to find all machines on the domain where the account is logged in or has a disconnected status. I logged out of all the machines and my account didn't lockout for a day. However, the next morning it was locked out again. I ran the script again and I found no sessions. We map drives with group policy, but this account has never had mapped drives. The account is not used on any mobile devices, and I have not cached credentials. 

How can I find the offending device?

Thank you in advance for your help!!!

Hello Friends :

I want to show you that how can you findout the place which your domain users are logging in ,
Of Course i mean the computer account which the user is using for logging in :

1- The first way is to use a free command line tool called "PsLoggedOn v1.33" you can downlaod it from here:
    http://technet.microsoft.com/fa-ir/sysinternals/bb897545(en-us).aspx

2- The second way is to use a free and open source third pary application called " Kaboodle " :
    http://www.kaboodle.org/index.html

3-The Thirs way is to use a command line tool called "NBTSCAN " you can see a sample trick here :
  
 C:\nbtscan>nbtscan 192.168.0.100-200
 Doing NBT name scan for addresses from 192.168.0.100-200

 IP address       NetBIOS Name     Server    User             MAC address
 ------------------------------------------------------------------------------
 192.168.0.119    SQUASH           <server>  SQUASHMAN        12-34-ba-c0-52-32
 192.168.0.153    BUMBLE-BEE       <server>  BUMBLE-BEE       00-0f-1f-b3-b5-89

 C:\nbtscan>

You can downlaod it from here : http://linux.wareseeker.com/download/nbtscan-1.5.1.rar/334598

---

Network is my LOVE

C:\>DCDIAG

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = HPDC1
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\HPDC1
      Starting test: Connectivity
         ......................... HPDC1 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\HPDC1
      Starting test: Advertising
         ......................... HPDC1 passed test Advertising
      Starting test: FrsEvent
         ......................... HPDC1 passed test FrsEvent
      Starting test: DFSREvent
         There are warning or error events within the last 24 hours after the SYSVOL has been shared.  Failing SYSVOL
         replication problems may cause Group Policy problems.
         ......................... HPDC1 failed test DFSREvent
      Starting test: SysVolCheck
         ......................... HPDC1 passed test SysVolCheck
      Starting test: KccEvent
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:14:30
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051C
            Time Generated: 01/15/2019   15:14:30
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:14:30
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:14:30
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:14:37
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:14:39
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:14:39
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:14:39
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:14:39
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000786
            Time Generated: 01/15/2019   15:14:39
            Event String:
            The attempt to establish a replication link to a read-only directory partition with the following parameters failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:15:48
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051C
            Time Generated: 01/15/2019   15:15:48
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:15:48
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:15:48
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:15:55
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:15:57
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:15:57
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:15:57
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:15:57
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000786
            Time Generated: 01/15/2019   15:15:57
            Event String:
            The attempt to establish a replication link to a read-only directory partition with the following parameters failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:17:51
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051C
            Time Generated: 01/15/2019   15:17:51
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:17:51
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x8000051B
            Time Generated: 01/15/2019   15:17:51
            Event String:
            The Knowledge Consistency Checker (KCC) has detected that attempts to establish a replication link with the following directory service has consistently failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:17:57
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:17:59
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:17:59
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:17:59
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000785
            Time Generated: 01/15/2019   15:17:59
            Event String:
            The attempt to establish a replication link for the following writable directory partition failed.
         A warning event occurred.  EventID: 0x80000786
            Time Generated: 01/15/2019   15:17:59
            Event String:
            The attempt to establish a replication link to a read-only directory partition with the following parameters failed.
         ......................... HPDC1 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... HPDC1 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... HPDC1 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... HPDC1 passed test NCSecDesc
      Starting test: NetLogons
         ......................... HPDC1 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... HPDC1 passed test ObjectsReplicated
      Starting test: Replications
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: DC=ForestDnsZones,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (1256):
            The remote system is not available. For information about network troubleshooting, see Windows Help.
            The failure occurred at 2019-01-15 14:51:54.
            The last success occurred at 2019-01-15 09:58:17.
            5 failures have occurred since the last success.
         [DC-VLZ] DsBindWithSpnEx() failed with error 1722,
         The RPC server is unavailable..
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: DC=DomainDnsZones,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2019-01-15 14:53:55.
            The last success occurred at 2019-01-15 10:07:46.
            14 failures have occurred since the last success.
            The guid-based DNS name 9d9a0759-1d8b-4fda-8c13-6bbe01fa994d._msdcs.hpddomain.com.ph
            is not registered on one or more DNS servers.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: CN=Schema,CN=Configuration,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2019-01-15 14:52:01.
            The last success occurred at 2019-01-15 09:58:11.
            5 failures have occurred since the last success.
            The guid-based DNS name 9d9a0759-1d8b-4fda-8c13-6bbe01fa994d._msdcs.hpddomain.com.ph
            is not registered on one or more DNS servers.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DP-DICOMSERVER to HPDC1
            Naming Context: CN=Configuration,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8606):
            Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.

            The failure occurred at 2019-01-15 14:52:03.
            The last success occurred at (never).
            99 failures have occurred since the last success.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: CN=Configuration,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2019-01-15 14:53:49.
            The last success occurred at 2019-01-15 10:03:23.
            13 failures have occurred since the last success.
            The guid-based DNS name 9d9a0759-1d8b-4fda-8c13-6bbe01fa994d._msdcs.hpddomain.com.ph
            is not registered on one or more DNS servers.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DP-DICOMSERVER to HPDC1
            Naming Context: DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8606):
            Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.

            The failure occurred at 2019-01-15 14:51:48.
            The last success occurred at (never).
            97 failures have occurred since the last success.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: DC=hpddomain,DC=com,DC=ph
            The replication generated an error (8524):
            The DSA operation is unable to proceed because of a DNS lookup failure.
            The failure occurred at 2019-01-15 15:18:55.
            The last success occurred at 2019-01-15 10:06:52.
            190 failures have occurred since the last success.
            The guid-based DNS name 9d9a0759-1d8b-4fda-8c13-6bbe01fa994d._msdcs.hpddomain.com.ph
            is not registered on one or more DNS servers.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: DC=sharepoint2k16,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (1256):
            The remote system is not available. For information about network troubleshooting, see Windows Help.
            The failure occurred at 2019-01-15 14:51:54.
            The last success occurred at 2019-01-15 09:58:20.
            5 failures have occurred since the last success.
         [Replications Check,HPDC1] A recent replication attempt failed:
            From DC-VLZ to HPDC1
            Naming Context: DC=HP-SHAREPOINT,DC=hpddomain,DC=com,DC=ph
            The replication generated an error (1256):
            The remote system is not available. For information about network troubleshooting, see Windows Help.
            The failure occurred at 2019-01-15 14:51:54.
            The last success occurred at 2019-01-15 09:58:26.
            5 failures have occurred since the last success.
         ......................... HPDC1 failed test Replications
      Starting test: RidManager
         ......................... HPDC1 passed test RidManager
      Starting test: Services
         ......................... HPDC1 passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:29:11
            Event String:
            The session setup from computer 'LP-DARRYL' failed because the security database does not contain a trust account 'LP-DARRYL$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:31:15
            Event String:
            The session setup from the computer LP-DARRYL failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:33:58
            Event String:
            The session setup from computer 'SUC-IMAGING1' failed because the security database does not contain a trust account 'SUC-IMAGING1$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:36:08
            Event String:
            The session setup from the computer SUC-IMAGING1 failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:37:25
            Event String:
            The session setup from computer 'HPUSERPC' failed because the security database does not contain a trust account 'HPUSERPC$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:39:26
            Event String:
            The session setup from the computer HPUSERPC failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:41:18
            Event String:
            The session setup from computer 'DS-PHLEBOA' failed because the security database does not contain a trust account 'DS-PHLEBOA$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:43:48
            Event String:
            The session setup from the computer DS-PHLEBOA failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:49:58
            Event String:
            The session setup from computer 'SI-IMAGING2' failed because the security database does not contain a trust account 'SI-IMAGING2$' referenced by the specified computer.
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   14:51:04
            Event String:
            The session setup from computer 'SR-PHLEBO2' failed because the security database does not contain a trust account 'SR-PHLEBO2$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:52:03
            Event String:
            The session setup from the computer SI-IMAGING2 failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   14:53:12
            Event String:
            The session setup from the computer SR-PHLEBO2 failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x40000004
            Time Generated: 01/15/2019   14:58:06
            Event String:
            The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server ml-imageserver$. The target name used was cifs/ML-DICOM.hpddomain.com.ph. This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (HPDDOMAIN.COM.PH) is different from the client domain (HPDDOMAIN.COM.PH), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   15:11:35
            Event String:
            The session setup from computer 'AL2-IMAGING61' failed because the security database does not contain a trust account 'AL2-IMAGING61$' referenced by the specified computer.
         An error event occurred.  EventID: 0x0000165B
            Time Generated: 01/15/2019   15:12:08
            Event String:
            The session setup from computer 'HPUSER-PC' failed because the security database does not contain a trust account 'HPUSER-PC$' referenced by the specified computer.
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   15:13:59
            Event String:
            The session setup from the computer AL2-IMAGING61 failed to authenticate. The following error occurred:
         An error event occurred.  EventID: 0x000016AD
            Time Generated: 01/15/2019   15:14:50
            Event String:
            The session setup from the computer HPUSER-PC failed to authenticate. The following error occurred:
         ......................... HPDC1 failed test SystemLog
      Starting test: VerifyReferences
         ......................... HPDC1 passed test VerifyReferences


   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : hpddomain
      Starting test: CheckSDRefDom
         ......................... hpddomain passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... hpddomain passed test CrossRefValidation

   Running enterprise tests on : hpddomain.com.ph
      Starting test: LocatorCheck
         ......................... hpddomain.com.ph passed test LocatorCheck
      Starting test: Intersite
         ......................... hpddomain.com.ph passed test Intersite

C:\>

Hi,

DCs: Windows 2012 R2

I have noticed in DNS (non Windows DNS) that we have 3 PTR records created for each Domain Controller. They are:

nslookup

> 10.10.10.32

Name: gc._msdsc.mydomain.com

Name: mydomain.com

Name: DC01.mydomain.com

Can someone explain how the first two entries have been created. Normally, only the last entry should be created.

dave