Dear All,

I have deploy Active Directory 2012 in my Environment. I create one user like dipendra.prodeep.com.np

I join the my 2 client PC which is running on XP2. when I am Log-in  Both PC through my username and Password (dipendra.prodeep.com) it's log-on both PC in same time.

I want to create one user can log-in only one PC at a time, not multiple PC at a time. if one is log-out this PC after that another can log-in on other PC in same username.

Thanks and regards,

Dipendra paudel

Dipendra Paudel

Hi,

I have DC and ADC. In ADC my client user name have access to create/delete user account. My doubt how i find out whether he only created that user account or not ? 

How to check the Particular User Create/Delete any user accounts ?

Thanks in advance

Regards, Hari Prasad.D

Hi All,

Is it possible to add a 2003 domain controller to a 2012 domain? As the 2012 forest level is the same as 2008 R2 I don't see why there should be a problem but I just want to make sure.

I have a customer who wants to reuse some servers are remote sites to act a domain controllers after I build them a new 2012 domain. I don't like it myself but the budget is very tight for the time being so there's a much reusing old kit and licenses as possible.

Thanks

Conor

I have just started here. So this looks like a legacy issue.  ugh!

When I try to remove AD from some servers that are in AD but do not need to be Domain Controllers, it always fails and looking at the logs, I see the server that holds the Infrastructure role is an old one from 4 years ago.  I have followed the suggestions using adsiedit and the like and it 'sorta' worked.  Yesterday all were pointing to the old server.  Today, I was able to edit it and it looks like it should.  running ndsutil points to the correct servers.

I have one server that does not get "the correct role holder' will not allow me to asdiedit the role holder.  Followed that kb.  dcpromo still fails.  I gotta be missing something. (obviously).

I am stumped.  All diags run ok and error (fairly) free.  Before I hose it up too much, 

Any ideas?

I have 4 servers and want to remove the AD services from 2.

Boss needs forest/AD/GPO documentation for the next admin that comes to see how everything is laid out..

Any idea how to do it?

We have a Server 2008 R2 active directory domain, 2008 R2 functional level for domain and forest, 3 DCs, Exchange 2010 server, multiple SQL 2008 servers, Blackberry Enterprise Server, 4 DFS servers, about 2 dozen member servers, and ~400 users spread around a dozen geographic locations.  Single domain, which is also the forest root.

The business was re-named and the IT department has been tasked with renaming the domain and everything therein.

Based on your collective experience, is it better to go through the effort of re-naming the current domain, or should we start over with a new forest, new domain, and migrate from old forest to new.

We don't want to create a new domain in the same forest, since the exsiting domain name (the forest root) will no longer be used and we don't want to maintain domain controllers ONLY to prop up that old root/domain.

Opinions, suggestions, pitfalls, tales from the trenches-- all welcome. 

Hi,

Installed the AD on Server 2012 Virtual Machine with top level domain name .LOCAL. Company already has Internet name with top name .ORG (Company.org). Is that possible to change top internal domain from .local to .org?

I think it will be easier for me to deploy an Exchange later with user’s address user@company.org instead user@company.local.

Thank you in advance

Hi ,

I set up two different domain server (windows 2008r2)  in the same subnet (192.168.44.0/24) with this configuration:

server1.test1.local:

IP address:192.168.44.150/24

and:

server2.test2.local

 IP address:192.168.44.149/24

these are 2  domain servers are in different forest and I want to create a trust relation between them.

they can ping each other and also with their name ( server1 and server2) and I add their IP address as a secondary DNS for each other

but when I want to add for example server1.test1.local in the name server list of server2 or add server2.test2.local in the name server list of server1 , I see this error:

the server with this IP address is not authoritative for the required zone 

I saw this error whenever I want to add  one of the  dns name and resolve the ip address of that in another dns server.

could you please assist 

Thanks

Hi,

Please help.

My office using Windows server standard 2003 R3 SP2 and the users use Windows XP SP3 Pro.

Recently i join all the users in our office to the server domain for global password policy settings. I create their user in the Active Directory and use that user to logon to their computer/laptop.

After join domain the computer all the user having problem, their computer become slow on a fix time everyday

E.g. : some computer become slow at 4.30 PM, or other computer become slow at 7.00PM

Before join the server domain there is no slow problem. Any solution for this problem.

Kindly help. Thanks.

Last night, I moved the DHCP role to a second domain controller, and then demoted the one I moved it off of (had to be force removed because of some errors).

This morning, about half of the DNS A records of the computers in that office showed up in DNS (timestamp at 6 AM, when they automatically booted). But half of them have no DNS records. Why are some of them not showing up?

