How to Check Open Ports in Windows 10 Using CMD

In this article, you will see the procedure to Check Open Ports in Windows 10 Using CMD (or Command Prompt). When an app uses a TCP/IP port on your device in order to access a network, that port would be locked out – no other program may be able to use it. And while everything related to ports and traffic is usually taken care of on its own by the system, there might be situations when you might have to know the application that is blocking a specific port.

Here you can find some built-in ways to do so- specifically the ways to check open ports using CMD or Command Prompt. Apart from using the Command Prompt, you can even consider using some third-party applications that can easily list the ports and the apps or processes that are using them.

Way to Check Open Ports in Windows 10 Using CMD

Here is how to check open Ports in Windows 10 Using CMD –

To find port-use with process names

Follow along with these steps to get the list of ports in use and the names of the processes tied up with them respectively.

Step-1: Open Run dialog box by pressing Win+R hotkeys. Type cmd in the text box and hit Shift + Ctrl + Enter keys altogether.

Step-2: Hit Yes on the UAC prompt.

Step-3: This will let you access an elevated Command Prompt on the screen. Here, type in or copy-paste the below-given code and hit Enter.

Wait for the entire result to load. Once you successfully run this command, simply scroll down to the port number you want to check. As shown below, you’ll be able to see the process’ name respectively below the port it is linked to.

To find port-use with the process identifiers

Usually, identifying the application which represented by a specific process name can be tricky. This method might help you identify the application that a process relates to.

Here also, first of all, launch the “Command Prompt” with admin rights using any of your preferred methods.

Copy-paste or type the below code and ensure to hit Enter.

Finally, the result now will contain the “PID” or the process identifiers instead of the names. Simply scroll down to the port you want to check and note the PID corresponding to it.

Moving ahead, open Task Manager. To do so, perform a right-click on the taskbar and select the option namely “Task Manager”.

Go to the Processes tab. Right-click on the Name column and choose PID (see snapshot).

You just need to find the PID you note earlier. The ‘Name’ column corresponding to the PID must reveal the application associated with the port.

Command line for looking at specific port

Is there a way to examine the status of a specific port from the Windows command line? I know I can use netstat to examine all ports but netstat is slow and looking at a specific port probably isn’t.

14 Answers 14

Here is the easy solution of port finding.

You can use the netstat combined with the -np flags and a pipe to the find or findstr commands.

Basic Usage is as such:

So for example to check port 80 on TCP, you can do this: netstat -np TCP | find «80» Which ends up giving the following kind of output:

As you can see, this only shows the connections on port 80 for the TCP protocol.

here o represents process ID. now you can do whatever with the process ID. To terminate the process, for e.g., use:

when I have problem with WAMP apache , I use this code for find which program is using port 80.

3068 is PID, so I can find it from task manager and stop that process.

As noted elsewhere: use netstat, with appropriate switches, and then filter the results with find[str]

To find a foreign port you could use:

To find a local port you might use:

Where N is the port number you are interested in.

-n ensures all ports will be numerical, i.e. not returned as translated to service names.

-a will ensure you search all connections (TCP, UDP, listening. )

In the find string you must include the colon, as the port qualifier, otherwise the number may match either local or foreign addresses.

You can further narrow narrow the search using other netstat switches as necessary.

Further reading (^0^)

it will give you number of sockets active on a specific IP and port(Server port number)

For Windows 8 User : Open Command Prompt, type netstat -an | find «your port number» , enter .

If reply comes like LISTENING then the port is in use, else it is free .

To find a foreign port (IPv4 or IPv6) you can use:

To find a local port (IPv4 or IPv6) you can use:

Where N is the port number you are interested in. The «/r» switch tells it to process it as regexp. The «/c» switch allows findstr to include spaces within search strings instead of treating a space as a search string delimiter. This added space prevents longer ports being mistreated — for example, «:80» vs «:8080» and other port munging issues.

To list remote connections to the local RDP server, for example:

