The netstat command can now display process IDs that correspond to active TCP or UDP connections in Windows 2000

Article translations Article translations
Article ID: 907980 - View products that this article applies to.
Notice
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy.
Expand all | Collapse all

On This Page

INTRODUCTION

This article describes a new feature that is available in the Microsoft Windows 2000 version of the netstat command. The netstat command can now display process IDs (PIDS) that are associated with active TCP or UDP network connections. This feature is available by downloading a Windows 2000 update.

MORE INFORMATION

Update information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time   Version            Size    File name
--------------------------------------------------------------
29-Sep-2005  05:24  5.0.2195.7071      67,856  Iphlpapi.dll     
29-Sep-2005  05:05  5.0.2195.7071      27,920  Netstat.exe      
23-Sep-2005  04:10  5.0.2195.7070   6,386,688  Sp3res.dll       
29-Sep-2005  05:06  5.0.2195.7071     320,336  Tcpip.sys
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

The netstat command can display the following information:
  • Active TCP connections
  • Ports on which a computer is listening
  • Ethernet statistics
  • The IP routing table
  • IPv4 statistics
  • IPv6 statistics
The netstat command displays active TCP connections when you use the command without parameters. The new -o parameter lets you audit and troubleshoot the ports that are being used. When you use the netstat command together with the -o parameter, the command displays the owning PID that is associated with each connection. This parameter was not previously present in Windows 2000. After you install this update, you can map ports to PIDs by using the netstat -ano command.

Note The Microsoft Windows XP and Microsoft Windows Server 2003 versions of the netstat command can display PIDs. This update does not provide the -b and -v parameters that are available in the Windows XP and Windows Server 2003 versions of the netstat command.

The netstat -ano command displays output that is similar to the following:
Collapse this tableExpand this table
ProtoLocal addressForeign addressStatePID
TCP0.0.0.0:800.0.0.0:0LISTENING460
TCP0.0.0.0:1350.0.0.0:0LISTENING1640
TCP0.0.0.0:4450.0.0.0:0LISTENING4
TCP0.0.0.0:10240.0.0.0:0LISTENING460
TCP0.0.0.0:10250.0.0.0:0LISTENING1308
TCP0.0.0.0:425100.0.0.0:0LISTENING1116
You can identify the port and the associated PID from the netstat -ano command output. You can then use Task Manager to identify the process that is associated with the PID. By default, Task Manager does not display the PID that is associated with a process. To display a PID in Task Manager, follow these steps:
  1. Press CTRL+ALT+DELETE, and then click Task Manager.
  2. In Task Manager, click the Process tab, click View, and then click Select Columns.
  3. In the Select Columns dialog box, click to select the PID (Process Identifier) check box, and then click OK. You see that the PID column has been added to the Process tab. You can now locate the PID and the corresponding executable file that started the process in Task Manager.
For more information about how to use the netstat command to find a PID, click the following article number to view the article in the Microsoft Knowledge Base:
281336 How to determine which program uses or blocks specific transmission control protocol ports in Windows
For more information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 907980 - Last Review: October 9, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Server
Keywords: 
kbautohotfix kbinfo kbfix kbwin2000presp5fix kbhotfixserver kbqfe KB907980

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com