Shulou(Shulou.com)06/01 Report--

What this article shares with you is how tcpsvcs.exe uses ultra-high virtual memory. The editor thinks it is very practical, so I share it with you. I hope you can get something after reading this article. Let's take a look at it.

Failure phenomenon:

The company has a server for DHCP services + file sharing services and the operating system is windows server 2003 Enterprise Edition + SP2. Open the task manager and find a process called tcpsvcs.exe that consumes about 1.9 gigabytes of virtual memory. Compared with another server that uses similar functions, the process only uses less than 10m of virtual memory, which is obviously abnormal.

Fault handling process and causes:

Search the Internet for information about tcpsvcs.exe and get the explanation: "tcpsvcs.exe is part of the Microsoft Windows network component. This system process is used for computers to use dedicated TCP/IP network services, such as DHCP, simple TCP and printing services. This program is very important for the normal operation of your system."

Further, open a command prompt window, run the tasklist / svc command, view the services associated with each process, and see the following results:

Svchost.exe 1904 TapiSrv

Svchost.exe 1916 TermService

Tcpsvcs.exe 2032 DHCPServer

Mcshield.exe 2076 McShield

Svchost.exe 2240 W3SVC

As you can see, on this machine, tcpsvcs.exe is only related to DHCP services.

An attempt was made to restart the DHCP service and found that the virtual memory immediately returned to normal. The next morning, I checked again and found that the virtual memory reached 1.9 gigabytes again. Compare the relevant parameters set in the DHCP service with another normal DHCP server, and no exception is found.

Turn to the encyclopedia of the Internet, enter relevant content to search, and found nothing valuable. Also visit the Microsoft support and help center http://support.microsoft.com, after searching, found a knowledge base article http://support.microsoft.com/kb/939928/zh-cn which is very close to the situation I described. According to the article: "this problem will occur because the Dnsapi.dll module does not manage some memory resources correctly." Also, if you turn off the DNS dynamic update setting in the DHCP configuration parameters, this problem will not occur. After testing, it was found that this was indeed the case with me.

Solution:

Method 1: disable the DNS dynamic update function of DHCP

Click start, click run, type dhcpmgmt.msc, and then click OK

2. In the console tree, right-click the node corresponding to the DHCP server, and then click Properties

On the DNS tab, click to clear the check box to enable DNS dynamic updates according to the following settings, and then click OK

4. Restart DHCP server service. For example, at a command prompt, type the following command, and then press ENTER: Net stopDHCPServer & & Netstart DHCPServer

This method is suitable for situations where there is no need for DNS dynamic updates. However, if there is an internal DNS service, and if you need to update the mapping between the machine name and IP address of the DHCP client to the DNS service through the DNS service, in order to achieve the requirement of accessing the internal computer through the machine name, this function cannot be disabled.

Method 2: update the patch

Microsoft has a patch for this issue, but since the SP3 service pack for windows server 2003 has not yet been released, it can only be downloaded separately. The download method is as follows:

1. Open the knowledge base article http://support.microsoft.com/kb/939928/zh-cn

2. After clicking "available hotfix patches" at the top of the page, you will automatically jump to the corresponding download page.

3. Select the appropriate version of the patch, enter your email address and submit it. The corresponding download address will be sent to the mailbox you filled in. Just click the description and link of the email to download.

This method is the fundamental solution. However, there is also a certain risk that if you choose the wrong version, or for some other reason, other problems may occur after installation. So, before using this method, be sure to carefully confirm your problem, whether it is consistent with the knowledge base article, make sure that the selected patch version is correct, make sure that your windows server 2003 has been hit SP1 or SP2, etc.

The above is the solution for tcpsvcs.exe to use ultra-high virtual memory. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.