Re: DNS Crash errors 4015 & 4004
- From: "Kurt Leege" <kurt@xxxxxxxxx>
- Date: Tue, 7 Aug 2007 14:51:15 -0400
Also - quick question about solution 2.
under internal_domain.local -> System -> MicrosoftDNS
I have 2 folders. There is no internal_domain.local file or folder. The
folders are
1. 16.168.192.in-addr.arpa
2. RootDNSServers
The first folder is a fragment of our domain IP in reverse. Is that the
internal_domain.local file I need to delete?
And in _msdcs.internal_domain.local there are 2 aliases. Do I delete both?
Thanks,
Kurt
"Manfred Zhuang [MSFT]" <v-mzhuan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:xCcuQaO2HHA.5836@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Kurt,
Thank you for posting here.
From your post, I understand that DNS service crashes twice every day,
error 4015 and 4004 are received. After installing SP2, the issue
persists.
No software and hardware change before the issue occurred. If I have
misunderstood your concern, please feel free to correct me.
This issue can be caused by several factors. I suggest you try following
steps to see if it works:
Suggestion 1: Re-running CEICW on SBS server:
=============================
Let's re-run CEICW to reset the network configuration. Please refer to
following article to do this.
How to configure Internet access in Windows Small Business Server 2003
http://support.microsoft.com/kb/825763/en-us
Suggestion 2: Check the DNS zones
=====================
1. Open Active Directory Users and Computers, click View, Advanced
features.
2. Expand internal_domain.local -> System -> MicrosoftDNS and delete
internal_Domain.local.
3. Go to DNS, expand forward lookup zones, click on
_msdcs.internal_domain.local and delete the Alias for
server.internal_domain.local (the long GUID entry).
4. Restart Netlogon service in the services.mcs
5. If you find that the you are missing the _msdcs zone under
internal_domain.local in your DNS service, create a new delegation by
performing the following:
a. Right click on internal_domain.local,
b. select new, then delegation, click next on the wizard,
c. under delegated domain, type in _msdcs and click next,
d. clck add and browse to the server's A record under forward lookup
zones,
internal_domain.local,
e. click ok and finish.
Suggestion 3: Prepare a Clean Boot environment.
=================
1. Click Start and Click Run, and in the "Open" line, type in "MSCONFIG"
(without the quotation marks) and click OK.
2. Under the Service tab, check "Hide All Microsoft Services", and then
click "Disable All" button. In this way, we can disable all the services
which belong to third-party programs.
3. Under the Startup tab, click "Disable All" button.
4. Click OK.
5. Choose Yes to restart the computer.
6. Check "Don't show this message or launch the system configuration
utility when Windows starts".
7. If it is convenient, please monitor the situation in the clean boot
environment for several days and check if he issue reoccurs.
NOTE: We can check on Normal Startup in the General tab to roll back to
Normal Mode after we get this issue resolved.
Suggestion 4: Remove and recreate DNS zone
===========================
1. Click start -> Administrative Tools -> Click DNS
2. Locate to forward lookup zone, and right click yourdomain.local, click
delete. click yes, also please delete _msdcs.domain.local if exists.
3. Right click server and click clear cache.
4. Input net stop netlogon in the command prompt.
5. Delete netlogon.dnb and netlogon.dns files under
%windir%\system32\config folder, and also delete domain.com.dns and
_msdcs.domain.com.dns under %windir%\system32\dns folder (if exists, not
under backup folder).
6. Open DNS manager. Right click forward lookup zone, click new zone¡,
follow the wizard to create a new primary zone named yourdomain.local
7. Open command prompt, input following commands:
net start netlogon
ipconfig /flushdns
ipconfig /registerdns
8. Then check the whether the PTR record exists, if not please create it.
9. Please check the issue again.
If the problem could not be resolved by above steps, please help me gather
following information:
1. Please let me know the accurate time when the issue happened.
2. How many DNS servers are in the network?
3. Would you please let me know the detailed information of the network
topology?
4. Please send me the DS mps report for further analysis.
a. Visit
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_DirSvc.EXE to download the file.
b. Run the MPSRPT_DirSvc.exe on the server box.
c. Wait for 10~15 minutes.
d. Open Windows explorer, navigate to
%SYSTEMROOT%\MPSReports\DirSvc\Logs\cab\
e. Send the .cab file directly to me at v-mzhuan@xxxxxxxxxxxxx
5. Please also send me the DNS record with following steps.
1. In the DNS console, expand your server and the forward Lookup Zones
2. Right click your domain name and click properties
3. In the General tab, please click change
4. Please uncheck the checkbox of "Store the zone in Active Directory"
5. Click OK
6. Open %systemroot%\system32\dns\ folder
7. Send the yourdomain.dns file to v-mzhuan@xxxxxxxxxxxxx
If you have any questions or concerns related to this issue, please let me
know.
Best regards,
Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
| From: "Kurt Leege" <kurt@xxxxxxxxx>
| Subject: DNS Crash errors 4015 & 4004
| Date: Mon, 6 Aug 2007 11:26:22 -0400
| Lines: 17
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| Message-ID: <#57km4D2HHA.6128@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: 248-186.customer.cloud9.net 168.100.248.186
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:54733
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| We've been experiencing a DNS crash twice a day [at around the same
time]
| for the last several weeks. It begins with the local company web page
going
| down & then a series of 4015 and 4004 errors in the DNS log, after which
all
| network connectivity is cut off until a reboot.
|
| We checked event ID which referred us to microsoft's 'fix' - installing
SP2.
| So we upgraded the server, but still have the same problem. The current
| version is SBS2003 premium version SP2 with Exchange SP2.
|
| Also - this problem cropped up out of the blue. There were no software
or
| hardware changes to the server directly prior to the advent of this
issue.
|
| Does anyone have suggestions as to what may be causing this?
|
| Thanks.
|
|
|
.
- Follow-Ups:
- Re: DNS Crash errors 4015 & 4004
- From: Manfred Zhuang [MSFT]
- Re: DNS Crash errors 4015 & 4004
- References:
- DNS Crash errors 4015 & 4004
- From: Kurt Leege
- RE: DNS Crash errors 4015 & 4004
- From: Manfred Zhuang [MSFT]
- DNS Crash errors 4015 & 4004
- Prev by Date: Re: Problem with incoming faxes being routed to a document library
- Next by Date: Re: WM5/ActiveSync Admin problem and solution from MS
- Previous by thread: Re: DNS Crash errors 4015 & 4004
- Next by thread: Re: DNS Crash errors 4015 & 4004
- Index(es):
Relevant Pages
|