Re: DNS service causing DC to hang on reboot

Well, now it won't boot up correctly and I have all 3 updates removed. Maybe
I should have removed them in the original order like I did the first time, I
don't know. I am going to have to put my DNS server back to Manual, I think
, until I can figure this out. This is SO frustrating!!! Gosh, I hope that
works at least...

"Saral6978" wrote:

By the way - no error messages are showing up at all, probably because it
can't get booted up all the way...

"Kerry Brown" wrote:

Are there any errors in the event logs? I would suspect that the DNS service
may indirectly be causing the problem. My suspicion is that DNS is using a
port that another service or program needs causing that process to fail. If
you can figure out what that process is then reserve the ports it needs this
may fix the problem. The again it may be your system is just not compatible
with KB945553.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/


"Saral6978" <Saral6978@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:78ACD16C-0E68-45A2-A572-149CD6C96B89@xxxxxxxxxxxxxxxx
Removed Updates KB948881, KB948590 and KB945553 (in that order) and then
set
my DNS server service to Automatic. Rebooted, and it booted up
successfully
and did not hang. Next, reinstalled KB948590 and boot was successful.
Next,
installed KB948881, and boot was successful. Finally, reapplied KB945553
(specific DNS update), which I downloaded manually and installed rather
than
use WSUS or Microsofts Update page, and lo and behold, my server won't
boot.
So, it's definitely the KB945553 update causing my problem. I'm going to
remove it and keep the other 2 and then contact Microsoft in the
morning...I'm not sure what more I can do about how to fix it if the
update
is causing DNS to not work properly during startup...

"Saral6978" wrote:

I attempted to reserve port 53, but I realized that probably wouldn't
work
because random ports start at 1024, so 53 shouldn't be affected. I set
the
DNS server service back to automatic and it hung again on "Preparing
Network
Connections". Honestly, I'm not sure what else to try at all. I can
attempt
to remove my latest Windows patches, but if I remove 945553, I have to
also
remove 948590 and 948881 because they appear tied to 945553. I really
don't
want to call Microsoft and open a case #, but I'm not sure what else
could
have hosed my DNS server service. Any other ideas? Anyone?

"Kerry Brown" wrote:

If it fixes the problem you would have to find out what port DNS is
clobbering then make an exception for it. It is important to install
the DNS
patches. They do cause some problems on some systems but the problems
can be
worked around. It just takes some work :-)

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/


"Saral6978" <Saral6978@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75E002F9-B88F-4CBD-8CD0-EB460C08161C@xxxxxxxxxxxxxxxx
I think I might have found the update causing the problem:

Microsoft Security Bulletin MS08-020 – Important
Vulnerability in DNS Client Could Allow Spoofing (945553)

This is one of the 5 updates I installed on this particular server on
9/3,
and the only one relating to DNS. I do have this update on another
Domain
Controller and the DNS service however is not doing the same thing.
That
server boots up just fine. But, perhaps it is a start to figuring
out
this
issue. Maybe I will remove the update and see if that fixes the
problem...


"Kerry Brown" wrote:

There may be an issue with the recent DNS patches conflicting with
other
network services.

http://support.microsoft.com/kb/956188

http://support.microsoft.com/kb/956189

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/
http://vistahelpca.blogspot.com/


"Saral6978" <Saral6978@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D585D55D-D32B-4F05-A330-8DB5A2CFF3D1@xxxxxxxxxxxxxxxx
*posting here and in the DNS forum*

DNS is causing my Domain Controller (Win2003R2) to hang on reboot.
It
freezes on "Preparing Network Connections". To determine it was
DNS, I
booted into Safe mode and disabled DHCP and DNS. The server
booted
normally
and I was able to log in. I then enabled DHCP and rebooted server
and
the
server booted normally. After I logged in, I then changed the DNS
service
to
manual and started the service and it started successfully and my
forward
and
reverse zones came up (active directory integrated) and all AD
errors
were
cleared on this particular server (I have a total of 4 DCs among 3
different
sites).

Problems started a couple of weeks ago, when after a reboot, DHCP
and
DNS
were not working. I had to manually start DHCP and although DNS
was
running,
the zones were gone. After I restarted DNS, the zones reappeared
and
all
was
fine. The next week DHCP was fine, but again, the zones in DNS
disappeared
until I restarted the service. Now this week, DNS won't even
allow the
server to boot. Once DNS is started, replication appears to be
working
just
fine between my sites, and my workstations and servers are happy.

Any suggestions on fixing the startup issue when DNS is set to
automatic?
Seeing as though this is a DC, I probably can't just uninstall and
reinstall
DNS, can I? I will probably be running dcdiag to help confirm
things
are
okay between all the DCs, but any other suggestions would be
helpful if
you
have them.

I'm just not sure why the DNS service is freezing my server upon
startup.

Thank you!

Sara









.