Active Directory, DNS, DC, GC, Domain Controller, TCP/IP

January 19th, 2008 Categories: software

- The Netlogon service does not start and event IDs 2114 and 7024 are logged in Windows Server 2003 and in Windows 2000 Server

After upgrading my W2K3 PDC to SP1, I’m now getting this error when the
windows time service starts.

Domain Secure Channel Utility — Nltest.exe

- How to verify Active Directory Domain Controller DNS Registration:
Run ipconfig /registerdns
- Registers only A and PTR records
- Check the netlogon.dns log file locaated by default at: %systemroot\system32\config
- Restart the netlogon service

Using NSlookup.exe

DNS problem?

Network Services Management Support Tools

NetLogon Service Fails When Secure Channel Not Functioning

Full Version: DNS errors

Browsing not working on one machine

How to configure an authoritative time server in Windows Server 2003

How to view and set LDAP policy in Active Directory by using Ntdsutil.exe

Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller

How to view and transfer FSMO roles in Windows Server 2003

Domain Controller issues

Domain controller does not find GC

How to remove and reinstall TCP/IP on a Windows Server 2003 domain controller

Errore MSDTC: I think I may have found a fix for the time being. I’m not entirely sure why
it works as of yet, but after performing the below steps, MSDTC no longer
logs warnings to the application event log. It’s interesting because a
typical start of MSDTC via the Services MMC snap-in or via the command line
consistently logs the aforementioned warnings to the application event log.
But, if you stop and start MSDTC once through the Component Services MMC
snap-in, any start of MSDTC going forward is warning free.

Run the Component Services MMC snap-in: Start -> Administrative Tools ->
Component Services

Browse to: Console Root -> Component Services -> Computers -> My Computer

Right click My Computer, and click “Stop MSDTC”

Then, right click My Computer again, and click “Start MSDTC”

Then as a test, restart MSDTC (net stop msdtc && net start msdtc) and check
the application event log. You should not see any warnings as before.

I think I may have inadvertently thought the steps I posted actually fixed
the problem, but I now believe it was one step I forgot I performed.

In Component Services, right click on My Computer, and click “Properties”.

Select the “MSDTC” tab. On the bottom of the tab page, click the “Security
Configuration” button. A new dialog will open. Just click “OK” to close the
dialog (I believe this may set the MSDTC defaults). Then click “OK” to close
the first dialog and try restarting the MSDTC service and see if the warnings
still occurr.

PDF Download    Invia l'articolo in formato PDF a
Tags: , , , , , , , ,
No comments yet.

Leave a Comment