DNS Change SocketPoolSize to recommended 2500 generates 7023

Question

_{Thursday, January 13, 2011 1:01 PM}

Hi Guys,
Was running the Best Practice Analyzer for the DNS role on my domain controller (w2k8R2), and it said I should change the DNS SocketPoolSize to 2500 (was 625)

I run the command  dnscmd /Config /SocketPoolSize 2500, which works fine but when I restart the DNS service, an error is generated and SocketPoolSize is reverted back to 625:

The DNS Server service terminated with the following error:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

I have found articles regarding the error, if my pool is over 9000, but cant find anything related to my issue.

Can anyone lead me in a direction? Thanks :)

All replies (5)

_{Tuesday, January 18, 2011 2:07 PM ✅Answered}

hi again. Just wanted to say that the RPC ports have been limited for some reason on my server.

The following commands from an elevated prompt solved the issue:

netsh interface ipv4 set dynamicportrange protocol=tcp startport=49152 numberofports=16384
netsh interface ipv4 set dynamicportrange protocol=udp startport=49152 numberofports=16384
netsh interface ipv6 set dynamicportrange protocol=tcp startport=49152 numberofports=16384
netsh interface ipv6 set dynamicportrange protocol=udp startport=49152 numberofports=16384

Thanks for your help anyway Tiger :)

_{Friday, January 14, 2011 2:51 AM}

Hi Ennova,

Thanks for posting here.

2500 is the default DNS Socket Pool Size value on Windows server 2008 R2. I suspect that for system steady reason BPA will always suggest to use system default settings, so this is the reason why it popped this prompt.

Meanwhile, could you verify the current value setting of registry key SocketPoolSize where under patch “ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\DNS\Parameters “, please manually modify it to the value you want ,restart computer and check if this issue persist.

For more information please refer to the link below:

DNS Socket Pool

http://technet.microsoft.com/en-us/library/ee683907(WS.10).aspx

Thanks.

Tiger Li

TechNet Subscriber Support in forum

If you have any feedback on our support, please contact [email protected]

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

_{Friday, January 14, 2011 7:16 AM}

Hi Tiger,

Thanks for your answer :)

The registry is configured to use 625. If i change it to 2500 and rerun the baseline, I get the warning:

Title:
DNS: The socket pool should be enabled with recommended settings.

Severity:
Warning

Date:
1/14/2011 8:06:18 AM

Category:
Configuration

Issue:
The value of MaxUserPort in the Windows Registry is configured to a value of 2024.

Impact:
The DNS server is more vulnerable to DNS spoofing attacks.

Resolution:
Enable the socket pool and configure a recommended value for MaxUserPort.

More information about this best practice and detailed resolution procedures: http://go.microsoft.com/fwlink/?LinkId=188782

I dont know why it says 2024, when I type 2025 in the registry. However, if I restart the DNS service. It fails with the same error, and reverts back to 625 for some reason. The other DC (have only 2 in my hyper-v cluster domain) has the recommended value of 2500.

Got any other suggestions?

_{Monday, January 17, 2011 4:27 AM}

Hi Ennova,

Thanks for update.

The warning indicate that key MaxUserPort has been modified to unrecommended value setting and I think this is a new issue that nothing to do with SocketPoolSize setting.

In my view , I’d suggest you to change back these two keys to default value system setting, after that restart server and reperform BPA and check if this issue will persist.

MaxUserPort :5000

SocketPoolSize:2500

MaxUserPort

http://technet.microsoft.com/en-us/library/cc938196.aspx

When you try to connect from TCP ports greater than 5000 you receive the error 'WSAENOBUFS (10055)'

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

Thanks.

Tiger Li

TechNet Subscriber Support in forum

If you have any feedback on our support, please contact [email protected]

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

_{Tuesday, January 18, 2011 9:27 AM}

Hi Tiger,

The problem is that I cant change to recommended values. If I do, I get the error stated in the initial post. Thats the whole issue :)

Ill create a MS ticket and update this post when I have the result.