The only unusual event viewer warning is that it didn't have DNS credentials. http://support.microsoft.com/kb/282001/en-us I put those in like the website said, and still nothing.

In IPV4 & scope Properties > DNS tab, I changed the option to Always dynamically update DNS. No good.

 Why is this half working?  What else can I try? 

My Windows 7 clients are unable to join AD using the FQDN of the domain since the domain was upgraded to Server 2012/AD 2012 and the FSMO/GC role was transferred as part of the upgrade.  We retired the old FSMO/GC holder and demoted it as part of the upgrade.

Clients can join the domain via the netbios name with no issues.  I think this may have been a sporadic issue prior to the upgrade, but it's definitely become consistent in the weeks following it.  dcdiag command returns no unusual messages.

Further complicating our situation is the fact that we are using a Linux based DNS server, so all service records were created by hand.  My first thought is that the record for the new server was somehow incorrect, but we simply replaced the old server record with an exact duplicate with the host name change where appropriate.  This record has been place since we first implemented AD as part of Server 2000, so it is entirely possible that the server record required for 2012 is different and a possible issue.

Any thoughts?  This is not a show stopper, but something is definitely amiss.  

Dear Community Members,

I have a requirement where I need to add extra IP telphone field in the Users. Help appreciated.

Best Regards 

hello,

i have a dc server i planed to move it to other server... i installed the other server and add it as a additional domain then i moved the fsmo roles except the schema after 10mins i try to open ad but it's give me the i can contact it.

so where is the problem what i have to do?

thanks.

We've set up an ADFS 2.0 server and 2008R2 RODC in a site together, and have enabled the RODC to cache passwords.

We expected ADFS to use the RODC that is located in the site with it.

We see in Resource Monitor that there is traffic from LSASS.exe to the RODC as we would expect, however we are also getting traffic from Microsoft.Identity.ServiceHost.exe to one of our writable DC's in another site.

Why are we seeing traffic to our other DC? We would have expected ADFS to talk to the RODC in the site with it.

Hello everyone, I have a two way transitive trust between two forest.  Forest A and forest B. 

On child domains of forest A i can create local groups and even put users from forest B. 

but when I log to a workstation on a child domain of forest A. I do not see the option to login with a user from any domain in Forest B. Is there something I am missing. 

When I look at the trusts on the root domain of forest A. I see the domains on Forest B as trusted and is transitivie. but when I go to a child domaino on Forest A. (child.forestA.local) I do not see any domains from Forest B in trusted by this domain

Hi everyone,

Recently (about 2 weeks ago) I performed a rendom on one of our two domains here.  The domain is a subdomain of a top level domain that is NOT an active directory domain.  First background on what was done:

originaldomain.com  <--- top level domain controlled by unix DNS servers at our location

groupa.originaldomain.com <---- domain 1, AD domain, proper glue records on the unix dns servers to relate all dns lookups for the subdomain to DNS servers in the AD.  This domain is nat'd.

groupb.originaldomain.com <---- domain 2, AD domain, proper glue records on the unix dns servers to relate all dns lookups for the subdomain to DNS servers in the AD.  This domain is nat'd on a separate network from groupa.

groupa and groupb, although both subdomains of originaldomain.com do not have trusts between them, we utilized this so it is easy to reference services and servers by FQDN instead of IP address.  This arrangement has always worked perfectly.  We were recently informed that we would be required to change our domain.  So now we have:

newdomain.com

as the new toplevel domain.  We still have originaldomain.com for a while longer before we surrender it.

groupb is a less critical group so it was the first we decided to perform the rendom on.  The rendom went smoothly and the roughly 180 workstations all were rebooted twice and showed the new name.

gpfixup was run

netdom renames were performed on each of the DC's

rendom /clean was performed

rendom /end was performed

No errors occurred and all operations reported success.

Spot checks showed the domain appeared to be working, users could log in, DNS was resolving correctly.  groupb was now:

groupb.newdomain.com

Now comes the problem, I was doing work on one of the DC's and noticed that if I ran gp management, it was trying to access the old group policies, not the new ones.  I checked the other DC's in the domain and the rest all seem to use the new domain, so for some reason one DC was in a weird state and attempting to utilize the old domain for GP.  I demoted the DC and re-promoted it and the problem persisted.  So at this point I'm thinking there is something else wrong, so I look at the DNS which shows something odd:

dc

|- Forward Lookup Zones

    |- _msdcs.olddomain.com

    |- newdomain.com

    |   |- _msdcs

    |- olddomain.com

So my forward lookup zone still has the old domain entries in it and instead of having a yellow  _msdcs.newdomain.com, _msdcs is a subfolder of newdomain.com.  I have no idea why this is or what I will need to do in order to fix it - I was under the impression that the /clean was going to remove all references to the old domain.  The only thing I can think is that between the clean and the end not enough time was given for replication.  There was only one other indication of an issue - when I ran DCDIAG I got an entry:

