Hi everyone,

I am wondering if someone could fill me in with some info about dns.exe

First some background info.

We are getting errors regarding non-paged memory allocation (event id 2019)
and I have read quite a bit about it, and I understand it's caused by an
application not giving non-paged memory back to the system.

Through my readings I found a note that any 'normal application should
typically not use much over 100K from the NP Pool.

Looking over my running processes, the only application which seems to have
WAY too much is dns.exe - which curently has 4,812K of non-paged memory. The
other thing that caught my attention is dns.exe has 5,205 handles as well.

Can someone tell me if this is normal for dns.exe or if there is some
explination for this behaviour?

Thanks in advance,

-Shaz ¬_¬

In news:BDAE22B8-931D-45E0-919B-0B9E4E6500EE@microsoft.com,
Lord Shaz <Lord Shaz@discussions.microsoft.com> requesting assistance, typed
the following:

Quote:

Hi everyone, I am wondering if someone could fill me in with some info about dns.exe First some background info. We are getting errors regarding non-paged memory allocation (event id 2019) and I have read quite a bit about it, and I understand it's caused by an application not giving non-paged memory back to the system. Through my readings I found a note that any 'normal application should typically not use much over 100K from the NP Pool. Looking over my running processes, the only application which seems to have WAY too much is dns.exe - which curently has 4,812K of non-paged memory. The other thing that caught my attention is dns.exe has 5,205 handles as well. Can someone tell me if this is normal for dns.exe or if there is some explination for this behaviour? Thanks in advance, -Shaz ¬_¬

That is normal after the KB951748 DNS security update. Read up on it...

The DNS patch will reserve 2500 ephemeral UDP ports. When you run a
netstat -ab, it will display the 2500 UDP ports that have been
reserved, but not necessarily in use. This is part of the memory
consumption. I've noticed the following (your mileage may vary):

dns.exe Before After
Mem usage 9758K 36,232K
Peak Mem 10,208K 36,584K
Paged Pool 71K 798K
NP Pool 17K 4,833K
Handles 238 5,217
Threads 20 20


Read up on it...

MS08-037: Description of the security update for DNS in Windows Server 2003,
in Windows XP, and in Windows 2000 Server (client side): July 8, 2008:
http://support.microsoft.com/?id=951748

MS08-037: Vulnerabilities in DNS could allow spoofing
http://support.microsoft.com/default.aspx/kb/953230

How to reserve a range of ephemeral ports on a computer that is running
Windows Server 2003 or Windows 2000 Server
http://support.microsoft.com/kb/812873

You experience issues with UDP-dependent network services after you install
DNS Server service security update 953230 (MS08-037)
http://support.microsoft.com/default.aspx/kb/956188

Some Services May Fail to Start or May Not Work Properly After Installing
MS08-037 (951746 and 951748)
http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx

SBS Services failing after MS08-037 - KB951746 and 951748
http://msmvps.com/blogs/thenakedmvp/archive/2008/07/18/sbs-services-failing-after-ms08-037-kb951746-and-951748.aspx

--
Regards,
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

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

Infinite Diversities in Infinite Combinations

OK thanks for your response :-)

I'll keep looking for the cause of the 2019 elsewhere.


Thanks again,

-Shaz ¬_¬

"Ace Fekay [MVP Direcrtory Services]" wrote:

Quote:

In news:BDAE22B8-931D-45E0-919B-0B9E4E6500EE@microsoft.com, Lord Shaz <Lord Shaz@discussions.microsoft.com> requesting assistance, typed the following: Hi everyone, I am wondering if someone could fill me in with some info about dns.exe First some background info. We are getting errors regarding non-paged memory allocation (event id 2019) and I have read quite a bit about it, and I understand it's caused by an application not giving non-paged memory back to the system. Through my readings I found a note that any 'normal application should typically not use much over 100K from the NP Pool. Looking over my running processes, the only application which seems to have WAY too much is dns.exe - which curently has 4,812K of non-paged memory. The other thing that caught my attention is dns.exe has 5,205 handles as well. Can someone tell me if this is normal for dns.exe or if there is some explination for this behaviour? Thanks in advance, -Shaz ¬_¬ That is normal after the KB951748 DNS security update. Read up on it... The DNS patch will reserve 2500 ephemeral UDP ports. When you run a netstat -ab, it will display the 2500 UDP ports that have been reserved, but not necessarily in use. This is part of the memory consumption. I've noticed the following (your mileage may vary): dns.exe Before After Mem usage 9758K 36,232K Peak Mem 10,208K 36,584K Paged Pool 71K 798K NP Pool 17K 4,833K Handles 238 5,217 Threads 20 20 Read up on it... MS08-037: Description of the security update for DNS in Windows Server 2003, in Windows XP, and in Windows 2000 Server (client side): July 8, 2008: http://support.microsoft.com/?id=951748 MS08-037: Vulnerabilities in DNS could allow spoofing http://support.microsoft.com/default.aspx/kb/953230 How to reserve a range of ephemeral ports on a computer that is running Windows Server 2003 or Windows 2000 Server http://support.microsoft.com/kb/812873 You experience issues with UDP-dependent network services after you install DNS Server service security update 953230 (MS08-037) http://support.microsoft.com/default.aspx/kb/956188 Some Services May Fail to Start or May Not Work Properly After Installing MS08-037 (951746 and 951748) http://blogs.technet.com/sbs/archive/2008/07/17/some-services-may-fail-to-start-or-may-not-work-properly-after-installing-ms08-037-951746-and-951748.aspx SBS Services failing after MS08-037 - KB951746 and 951748 http://msmvps.com/blogs/thenakedmvp/archive/2008/07/18/sbs-services-failing-after-ms08-037-kb951746-and-951748.aspx -- Regards, Ace This posting is provided "AS-IS" with no warranties or guarantees and confers no rights. Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP Microsoft MVP - Directory Services Microsoft Certified Trainer For urgent issues, you may want to contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers. Infinite Diversities in Infinite Combinations

In news:27711CAE-C240-43ED-B0B5-7B9BB8B37B94@microsoft.com,
Lord Shaz <LordShaz@discussions.microsoft.com> requesting assistance, typed
the following:

Quote:

OK thanks for your response :-) I'll keep looking for the cause of the 2019 elsewhere. Thanks again, -Shaz ¬_¬

Sorry for not responding about the 2019. What was the Source Name in the
event? There are two possible ones I found relating to memory leaks. The
main one, I believe is what you are getting, Source = Srv. This indicates an
application is causing it. Default system services are not usually the
cause, but can be, such as the VSS, or even the index service. Mostly what
I've seen is other Microsoft or third party apps installed that can be
causing it. This all depends on what is installed on the machine, such as
SQL, Exchange, Antivirus software, printers, and many others.

To troubleshoot which one it is, take a look at this link which provides
various ways and suggestions to isolate the cause.

http://eventid.net/display.asp?eventid=2019&eventno=661&source=Srv&phase=1

Ace

OK Thanks, I'll check it out

Yes the source is Srv



"Ace Fekay [MVP Direcrtory Services]" wrote:

Quote:

In news:27711CAE-C240-43ED-B0B5-7B9BB8B37B94@microsoft.com, Lord Shaz <LordShaz@discussions.microsoft.com> requesting assistance, typed the following: OK thanks for your response :-) I'll keep looking for the cause of the 2019 elsewhere. Thanks again, -Shaz ¬_¬ Sorry for not responding about the 2019. What was the Source Name in the event? There are two possible ones I found relating to memory leaks. The main one, I believe is what you are getting, Source = Srv. This indicates an application is causing it. Default system services are not usually the cause, but can be, such as the VSS, or even the index service. Mostly what I've seen is other Microsoft or third party apps installed that can be causing it. This all depends on what is installed on the machine, such as SQL, Exchange, Antivirus software, printers, and many others. To troubleshoot which one it is, take a look at this link which provides various ways and suggestions to isolate the cause. http://eventid.net/display.asp?eventid=2019&eventno=661&source=Srv&phase=1 Ace

In news:506F6309-D311-4D2D-BE2F-1DC51A76584E@microsoft.com,
Lord Shaz <LordShaz@discussions.microsoft.com> requesting assistance, typed
the following:

Quote:

OK Thanks, I'll check it out Yes the source is Srv

Let me know how you make out.

Ace