Discussion:
DNS Crash errors 4015 & 4004
(too old to reply)
Kurt Leege
2007-08-06 15:26:22 UTC
Permalink
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.
Manfred Zhuang [MSFT]
2007-08-07 11:31:49 UTC
Permalink
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-***@microsoft.com

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-***@microsoft.com

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" <***@dvbny.com>
| 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: <#***@TK2MSFTNGP02.phx.gbl>
| 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.
|
|
|
Kurt Leege
2007-08-07 15:16:45 UTC
Permalink
Thanks for your reply Manfred. I'll try these solutions as I get a chance in
the coming days.

With respect to your questions at the end

1. Errors occur between 3-4pm and 10-11pm each day [the exact time varies
each occurance - but it is always within that frame]

2. There is only one DNS server in our network

3. It is a small network with 9 PC's, 2 network printers and 14 users. Our
server has a two NIC setup with the external NIC connected to a router [and
set up as per the normal setup for this configuration]. The software was
factory installed as SBS 2003 premier SP1. We have not previously had any
problems. We have windows update turned on so we are up to date on all
patches and upgrades. The only 3rd party software we have running constantly
is AVG anti-virus. We also use MAS 90 and Act as server based programs.
Other than that we simply use the server as a file server & Exchange
server - so its resources are not overtaxed. We did recently migrate
exchange and several logs over to the D side of the partition as we were
running low on space, but we did this after the errors began in order to
clear additional space for the SP2 upgrade. The drives have also been
recently defragged.

If the problem persists after attempting these solutions, I'll forward the
requested reports.

Thanks,
Kurt
Post by Manfred Zhuang [MSFT]
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
=============================
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
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
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
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\
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
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.
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.
--------------------
| 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
| 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.
|
|
|
Kurt Leege
2007-08-07 18:51:15 UTC
Permalink
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
Post by Manfred Zhuang [MSFT]
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
=============================
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
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
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
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\
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
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.
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.
--------------------
| 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
| 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.
|
|
|
Manfred Zhuang [MSFT]
2007-08-08 12:49:37 UTC
Permalink
Dear Kurt,

Thank you for your reply.

I understand that you will try the steps soon.

Please take your time and let me know the result at your earliest
convenience.

In answer to your questions, if internal_domain.local cannot be found,
let's just skip it. It is normal.

Regarding the aliases, please delete all of them.

I am sorry for not explaining clearly.

If anything is unclear, please don't hesitate to let me know and I will be
glad to help.

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" <***@dvbny.com>
| References: <#***@TK2MSFTNGP02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: DNS Crash errors 4015 & 4004
| Date: Tue, 7 Aug 2007 14:51:15 -0400
| Lines: 220
| 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: <uRm#***@TK2MSFTNGP03.phx.gbl>
| 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!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:55033
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| 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-***@online.microsoft.com> wrote in message
| news:***@TK2MSFTNGHUB02.phx.gbl...
| > 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-***@microsoft.com
| >
| > 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-***@microsoft.com
| >
| > 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" <***@dvbny.com>
| > | 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: <#***@TK2MSFTNGP02.phx.gbl>
| > | 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.
| > |
| > |
| > |
| >
|
|
|
Manfred Zhuang [MSFT]
2007-08-14 11:22:41 UTC
Permalink
From: Kurt Leege [mailto:***@dvbny.com]
Sent: Monday, August 13, 2007 8:15 AM
To: Manfred Zhuang (CS&S)
Subject: RE: Follow Up For MS Public Newsgroup Post (DNS Crash errors 4015
& 4004) with Manfred Zhuang ( 40101073)

Hi Manfred:

I sent you an e-mail on Saturday with the log files you requested as I had
no luck with the four solutions.

I received a delay notification this morning. Please let me know if and
when you receive the message. If for some reason you don't, I will resend.

Regards,
Kurt
Manfred Zhuang [MSFT]
2007-08-14 11:25:46 UTC
Permalink
Hello Kurt,

Thank you for your reply.

I understand that you sent me the log files on Saturday.