Or to see who is touching your DNS:

If you want to exclude local-only ports you can use a series of exceptions with «/v» and escape characters with a backslash:

How to get a list of all open ports on Windows 7, Vista and XP?

There is a small freeware Utility called CurrPorts from Nirsoft that displays all open ports on windows.

Download CurrPorts to your computer:

Unpack the .zip file and double click on the file cports.exe to start CurrPorts. The application will show you a list of all open ports and offers the ability to apply filters on the list.

8 thoughts on “How to get a list of all open ports on Windows 7, Vista and XP?”

Thia little program is great it leaves no footprint when in use and is very handy at finding leeching programs that have either attached themselves to other processes such as IE and for those that are just disguising themselves as knowen processes by using the same name.
Thanks! Oh yeah and best of all it’s FREE
Striker

thanks it works.

than yoould you explainu for the reply.i did not understand what is the thia little program, c

i have problem assigning a port to my build in web cam,can you help please

I am using win 7 and after I instol ZXpos CNT1 software that used for network drive tese in CDMA20001xevdo even if com ports are avalable on device manager but i can not find this ports on CNT1 interface for detecting phone and gps
can i get any help!

I have the same problem after I re-installed my OS (Windows 7). Before no problem.

How to Check for Ports in Use in Windows 10

At any one time, there’s a whole bunch of information being sent between your Windows 10 PC and the endless void of the Internet. This is done using a process whereby network-dependent processes seek out TCP and UDP ports, which they use to communicate with the Internet. First, your data gets sent to remote ports at the destination or website your processes are trying to connect to, then it gets received at local ports back on your PC.

Most of the time, Windows 10 knows how to manage ports and ensure that traffic is being directed through the right ports so that those processes can connect with what they need to. But sometimes two processes may be assigned to one port, or maybe you just want to get a better picture of your network traffic and what’s going in and out.

That’s why wrote this guide that shows you how to get an overview of your ports and see which applications are using which ports.

Use Nirsoft CurrPorts

NirSoft is one of the best indie software developers, giving us great utilities, like PassView and WirelessKeyView. While some people will prefer checking their ports without installing third-party software (in which case, scroll down to the CMD method), CurrPorts is easily the fastest and most convenient way to view your ports.

Once you’ve installed CurrPorts, just open it to see a list of all your ports currently in use. If you’re looking for local ports in use, just click the “Local Port” column at the top to order the list by port number (handy if you’re looking for a specific one). You can do the same thing with remote ports, too.

If you want to really find specific ports, click the “Advanced Filters” icon at the top and enter your string in the format they suggest. It should look something like the below image.

Hit OK when you’re ready, and the list will filter down to your queries.

Command Prompt Method

The integrated – though not necessarily the simplest – way to check open ports is to use the trusty command prompt.

Click the Start button, type cmd , then right-click “Command Prompt” when it shows up in the search results. Click “Run as administrator.”

Once you’re in the elevated command prompt, enter the following command:

This will steadily bring up a list of ports that is probably quite long, along with the Windows processes that are using them. (You can press Ctrl + A , then Ctrl + C to copy all information to the clipboard.) On the average PC, there will be two main local IP addresses that contain ports on your PC.

The first, in our case, is “127.0.0.1.” This IP address is otherwise known as “localhost” or a “loopback address,” and any process listening to ports here is communicating internally on your local network without using any network interface. The actual port is the number you see after the colon. (See image below.)

The bulk of your processes will probably be listening to ports prefixed with “192.168.xxx.xxx,” which is your IP address. This means the processes you see listed here are listening for communications from remote Internet locations (such as websites). Again, the port number is the number after the colon.

TCPView

If you don’t mind installing a third-party app and want to have more control over what’s going on with all your ports, you can use a lightweight app called TCPView. This immediately brings up a list of processes and their associated ports.

What make this better than the command prompt is that you can actively see the ports opening, closing and sending packets. Just look for the green, red and yellow highlights. You can also reorder the list by clicking the column headings, making it easier to find the process you want or two separate processes vying for the same port.

