Net Logon Service Paused

[SaltLife]

OS:

Windows 2003-R2

Over view of the Domain Details:

We have a single PDC environment ran within a virtual machine. This PDC also hosts DHCP and DNS

This server was initially a dedicated server that was running on out of date hardware in a clustered DC environment. When this server was converted into a PDC the other DC's were taken off line sucessfully using DCPROMO.

Problem:

I just recently rebooted this server for standard maintenance when the DC came online the net logon service was sent a "Pause" command.

Source: Service Control Manager

Event ID: 7035

I immediately went into services.msc and "resumed" the service and everything appears to be working. However this seems to be a bandaid.

I ran DCDIAG and the only failure to occur is:

Starting test: Services

* Checking Service: Dnscache

* Checking Service: NtFrs

* Checking Service: IsmServ

* Checking Service: kdc

* Checking Service: SamSs

* Checking Service: LanmanServer

* Checking Service: LanmanWorkstation

* Checking Service: RpcSs

* Checking Service: RPCLOCATOR

RPCLOCATOR Service is stopped on [OZLO5]

* Checking Service: w32time

* Checking Service: TrkWks

* Checking Service: TrkSvr

* Checking Service: NETLOGON

......................... MYPDC failed test Services

Any other insight would be helpful. I have read searching google that it may be caused by a GUID issue and DNS... not sure.

-- Thank You

Edited August 11, 2008 by ivdubvr6i

[Joel]

What OS?

[SaltLife]

What OS?

Wow, of all the things to forget... //bad bad bad

Windows 2003-R2 STD

[SaltLife]

Does anyone know how to obtain a current GUID? This is relevant to the original question. I need to determine what is causing the server to pause the service on startup.

[Grogi]

Have you checked fsmo roles?

There are two ways: ntdslutil or from w2k3 support tools: netdom query fsmo

Check if some of roles left on second DC. If so, seize it to PDC. Ofcourse, your PDC must be global catalog also before do anything. Check that!

[SaltLife]

Have you checked fsmo roles?

There are two ways: ntdslutil or from w2k3 support tools: netdom query fsmo

Check if some of roles left on second DC. If so, seize it to PDC. Ofcourse, your PDC must be global catalog also before do anything. Check that!

Okay, thanks

Just checked all of the roles and it results in:

C:\>netdom query fsmo MYPDC

Schema owner MYPDC

Domain role owner MYPDC

PDC role MYPDC

RID pool manager MYPDC

Infrastructure owner MYPDC

Which I pretty much expected. The PDC had to be functional before I upgraded it to Windows 2003 server. Which it was. I feel the pausing of the service has something to do with converting the server into a virtual machine that runs on ESX. Has anyone had any experience with this??

[Joel]

The PDC had to be functional before I upgraded it to Windows 2003 server. Which it was.

Whoa, you never said you upgraded anything. You said you converted a physical machine to a VM.

There are no PDCs in a 2000-2003 domain. They're just DCs.

[SaltLife]

Whoa, you never said you upgraded anything. You said you converted a physical machine to a VM.

There are no PDCs in a 2000-2003 domain. They're just DCs.

Okay, you got me. There are no PDC/BDC in the same since as 2k or NT. The machine was converted to Windows 2003 after I removed all other DC controllers from the domain. This was all done while the machine was a "physical" box. Only once everything was completed and working did we convert the machine into a virtual clone.

[Richard Maletta]

I have the exact same issue On startup

I have a Proliant DL380 G5 running Windows 2003 SP 3

It is the Domain Controller running Exchange 2003

It is also the DHCP and DNS Server

dcdiag and nsdiag both are correct

On startup

First I get a error telling the the time server could not logon then

I get and event 7035 telling me that the Net Logon server has been sucessfully sent a Pause.

and lastly exchange can not start again because it can not logon

Once I logon I can

1) Resume the Netlogon service

2) Start exchange

3) Start Windows time server

Then all is well