Unfortunately, I did not receive them.

Would you please resend them? Thank you for your effort.

In addition, I would like to confirm that have you compressed them? Please
also let me know the size of the attachment.

I am sorry for the inconvenience.

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.
--------------------
| Newsgroups: microsoft.public.windows.server.sbs
| From: v-***@online.microsoft.com (Manfred Zhuang [MSFT])
| Organization: Microsoft
| Date: Tue, 14 Aug 2007 11:22:41 GMT
| Subject: Re: DNS Crash errors 4015 & 4004
| X-Tomcat-NG: microsoft.public.windows.server.sbs
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
|
|
|
| From: Kurt Leege [mailto:***@dvbny.com]
| Sent: Monday, August 13, 2007 8:15 AM
| To: Manfred Zhuang (CS&S)
| Subject: RE: Follow Up For MS Public Newsgroup Post (DNS Crash errors
4015
| & 4004) with Manfred Zhuang ( 40101073)
|
| Hi Manfred:
|
| I sent you an e-mail on Saturday with the log files you requested as I
had
| no luck with the four solutions.
|
| I received a delay notification this morning. Please let me know if and
| when you receive the message. If for some reason you don't, I will resend.
|
| Regards,
| Kurt
|
Kurt Leege
2007-08-15 20:39:46 UTC
Permalink
Hi Manfred:

The larger file is already compressed [6MB size] and will not compress
further using a zip program.

The e-mail appears to have gone through after I hit 'force connect' on the
e-mail in the smtp queue.

Please let me know if you have received it.

Regards,
Kurt
Post by Manfred Zhuang [MSFT]
Hello Kurt,
Thank you for your reply.
I understand that you sent me the log files on Saturday.
Unfortunately, I did not receive them.
Would you please resend them? Thank you for your effort.
In addition, I would like to confirm that have you compressed them? Please
also let me know the size of the attachment.
I am sorry for the inconvenience.
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.
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.
--------------------
| Newsgroups: microsoft.public.windows.server.sbs
| Organization: Microsoft
| Date: Tue, 14 Aug 2007 11:22:41 GMT
| Subject: Re: DNS Crash errors 4015 & 4004
| X-Tomcat-NG: microsoft.public.windows.server.sbs
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
|
|
|
| Sent: Monday, August 13, 2007 8:15 AM
| To: Manfred Zhuang (CS&S)
| Subject: RE: Follow Up For MS Public Newsgroup Post (DNS Crash errors
4015
| & 4004) with Manfred Zhuang ( 40101073)
|
|
| I sent you an e-mail on Saturday with the log files you requested as I
had
| no luck with the four solutions.
|
| I received a delay notification this morning. Please let me know if and
| when you receive the message. If for some reason you don't, I will resend.
|
| Regards,
| Kurt
|
Manfred Zhuang [MSFT]
2007-08-16 08:44:03 UTC
Permalink
From: Manfred Zhuang (CS&S)
Sent: Thursday, August 16, 2007 1:43 AM
To:
Subject: Follow Up For MS Public Newsgroup Post (DNS Crash errors 4015 &
4004) with Manfred Zhuang ( 40101073)

Hello Kurt,

Thank you for your reply.

I understand that the files still could not be sent to me.

Based on current situation, I have created a workspace for you.

Please visit following URL to access it"

Workspace URL:
(https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=2261dfd7-8c98-44b0-
be40-e5efcbf434f1)
Note: Due to differences in text formatting with various email clients, the
workspace link above may appear to be broken. Please be sure to include all
text between '(' and ')' when typing or copying the workspace link into
your browser.

The password is *********** (Removed)

Please upload the files and then send a separate email to let me know.

Your time and effort will be appreciated.

Best regards,

Manfred Zhuang(MSFT)
v-***@microsoft.com
Microsoft Online Newsgroup Support
Manfred Zhuang [MSFT]
2007-08-17 07:07:35 UTC
Permalink
From: Kurt
Sent: Thursday, August 16, 2007 11:47 AM
To: Manfred Zhuang (CS&S)
Subject: RE: Follow Up For MS Public Newsgroup Post (DNS Crash errors 4015
& 4004) with Manfred Zhuang ( 40101073)