If you do find a process or connection you want to close, just right-click that process. You can then select “End process,” which is exactly the same function as the one in Windows task manager. Or you can click “Close Connection” to leave the process open but stop it from listening on a given port.

If you’re having some trouble in Windows 10, then see whether a Windows update may be causing it. We also have a handy guide for managing the health of your hard drive in Windows 10.

Related:

Content Manager at Make Tech Easier. Enjoys Android, Windows, and tinkering with retro console emulation to breaking point.

How to Find Open and Blocked TCP/UDP Ports

Using one of these free scanning tools

There’s a good chance you’ve happened upon this article because an application you’re trying to run is complaining about a “port” being blocked or you’ve read about how leaving certain “ports” open on your network can be a security problem.

Either way, by the end of this piece you’ll not only know what these ports everyone is going on about are, but how to check your computer to find open or closed ports.

What Is a Network Port?

The first thing you should know is that the ports we’re referring to here are virtual. It has nothing to do with the physical network hardware ports on your router, TV, consoles or computers. Ports are simply a way for your network hardware and software to organize information traffic.

Think of reserved lanes on a road. The sidewalk is for pedestrians. There might be a dedicated bike lane. Carpool vehicles and buses have their own lanes too. Ports serve the same function. One port might be used for receiving emails, while another carries file transfer requests, or website traffic.

There are two common types of ports, which need a brief explanation before we move on to checking which ports on your system are open and which aren’t.

What Are TCP & UDP Ports?

The two common types of ports on modern networks are known as TCP and UDP ports. That is Transmission Control Protocol and User Datagram Protocol respectively. So these two port types use different network protocols.

Which you can think of as distinctive sets of rules for how bits of information should be sent and received. Both port types are built on the fundamental Internet Protocol (IP) that makes the internet and home networks, well, work. However, they are suitable for different applications.

The big difference is that when you send information over UDP, the sender doesn’t first have to establish a connection with the receiver before starting the conversation. It’s a bit like sending a letter. You don’t know if the other person received your message and you have no guarantee that you’ll get any feedback.

TCP, on the other hand, is more like making a phone call. The receiver has to “pick up” the connection and there’s a back-and-forth flow of information until someone deliberately hangs up.

UDP messages are generally broadcast over a network to anyone who is listening on the specified UDP port. This makes it perfect for housekeeping type messages that relate to running the network itself. It’s also perfect for voice-over-IP streaming, online video games and streaming broadcasts.

Why? These applications benefit from UDP’s low latency and constant stream of information that doesn’t have to be perfect to be useful. A little corruption in your Skype chat is far less important than low amounts of lag, after all.

TCP is much more common than UDP and absolutely makes sure that all data is received free from errors. Just about everything that doesn’t need the specific advantages of UDP, uses TCP instead.

Which Ports Are Usually Open By Default?

There are a LOT of ports. A port number can be anything from 0 to 65535! That doesn’t mean any application can just pick any port. There are established standards and ranges, which helps us make sense of the noise.

Ports 0-1023 are associated with some of the most important and fundamental network services. This makes sense, since the lower-numbered ports were assigned first. The SMTP protocol for email, for example, is exclusively used by port 25.

Ports 1024-49151 are known as “registered ports” and are assigned to important common services such as OpenVPN on port 1194 or Microsoft SQL on ports 1433 and 1434.

The rest of the port numbers are known as “dynamic” or “private” ports. These ports aren’t reserved and anyone can use them on a network to support a particular service. The only problem crops up when two or more services on the same network are using the same port.

While it’s impossible to list every single important port, these common ports are useful to know by heart:

• 20 – FTP (File Transfer Protocol)
• 22 – Secure Shell (SSH)
• 25 – Simple Mail Transfer Protocol (SMTP)
• 53 – Domain Name System (DNS)
• 80 – Hypertext Transfer Protocol (HTTP)
• 110 – Post Office Protocol (POP3)
• 143 – Internet Message Access Protocol (IMAP)
• 443 – HTTP Secure (HTTPS)