All other dcdiag tests passed without a problem.  I'm thinking the problem with the DFSREvent is either related to the DNS issue or the server that is giving bad values with regard to group policy management (which may be tied into the DNS issue).

I do see DFSR error event ID 1202 in the DFS Replication logs, but it doesn't tell me which server it's attempting to replicate with in terms of the failure...

Any suggestions would be most appreciated.

Let me give background on my environment

Small Business Server 2003 Standard & Windows 2008 Standard Terminal Server (no workstations) When users attempt to logon to the terminal server they get "Access Denied" right before they get to a desktop. If a user is part of the domain admin's they can login with no issues (this is how I discovered this issue, I was cleaning out the domain admin's group) I also get issues when trying to run anRSOP.msc from this machine & gpupdate /force as well. I tried adding a Windows 2008R2 machine to the domain and ran into the same issues when running the above commands.

This environment seems to be an upgrade from Server 2000 from what I can tell. I recently raised the domain/forest function levels to 2003.

I turned on Kerberos logging & enabled debugging. In my research it is possible this is a SPN issue, but I cannot view the SPN's attached to my LocalSystem account (Terminal Serv Licensing runs under this context) as this error is returned each time I check: FindDomainForAccount: DsGetDcNameWithAccountW failed!

I tried the following commands all with the result above:

• setspn –L “Local System”     
• setspn –L “LocalSystem”    
• setspn –L LocalSystem

Now to my error logs, here are a couple entries from the SBS box event log:

Client Time:

 Server Time: 18:15:0.0000 8/29/2013 Z

 Error Code: 0x7 KDC_ERR_S_PRINCIPAL_UNKNOWN

 Extended Error:

 Client Realm:

 Client Name:

 Server Realm: GU.LOCAL

 Server Name: TermServLicensing

 Target Name: TermServLicensing@GU.LOCAL

 Error Text:

 File: 9

 Line: b22

 Error Data is in record data.

A Kerberos Error Message was received:

        on logon session

 Client Time:

 Server Time: 18:15:0.0000 8/29/2013 Z

 Error Code: 0xd KDC_ERR_BADOPTION

 Extended Error: 0xc00000bb KLIN(0)

 Client Realm:

 Client Name:

 Server Realm: GU.LOCAL

 Server Name: host/gu-sbs1.gu.local

 Target Name: host/gu-sbs1.gu.local@GU.LOCAL

 Error Text:

 File: 9

 Line: b22

 Error Data is in record data.

Here is some of the Kerberos debug log file:

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x252ac6f, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536aa9, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536c71, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536d36, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536d57, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536d96, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536db7, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536dee, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2536e24, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2539dca, accepting 0:0x3e7

416.1148> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x253ae5b, accepting 0:0x3e7

416.6988> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.6988> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x253dba3, accepting 0:0x3e7

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.516> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.516> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x253e126, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x253e13c, accepting 0:0x3e7

416.596> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.596> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2540d9a, accepting 0:0x3e7

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2548944, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x254ef74, accepting 0:0x3e7

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.1144> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1144> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2552bb2, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2552c0a, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2552c69, accepting 0:0x3e7

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x255628d, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x255b944, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2560d3d, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.408> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25674b5, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x256d68c, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25748c0, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket creating logon session for 0:0x2579c99, accepting 0:0x3e7, client GU-SBS1$@GU.LOCAL

416.7292> Kerb-Warn: KerbGetTgsTicket failed to unpack KDC reply: 0x3c

416.7292> KSupp-Warning: KerbUnpackData failed to unpack typed data, trying error method data

416.7292> KSupp-Error: KerbUnpackErrorData received failure from kdc 0xd KLIN(0) NTSTATUS(0xc00000bb)

416.7292> Kerb-Warn: Failed S4Uproxy request c00000bb(4)

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2579da8, accepting 0:0x3e7

416.1052> Kerb-Error: Failed to create token: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\krbtoken.cxx, line 2461

416.1052> Kerb-Error: Failed to create token from ticket: 0xc000006e. d:\nt\ds\security\protocols\kerberos\client2\ctxtapi.cxx, line 3778

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x257fef7, accepting 0:0x3e7

416.6988> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2583a27, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2585499, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2586667, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25866bc, accepting 0:0x3e7

416.1148> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x258671b, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x258c183, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2591dcb, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2597bf9, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x259cfa0, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25a04c7, accepting 0:0x3e7

416.6988> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25a3279, accepting 0:0x3e7

416.7264> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25a4281, accepting 0:0x3e7

