DNS Service doesn't start on bootup

Fresh install of 2008 R2, DNS and AD DS roles installed. On reboot, DNS
doesn't start automatically, but I can log on and start DNS manually. In
system events, I see ID 7036 "The DNS Server service entered the stopped
state," followed by ID 7023, "The DNS Server service terminated with the
following error: The network is not present or not started." Suggestions on
where to start?

"Joe Blizzard" <> wrote in message
news:...
> Fresh install of 2008 R2, DNS and AD DS roles installed. On reboot, DNS
> doesn't start automatically, but I can log on and start DNS manually. In
> system events, I see ID 7036 "The DNS Server service entered the stopped
> state," followed by ID 7023, "The DNS Server service terminated with the
> following error: The network is not present or not started." Suggestions
> on where to start?
>


As Jonathan indicated, it appears that the message you are getting, "...The
network is not present or not started," may indicate that the NIC or network
services are not starting first, which is required for DNS and other network
based services. The 7036 and 7023 eventID#s are generic to any services.
We'll need something a little more specific. Do you see any other error
messages in any other event logs?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"Ace Fekay [MCT]" wrote
> Do you see any other error messages in any other event logs?

I see some warnings from the network adapter as the link goes down and back
up on each port before initializing. This happens prior to other services
starting. It's an Intel PRO/1000 PT dual port server adapter configured for
teaming. I tried disabling teaming, but DNS still failed to auto-start.

"Joe Blizzard" <> wrote in message
news:...
> "Ace Fekay [MCT]" wrote
>> Do you see any other error messages in any other event logs?
>
> I see some warnings from the network adapter as the link goes down and
> back up on each port before initializing. This happens prior to other
> services starting. It's an Intel PRO/1000 PT dual port server adapter
> configured for teaming. I tried disabling teaming, but DNS still failed to
> auto-start.
>


Have you checked and tried to eliminate the simple things, such as a bad
wire, connection loose, bad switch port, etc?

Ace

"J de Boyne Pollard" wrote
> This happens prior to other services starting.
>
> How do you know this?

Startup messages from other services appear in the event logs after the
successful NIC initialization message.

"Ace Fekay [MCT]" wrote
> Have you checked and tried to eliminate the simple things, such as a bad
> wire, connection loose, bad switch port, etc?

I've tried different cables and different switch ports. I changed some NIC
parameters (specified link speed instead of autonegotiate for the individual
NICs and disabled 'probes' for the team) and this eliminated all of the NIC
error events, but DNS still doesn't auto start.

"Joe Blizzard" <> wrote in message
news:...
> "Ace Fekay [MCT]" wrote
>> Have you checked and tried to eliminate the simple things, such as a bad
>> wire, connection loose, bad switch port, etc?
>
> I've tried different cables and different switch ports. I changed some NIC
> parameters (specified link speed instead of autonegotiate for the
> individual NICs and disabled 'probes' for the team) and this eliminated
> all of the NIC error events, but DNS still doesn't auto start.
>


How about drivers? Have you considered disabling the team and see if that is
causing it.

Apparently something is holding it up. It's difficult to ascertain.

Ace.

"Ace Fekay [MCT]" wrote
> How about drivers? Have you considered disabling the team and see if that
> is causing it.
>
> Apparently something is holding it up. It's difficult to ascertain.

Disabling teaming didn't help. However, I just disabled the Intel NIC and
installed an old Broadcom NIC and DNS started on reboot, just like it's
supposed to. It appears there's something wonky with my Intel NIC or its
drivers. Armed with that information, I think I'll continue troubleshooting
tomorrow, on company time.

"Joe Blizzard" <> wrote in message
news:...
> "Ace Fekay [MCT]" wrote
>> How about drivers? Have you considered disabling the team and see if that
>> is causing it.
>>
>> Apparently something is holding it up. It's difficult to ascertain.
>
> Disabling teaming didn't help. However, I just disabled the Intel NIC and
> installed an old Broadcom NIC and DNS started on reboot, just like it's
> supposed to. It appears there's something wonky with my Intel NIC or its
> drivers. Armed with that information, I think I'll continue
> troubleshooting tomorrow, on company time.
>


That's good to hear you narrowed it down. Let us know how you make out.

Ace

"Ace Fekay [MCT]" wrote
> Let us know how you make out.

This morning I uninstalled the Intel drivers and started over. With the
Microsoft driver, each NIC in the PRO/1000 PT Dual adapter works fine as a
standalone NIC. I can load the Intel drivers and I'm still good in
standalone, but if I team the NICs, DNS fails to start. Then if I remove the
team and try to return to standalone, DNS fails on a standalone NIC. The
only way I've been able to get it back to working is to uninstall the Intel
drivers and start over again. I've repeated this cycle a couple of times.
Intel support hasn't been any help so far.