Since there are so many thousands of common port numbers, the easiest approach is to remember the ranges. Which will tell you if a given port is reserved or not. Thanks to Google, you can also look up which services use a specific port in no time at all.

Find Open Ports In Windows

Now that we’ve got all the basic knowledge about TCP and UDP ports out of the way, it’s time to get down to the process of finding which ports are open and in use on your computer.

The good news is that Windows has a pretty useful command built into it that will show you what ports are currently being used on your computer by various applications and services.

• The first thing you want to do is open the Start Menu and search for CMD.

• Now, right-click on CMD and Run as Administrator.

• With the Command Prompt open, type:

Netstat -ab

• Don’t worry about a long list of info scrolling by faster than you can read it. You can simply use CTRL+C and CTRL+V to copy and paste the information into Notepad or any other text editor.
• The information in brackets is the name of the program that’s using the port. TCP or UDP refers to the protocol being used on that port. The number consists of an IP address and then the port number after the colon.

Scanning For Blocked Ports

That takes care of finding which ports are being used and by which application, but it doesn’t tell us which ports are being actively blocked by the Windows Firewall.

• Once again, open the Start Menu and search for CMD.
• Right-click on CMD and Run as Administrator.
• With the Command Prompt open, type:

netsh firewall show state

This is a display of blocked and open ports as per the configuration of your Windows Firewall.

You’ll see a note about this command being deprecated, but the new command doesn’t show us the information we want. So for now using the ‘show state’ command is still the fastest and easiest way to get port information.

Just because the Windows Firewall isn’t blocking a port, that doesn’t mean your router or ISP aren’t. So the last thing we want to do is check if any external blocking is happening.

• Open the Start Menu and search for CMD.
• Now, right-click on CMD and Run as Administrator.
• With the Command Prompt open, type:

netstat -ano | findstr -i SYN_SENT

If you don’t get any hits listed, then nothing is being blocked. If some ports are listed, it means they are being blocked. If a port not blocked by Windows shows up here, you may want to check your router or pop an email to your ISP, if switching to a different port isn’t an option.

Useful Apps To Map Out Your Port Status

While the Command Prompt is a good quick and dirty tool, there are more refined third-party applications that can help you get a picture of your port configuration. The two highlighted here are just popular examples.

SolarWinds Free Port Scanner

SolarWinds requires that you submit your name and details in order to download it, but it’s up to you whether you put your real information into the form or not. We tried several free tools before settling on SolarWinds, but it was the only tool that both worked properly under Windows 10 and had an easy interface.

It was also the only one not to trigger a false positive virus flag. One of the big problems with port scanning software is that security companies tend to see them as malware. So most users ignore any virus warning that come with such tools. That’s a problem because you can’t tell the difference between a false positive and a real virus in these apps.

SolarWinds might come with some strings attached, but it actually works as advertised and is easy to use.

CanYouSeeMe

This is, as you can probably tell, a website service rather than an application. It’s a good first port of call to see if external data can get through your local port or not. It auto-detects your IP address and all you have to do is specify which port to test.

It will then tell you if the port is blocked or not and you’ll then have to figure out whether the blockage is on the computer, router or at the service provider level.

Conclusion

For most users, ports aren’t something you need to worry about. They are managed by your operating system, applications and network hardware.

When things go wrong however, it’s good to have the tool in hand that let you find open ports to sniff out suspicious activity or figure out where exactly your precious information is hitting a brick wall.

Sydney Butler is a social scientist and technology fanatic who tries to understand how people and technology coexist. He has two decades of experience as a freelance computer technician and more than a decade as a technologies researcher and instructor. Sydney has been a professional technology writer for more than five years and covers topics such as VR, Gaming, Cyber security and Transhumanism. Read Sydney’s Full Bio