Thanks for your help Manfred. I just uploaded the two files. Please let me
know if you can come up with a solution.

Also, if you could copy an e-mail with any solutions to ***@verizon.net
that would be great, as I won't be returning to the office until Monday.

Regards,
Kurt
Manfred Zhuang [MSFT]
2007-08-17 11:12:10 UTC
Permalink
Hello Kurt,

Thank you for uploading the files.

After checking them, I found the data of 4015 error is 00000051.

It is most likely caused by that DNS server is listening on both the
internal and external adapters.

I suggest you check following setting:

1. Open DNS management.
2. Right click your server and click Properties.
3. Please check how many IP addresses the server is listening on.

Please ensure it only listens on the internal NIC.

After that, please delete all records in forward lookup zone that reference
the external adapter address.

Please try the above steps at your earliest convenience. If you have any
concern, please feel free to 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.
--------------------
| Newsgroups: microsoft.public.windows.server.sbs
| From: v-***@online.microsoft.com (Manfred Zhuang [MSFT])
| Organization: Microsoft
| Date: Fri, 17 Aug 2007 07:07:35 GMT
| Subject: Re: DNS Crash errors 4015 & 4004
| X-Tomcat-NG: microsoft.public.windows.server.sbs
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
|
|
|
| From: Kurt
| Sent: Thursday, August 16, 2007 11:47 AM
| To: Manfred Zhuang (CS&S)
| Subject: RE: Follow Up For MS Public Newsgroup Post (DNS Crash errors
4015
| & 4004) with Manfred Zhuang ( 40101073)
|
| Thanks for your help Manfred. I just uploaded the two files. Please let
me
| know if you can come up with a solution.
|
| Also, if you could copy an e-mail with any solutions to ***@verizon.net
| that would be great, as I won't be returning to the office until Monday.
|
| Regards,
| Kurt
|
Kurt Leege
2007-08-17 16:14:16 UTC
Permalink
Checked the settings, DNS is only listening on the internal NIC and there
are no references to the external adapter address in the Forward Lookup
zone.

Any further thoughts? What kinda bugs me is this just started randomly,
without any system changes. Is that a clue?

Thanks for your patience and help with this. It is much appreciated

Kurt
Post by Manfred Zhuang [MSFT]
Hello Kurt,
Thank you for uploading the files.
After checking them, I found the data of 4015 error is 00000051.
It is most likely caused by that DNS server is listening on both the
internal and external adapters.
1. Open DNS management.
2. Right click your server and click Properties.
3. Please check how many IP addresses the server is listening on.
Please ensure it only listens on the internal NIC.
After that, please delete all records in forward lookup zone that reference
the external adapter address.
Please try the above steps at your earliest convenience. If you have any
concern, please feel free to let me know.
Best regards,
Manfred Zhuang(MSFT)
Microsoft Online Newsgroup Support
Get Secure! - www.microsoft.com/security
Manfred Zhuang [MSFT]
2007-08-20 12:07:32 UTC
Permalink
Hello Kurt,

Thank you for your reply.

I understand that the DNS server is only listening on the internal adapter,
but the issue persists.

Firstly I am sorry for the inconvenience that you are experiencing and I
appreciate your time and effort spent on this issue.

It seems that the issue is quite complex and we may need more time to
troubleshoot it.

Your patience will be appreciated.

Let's try following steps to narrow down the cause:

1. Windows Server 2003 Domain Controllers hosting AD-Integrated DNS zones
may sporadically fail to load the DNS zones after reboot. When this occurs
the dnsmgmt.msc snap-in displays a Red "X" for the server name instead of
the DNS zones and connectivity is impacted. When this issue occurs the DNS
Event log will also log Event ID 4015. Determine if LDAP is working
correctly on the DC and if the zones can be viewed using LDP.exe or other
LDAP capable tools.