416.1148> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25a6c5b, accepting 0:0x3e7

416.1148> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25a6fa7, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25abc77, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25abcc7, accepting 0:0x3e7

416.7304> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25aed24, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25b430e, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25b45fb, accepting 0:0x3e7

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25b9b5a, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25bdeb3, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25bdf11, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25bdf7c, accepting 0:0x3e7

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25bf9da, accepting 0:0x3e7

416.6988> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25c148e, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25c185a, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25c18f8, accepting 0:0x3e7

416.596> Kerb-Warn: KerbGetTgtForService getting new TGT for account

416.596> Kerb-LSess: KerbFindCommonPaEtype using current password of administrator@GU.LOCAL

416.7304> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25c6957, accepting 0:0x3e7

416.7304> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25cc78e, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25d18ca, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25d7814, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25dcb8c, accepting 0:0x3e7

416.508> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25e1f6f, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25e7e04, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25ed805, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25ef286, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25ef2fc, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25ef35b, accepting 0:0x3e7

416.7264> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25f3093, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25f83ee, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x25fe33c, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.408> Kerb-LSess: KerbFindCommonPaEtype using current password of morgan.perkins@GU

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2602180, accepting 0:0x3e7

416.7304> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.408> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.7296> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.504> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.508> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.7264> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x26025a8, accepting 0:0x3e7

416.7304> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2603b97, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2609007, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x260b9d0, accepting 0:0x3e7

416.7264> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x260f6f8, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket creating logon session for 0:0x2613373, accepting 0:0x3e7, client GU-SBS1$@GU.LOCAL

416.8768> Kerb-Warn: KerbGetTgsTicket failed to unpack KDC reply: 0x3c

416.8768> KSupp-Warning: KerbUnpackData failed to unpack typed data, trying error method data

416.8768> KSupp-Error: KerbUnpackErrorData received failure from kdc 0xd KLIN(0) NTSTATUS(0xc00000bb)

416.8768> Kerb-Warn: Failed S4Uproxy request c00000bb(4)

416.508> Kerb-Warn: KerbReplacePasswords replacing old keys

416.508> Kerb-LSess: KerbFindCommonPaEtype using current password of GU-SBS1$@GU.LOCAL

416.508> Kerb-Warn: KerbGetTgsTicket failed to unpack KDC reply: 0x3c

416.508> Kerb-Warn: KerbGetTgsTicket KerbCallKdc: error 0x7

416.508> Kerb-Warn: Failed to get TGS ticket for service 0xc000018b :

 TermServLicensing

416.508> Kerb-Warn: d:\nt\ds\security\protocols\kerberos\client2\kerbtick.cxx, line 3899

416.508> Kerb-Warn: SpInitLsaModeContext failed to get outbound ticket, KerbGetServiceTicket failed with 0xc000018b

416.7264> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2614eb3, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x261a33e, accepting 0:0x3e7

416.516> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x261ec25, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x261ed0d, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x261ed62, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x261edc1, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2620148, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2625d68, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x262b0db, accepting 0:0x3e7

416.408> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263031e, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263671a, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263bb8c, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263d9da, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263e8fe, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x263e94d, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x26411f6, accepting 0:0x3e7

416.7304> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x26464c1, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x264c661, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x264f440, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x264f495, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x264f4f4, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2651e39, accepting 0:0x3e7

416.6988> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2654aaa, accepting 0:0x3e7

416.1052> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2654ecd, accepting 0:0x3e7

416.1144> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2654f16, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2657979, accepting 0:0x3e7

416.504> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x265d84a, accepting 0:0x3e7

416.7296> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2662f54, accepting 0:0x3e7

416.7072> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x2669279, accepting 0:0x3e7

416.504> Kerb-LSess: KerbFindCommonPaEtype using current password of IUSR_GU-SBS1@GU

416.7264> Kerb-LSess: KerbCreateLogonSessionFromTicket NOT creating ASC logon session for 0:0x266fbe2, accepting 0:0x3e7

Hello,

I have enabled netlogon logging, and am noticing a few things that I am unable to diagnose after further research. My main concern is with a critical error that seems to occur every ten minutes. Occasionally the Chinese characters change but always translate to roughly the same message. Searching google for information about "I_NetlogonLdapLookup" has provided no helpful information either. Does anybody know what could cause this? We have 3 DCs (Server 2008R2, 2012) and this shows up in all three netlogon logs.

08/26 17:55:40 [CRITICAL] I_NetlogonLdapLookup: unrecognized parameter 湄䡳獯乴浡ѥ䠗偙剅㍖渮

All client computers are Windows 7 Pro x64. Any help is appreciated, thanks.

Alex Tester Information Technology Assistant National Automotive Experts