a) Click Start, select RUN, type "LDP.exe" and click Open
b) Click Connection and select Connect
c) Enter the name of the DC, enter port 389 and click OK
d) Click Connection and select Bind.
e) Click on View and select Tree and for BaseDN enter the DN for your zone
using the example below and click OK:

DC=<zoneName.com>,CN=MicrosoftDNS,DC=ForestDnsZones,DC=<rootdomain>,DC=<com>

f) Double-click on the

DC=<zoneName.com>,CN=MicrosoftDNS,DC=ForestDnsZones,DC=<rootdomain>,DC=<com>
when it populates in the left pane to see if the records are present.

2. If this object does not exist, please let me know. If the zones are
viewable in LDP.exe and restarting the DNS Server service does not cause
the zones to load, this issue is likely due to a timing issue where DNS
fails to attempt retries at loading the zones when the LDAP server is busy.
Some of these failures are caused by an inability to locate the zone object
in the directory. At the DNS server, use LDIFDE to export the zone to see
if it reports an error. The command to type in the command prompt will be
similar to this:

Ldifde -f outputFile.txt -d
DC=<zonename.com>,CN=MicrosoftDNS,DC=ForestDnsZones,DC=<rootdomain>,DC=<com>

3. Please let me know if there is any error encountered.

In addition, please send following files to v-***@microsoft.com:

1. DNS database
===========
To dump the DNS database, please use the following commands under command
prompt:

DNSCMD /ExportZone _msdcs.***.local msdcs.txt
DNSCMD /ExportZone ****.local dvbnewyork.txt

Then get the two files located in C:\Windows\System32\DNS for further
investigation. For more information regarding this utility, please refer to
the following article:

304489 Extracting DNS Active Directory-Integrated Zone Files
http://support.microsoft.com/?id=304489

2. Get DNS debug log:
===============
Select and enable debug logging options on the DNS server; Windows Server
2003
http://technet2.microsoft.com/windowsserver/en/library/9b82dd18-e7b2-4c36-b9
81-471b7b762c461033.mspx?mfr=true

NOTE: Please specify the name and the path of the log file.

After enabling the DNS debug log, reproduce the issue and then send me the
log file.

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" <***@dvbny.com>
| References: <#***@TK2MSFTNGP02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
<uRm#***@TK2MSFTNGP03.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
<***@TK2MSFTNGP02.phx.gbl>
<MKatdG#***@TK2MSFTNGHUB02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
<***@TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: DNS Crash errors 4015 & 4004
| Date: Fri, 17 Aug 2007 12:14:16 -0400
| Lines: 46
| 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: <***@TK2MSFTNGP02.phx.gbl>
| 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:57263
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Checked the settings, DNS is only listening on the internal NIC and there
| are no references to the external adapter address in the Forward Lookup
| zone.
|
| Any further thoughts? What kinda bugs me is this just started randomly,
| without any system changes. Is that a clue?
|
| Thanks for your patience and help with this. It is much appreciated
|
| Kurt
|
|
| "Manfred Zhuang [MSFT]" <v-***@online.microsoft.com> wrote in message
| news:***@TK2MSFTNGHUB02.phx.gbl...
| > Hello Kurt,
| >
| > Thank you for uploading the files.
| >
| > After checking them, I found the data of 4015 error is 00000051.
| >
| > It is most likely caused by that DNS server is listening on both the
| > internal and external adapters.
| >
| > I suggest you check following setting:
| >
| > 1. Open DNS management.
| > 2. Right click your server and click Properties.
| > 3. Please check how many IP addresses the server is listening on.
| >
| > Please ensure it only listens on the internal NIC.
| >
| > After that, please delete all records in forward lookup zone that
| > reference
| > the external adapter address.
| >
| > Please try the above steps at your earliest convenience. If you have any
| > concern, please feel free to let me know.
| >
| > Best regards,
| >
| > Manfred Zhuang(MSFT)
| > Microsoft Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
|
|
|

Continue reading on narkive:
Loading...