port allocation windows 10

• Back-to-School Tech Tips
• Editor's Choice: School Tech

How to Check If a Port Is Open in Windows 10

You can use a Windows command or third-party utilities

• University of Maine

• Western Governors University
• The Ultimate Laptop Buying Guide

What to Know

• Easiest: Open the Start menu > type command > right-click the Command Prompt app > Run as administrator .
• Type  netstat -ab  > press  Enter > look for items in the "LISTENING" state. 
• The alternative is to use a third-party app: We like TCPView, Nirsoft CurrPorts, and PortQry Command Line Port Scanner.

This article outlines how to check for open ports in Windows 10, which is necessary if an application cannot access the internet or you want to block an application.

How to Check If a Port Is Open With Netstat

The easiest way to check if a port is open on Windows 10 is by using the Netstat command . 'Netstat' is short for network statistics. It will show you what ports each internet protocol (like TCP, FTP, etc.) is currently using.

The command has many parameters, but the ones you'll need to use to check if a port is open are (a), which provides the active ports, and (b), which will tell you the name of the processes using those ports.

Select the Start menu and type "command." Right-click on the Command Prompt app and select Run as administrator .

Type netstat -ab and press Enter . You'll see a long list of results, depending on what's currently connecting to the network. You'll see a list of running processes. The open port numbers will be after the last colon on the local IP address (the one on the left).

Look for the items on the list with a state of "LISTENING." These are the processes that are communicating via one of the currently opened ports.

If you want to know the program's name that has a specific port open, then type netstat -aon and press Enter . This command will show the protocol the app is using, the local and remote IP addresses, and most importantly, the PID of the application using that port (the number on the far right). Remember to look for the LISTENING status.

To find the application related to that PID, right-click the task manager and select Task Manager . Select the Details tab. Look in the PID field for the PID you noted from the command prompt screen.

How to Check If a Port Is Working Using Third-Party Apps

If you don't want to use the command prompt to check for open ports, there are very easy-to-use third-party apps that can help.

TCPView is a utility included in Microsoft Sysinternals that shows you a list of all running processes and their associated open ports. This app displays ports opening and closing and packet transfers, all in real-time.

Nirsoft CurrPorts

Nirsoft CurrPorts  is another utility to see all ports currently being used by applications and services on your system. Just look for the  local ports  column to see which of your computer's ports are active.

The list also includes ports that are being connected to on the remote end (the server out on the internet).

PortQry Command Line Port Scanner 

Install PortQry Command Line Port Scanner for another command-line utility dedicated to scanning your computer for open ports. Once you install it, open Command Prompt in administrator mode . PortQry automatically installs in the C:\PortQryV2 directory, so change the directory of your command prompt to that directory.

Type the command portqry.exe -local to see all open TCP and UDP ports for your machine. It'll show you everything you can see with the NetStat command, plus port mappings and how many ports are in each state.

What Is a Port?

Applications running on your computer reach out and get information and data from servers elsewhere on the internet. These applications and the server know how to communicate based on their IP address and the port number.

Think of the IP address as a street address and the port number as the apartment number. If either the server or application attempts to communicate using any other port number, it won't work. Every other door will be "locked" because other ports are closed.

Get the Latest Tech News Delivered Every Day

• How to Use the Netstat Command
• Command Prompt: What It Is and How to Use It
• How to Use the Netstat Command on Mac
• How to Use the Ping Command for Testing in Windows
• 10 Best Free Firewall Programs
• How to Find Your IP Address in Windows
• How to Open an Elevated Command Prompt
• How to Set Up Port Forwarding
• How to Open Disk Management From Command Prompt
• How to Open Command Prompt (Windows 11, 10, 8, 7, etc.)
• How to Reset Network Settings in Windows 10
• 21 Best Command Prompt Tricks
• How to Open Disk Management
• What's Conhost.exe in Windows? What Does it Do?
• How to Fix It When Copy and Paste Isn't Working in Windows 10/11
• What Is Windows Terminal & How Does It Work?

By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.

How-To Geek

How do i open a port on windows firewall.

Firewalls are there to protect you from threats on the internet (both traffic from the internet and from local applications trying to gain access when they shouldn't).

Quick Links

How to open a port on windows 10.

Firewalls are there to protect you from threats on the internet (both traffic from the internet and from local applications trying to gain access when they shouldn't). Sometimes, though, you'll want to allow otherwise restricted traffic through your firewall. To do so, you'll have to open a port.

When a device connects to another device on a network (including the internet), it specifies a port number that lets the receiving device know how to handle the traffic. Where an IP address shows traffic how to get to a particular device on a network, the port number lets the receiving device know which program gets that traffic. By default, most unsolicited traffic from the internet is blocked by Windows Firewall. If you're running something like a game server, you might need to open a port to allow that specific kind of traffic through the firewall.

Note: This article shows you how to open a port on a particular PC's firewall to let traffic in. If you have a router on your network (which you likely do), you will also need to allow the same traffic through that router by forwarding the port there.

Clicking Start, type "Windows Firewall" into the search box, and then click on "Windows Defender Firewall."

Once Windows Firewall opens, click on "Advanced Settings."

This launches Windows Defender Firewall with Advanced Security. Click the "Inbound Rules" category on the left. In the far right pane, click the "New Rule" command.

If you need to open a rule for outgoing traffic, instead of clicking "Inbound Rule," you'd click "Outbound Rule." Most apps are pretty good about creating their own outbound rules when you install them, but you might occasionally run into one that cannot.

On the Rule Type page, select the "Port" option and then click "Next."

On the next screen, you'll have to choose whether the port you're opening uses the Transmission Control Protocol (TCP) or User Datagram Protocol (UDP). Unfortunately, we can't tell you specifically which to use because different apps use different protocols. Port numbers can range from 0-65535, with ports up to 1023 being reserved for privileged services. You can find an unofficial list of (most) TCP/UDP ports on the Wikipedia page , and you can also search for the app you're using. If you can't determine the specific protocol to use for your app, you can create two new inbound rules---one for TCP and one for UDP.

Select the "Specific Local Ports" option and then type the port number into the field provided. If you're opening more than one port, you can separate them by commas. If you need to open a range of ports, use a hyphen (-).

Click "Next" when you're done.

On the next page, click "Allow the Connection" and then click "Next."

Note: For this guide, we'll be using the "Allow the Connection" option, as we trust the connection for which we're creating a rule. If you want a little more piece of mind, the "Allow the connection if it is secure" rule uses Internet Protocol security (IPsec) to authenticate the connection. You can try that option, but many apps do not support it. If you try the more secure option and it doesn't work, you can always come back and change to the less secure one.

Next, choose when the rule applies and click "Next." You can choose one or all of the following:

• Domain:  When a PC is connected to a domain controller that Windows can authenticate access to the domain.
• Private:  When a PC is connected to a private network, like a home network or a network that you trust.
• Public:  When a PC is connected to an open network, like a cafe, airport, or library where anyone can join, and the security is unknown to you.

Related: What's the Difference Between Private and Public Networks in Windows?

In the final window, give your new rule a name and an optional, more detailed description. Click "Finish" when you're done.

If you want to disable the rule at any point, locate it in the list of Inbound or Outbound Rules, right-click it, and then click "Disable Rule."

That's all there is to it. If you need to open any other ports for a different program or with a different rule, repeat the steps above using a different set of ports to open.

Related: How to Create Advanced Firewall Rules in the Windows Firewall

How to Check Ports in Use in Windows 10 & 11

Can’t use a specific port? Here’s how to check which port is in use in Windows with simple commands and apps like currports and tcpview.

Windows has many applications connected or trying to connect to the internet at any point in time. With all those applications, it is only natural that they use many network ports.

Two or more applications may need the same port to work from time to time. When that specific port is already in use by one application, the other application cannot use that port, and it may show a warning message, error out, or crash entirely.

In those situations, it is better to know which ports are used and which application is using that specific port. That way, you can either change the port or terminate the problem-causing application so that the other one works as it should.

The good thing is that it is pretty easy to know which port is used by which application in Windows . So, without further ado, let me show the steps to find which ports are used in Windows 10 and 11 operating systems.

Note: The methods shown below work in Windows 7, 8, 10, and 11.

Table of contents:

Command to check ports in use

• Using CurrPorts
• Using TCPView

Using a single command, you can get a list of all the ports in use by various programs. This method is quite helpful if you want to take a quick glance at the ports in use.

1. Search for “cmd” in the start menu, right-click on the Command Prompt and select “Run as Administrator.” This option lets you open the command prompt with admin rights.

2. In the elevated command prompt window, execute the below command. You can copy and paste the command into the Command Prompt window by right-clicking inside it.

3. You will see the port number right next to the IP address (ex: 192.168.42.198: 50943 ) in the output result. You can see the highlighted portion of the attached image for better representation.

Keep in mind that the list will not be refreshed automatically. You have to execute the command again when you need an updated list. If you want the used port list to be updated automatically, follow one of the two methods illustrated below.

Use CurrPorts to find ports in use

Nirsoft Utilities has a pretty neat and lightweight tool called CurrPorts. It shows all the ports used by Windows and other programs. Let me show you how to use the application to get the information you need.

A quick note: In case you don’t know, Nirsoft has a lot of small and portable apps that are pretty useful in day-to-day life. If you’ve never used Nirsoft Utilities, browse the developer site and find many interesting little tools.

1. First, download CurrPorts from the official website. Being a portable application, you don’t have to install it. After downloading, extract the exe file from the zip file and double-click the file to open it.

2. As soon as you open the window, the application will list all the connections and their ports. You can find the port number under the Local Port section.

3. Being a dedicated port monitoring application, it offers quite a few options to manage the applications and ports. Right-click on any option, and you will see appropriate options like the ability to close the TCP connection, copying properties, application properties, etc.

4. If you want finer control, you can create your own filters to narrow down the search. To do that, select “Options -> Advanced Filters” option.

Use Sysinternals TCPView to check ports in use

Sysinternals TCPView is a Microsoft tool that makes it easy to view all the TCP connections and ports used in Windows 10 and 11. The tool is very similar to CurrPorts.

1. Download TCPView from the Sysinternals website, extract the exe file to your desktop, and double-click on it.

2. As soon as you open the application, you will see a user agreement. Agree to the agreement, and you will instantly see all the TCP connections and ports in use. You will find the port numbers under the Local Port section.

3. You can end the connection and free the port if you want to. To do that, right-click on the connection and select “End Process.” This will terminates the process.

That is all. It is that simple to find which ports are used in Windows 10 and Windows 11. If you like this article, check out how to change the network name in Windows 10 and how to show download and upload speed on the taskbar in Windows .

How to open ports in Windows Firewall

How do you open ports in Windows Firewall?

When dealing with certain apps and processes on your Windows 10 PC, you might run issues if you aren't connecting properly to the internet. If you've come across a potential fix that involves opening a certain port in your firewall, you might be wondering what exactly that process entails. This is a problem that can arise in plenty of situations, but especially when attempting to set up a VPN. If you suspect Windows Firewall is part of your connectivity issue, here's how to open ports.

How to open a port for incoming traffic in Windows Firewall

Windows Firewall is designed as a security measure for your PC. To put it simply, a firewall analyzes incoming and outgoing connections to determine whether or not they're threats. If you suspect that your Windows Firewall is causing connectivity issues, you can open a port for incoming traffic. Here's how:

• Right-click the Start button.
• Click Search .
• Type Windows Firewall .
• Click Windows Firewall .
• Click Advanced settings .
• Click Inbound Rules in the left frame of the window.
• Click New Rule… in the right frame of the window.
• Click Port .
• Click Next .
• Click either TCP or UDP .
• Click Specific local ports .
• Type a port number . (In this case, we will open port 1707.)
• Click Allow the connection .
• Click any network types you'd like to allow the connection over.
• Type a name for the rule.
• Click Finish .

How to open a port for outgoing traffic in Windows Firewall

The same set of steps listed above can be used to create a rule for outgoing traffic. In step No. 6, instead of clicking Inbound Rules , you'll want to click Outgoing Rules . The rest of the steps are the same, and you can disable the rule in the same manner by using the steps in the next section.

How to close a port in Windows Firewall

Want to disable the rule you created to open a port in the Windows Firewall? Here's how:

• Click Inbound Rules or Outbound Rules in the left frame of the window, depending on what type of rule you created.
• Click the rule you created.
• Click the name of the rule in the right frame of the window.
• Click Disable Rule .
• Click Delete if you want to completely delete the rule.

More resources

Need a bit more help with Windows Firewall and Windows 10? We have plenty of resources covering a wide range of topics.

• How to troubleshoot and fix Windows Firewall problems
• What you need to know about the new Windows Defender Security Center in the Creators Update
• Windows 10 help, tips, and tricks

Get the Windows Central Newsletter

All the latest news, reviews, and guides for Windows and Xbox diehards.

Cale Hunt is formerly a Senior Editor at Windows Central. He focuses mainly on laptop reviews, news, and accessory coverage. He's been reviewing laptops and accessories full-time since 2016, with hundreds of reviews published for Windows Central. He is an avid PC gamer and multi-platform user, and spends most of his time either tinkering with or writing about tech.

• 2 Starfield lockpicking: How to solve digipick puzzles
• 3 Starfield inventory management: What to keep, sell, and drop
• 4 7 ways to earn credits fast in Starfield
• 5 Starfield beginners guide: 7 things I wish I knew before playing

• All about AI
• Google Bard
• Inflection AI Pi Chatbot
• Anthropic Claude
• Generative AI
• AI Image Generation
• AI Regulation
• AI Research
• Large Language Models (LLM)
• Surface Pro
• Surface Laptop
• Surface Book
• Surface Duo
• Surface Neo
• Surface Studio
• Surface Hub
• Surface Pen
• Surface Headphones
• Surface Earbuds
• About WinBuzzer
• Follow Us: PUSH, Feeds, Social
• Write for Us
• Cookie Policy and Privacy Policy
• Terms of Service

How to Open or Close a Port in Windows 10 Firewall

We show you how to open or close a port in Windows 10 to increase compatibility with VPNs and other software or improve security.

The Windows 10 Firewall is an important part of your system's security, but it can also be a nuisance. At times, for example, it can cause connection issues with certain services. In such cases it may be necessary to add a Windows Firewall rule to open the relevant port. Common Windows 10 ports that users want to open include port 80,8088, 4000, 443, and 88. It pays to be aware of the security risks involved with opening a particular port. Consider that there may be a reason it's closed, and you may only want to do so temporarily.

After you've researched any risks, you can follow our guide below to learn how to open a port in Windows and how to close a port to maintain security.

How to Open or Block a Port or Port Range in Windows 10 Firewall

The Windows Firewall looks at incoming and outgoing connections and analyses them to determine whether they're trustworthy. At times, however, it may block a useful port unless the user explicitly tells it not to. To add a port to Windows Firewall (or close a port), you need to add something called a Windows Firewall rule or Firewall exception. This requires use of the dedicated Firewall app.

With that, your VPN, SSH, or other software should work correctly. If you are setting up a VPN and still struggling, our dedicated guide may be of some use. You should also bear in mind that the problem may be with your network connection itself, in which case you may want to perform a network reset .

• how to allow ports through firewall windows 10
• how to close a port
• how to close ports
• open ports on network
• Windows 10 Firewall
• Windows 10 Firewall open port
• Windows 10 Firewall Rules
• windows 10 ports
• windows firewall allow port

RELATED ARTICLES

How to censor on discord using a discord spoiler tag (manual or via bots), how to connect spotify to discord and use discord spotify bots, how to add or remove a password from excel workbooks, worksheets and cells, recent news.

Hackers Exploit WinRAR Vulnerability to Target Financial Traders

Project Moohan: Samsung and Google’s XR Headset Faces Delays

Android Gears up to Enhance eSIM Support in the Pixel 8,...

OpenAI Opens Up Fine-Tuning for GPT-3.5 Turbo, Making It More Adaptable...

Subscribe to WinBuzzer on Google News

How to configure port forwarding on a Windows 10 PC

James Walker

June 3, 2019

Looking for more How To posts? Check out our How To Page for all the latest tips on Windows, Microsoft Teams, LinkedIn, and more!

Windows 10 has built-in support for port forwarding but it’s not exposed in the Settings interface. Port forwarding allows you to access network resources as if they’re hosted on your local machine, which can be helpful when working on a LAN (local area network) or developing with web servers.

In this guide, we’ll walk you through adding your own port forwarding rule. For the purposes of this guide, we’ll add a rule which routes the address “http://127.0.0.1:9000” to “http://192.168.0.10:80”. You’ll then be able to visit “http://127.0.0.1:9000” in a browser and view what you would have seen if you’d accessed “http://192.168.0.10:80” directly.

Adding the rule requires use of the command prompt. You’ll need to be logged in as an administrator, too. Begin by typing “cmd” into the Start menu. Click the first search result while holding the Control and Shift keys to launch Command Prompt as an administrator.

Next, you’ll use the “netsh” command to configure the port-forwarding rule. It’s a somewhat long-winded command, so be sure to type it as you see below.

netsh interface portproxy add v4tov4 listenaddress=127.0.0.1 listenport=9000 connectaddress=192.168.0.10 connectport=80

Notice how the values given for “listenaddress”, “listenport”, “connectaddress” and “connectport” correspond to those we stated earlier. You’ll need to make adjustments here to suit the rule you’re adding. For example, if you want to route to port 8888 on the device with IP 192.168.0.1, you’d use these values for the “connectport” and “connectaddress” respectively.

When you press enter, the rule will be added and applied immediately. Try visiting the listening address and port in your browser – you should see the content being served by the connect address and port.

When it comes time to remove the rule, return to an administrator command prompt and use the following command:

netsh interface portproxy delete v4tov4 listenaddress=127.0.0.1 listenport=9000

Again, you’ll need to adjust the specified listening address and port to match the values you’re using. The rule will be deleted immediately and will no longer apply to new network requests.

New Xbox One S Fortnite Special Edition bundle to launch on June 7th, along with Xbox “greatest deals of the year” sale

Google’s new stadia game platform tries to get jump on e3 with june 6th webcast.

OnMSFT.com is built on:

Wordpress GeneratePress Azure

Theme thanks to heather.

Home About Contact Us

Join our team, © copyright 2014 - 2023 onmsft.com llc.

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Windows 10 USB port allocation

In a production line PC, a device-under-the-test product is plugged in and allocated with a port number. Then unplugged and the comport disappeared from the device manager list.

When a new product is plugged in - it gets a different port number and so on.

It seems that each allocated port number is kept for a particular device.

Once getting into 256 ports, the PC does not connect to any more devices, as all the com port numbers had been exhausted, although at any given time there is only a single device connected.

Any idea how to solve this?

• 2 See windowsdot.com/… . Have you researched this before asking it as a question? –  DrMoishe Pippik Oct 27, 2022 at 0:46
• 1 Downvotes are not warranted in my opinion. –  LawrenceC Oct 27, 2022 at 2:05
• This wording is confusing, “In a production line PC, a device-under-the-test product is plugged in and allocated with a port number. Then unplugged and the comport disappeared from the device manager list.” This this PC using USB ports to test stuff? I can’t understand what else this could be. –  Giacomo1968 Oct 27, 2022 at 2:08

2 Answers 2

Open Device Manager, as admin.

Scroll down to "Universal Serial Bus controllers"

Right click and uninstall all USB Root Hub and controller devices.

Note: If your mouse is connected via USB, it will stop working - same for your keyboard and any other USB device. Use a PS/2 mouse if your system has one, or do this while connected to the system via Remote Desktop.

Windows Plug and Play will redetect and reinstall the Root Hub and controller devices. You may need to restart again.

See if that resets the COM port count.

Thanks for the answer .

Meanwhile, a solution had been found:

Windows 10 allocates a serial port number to any different device which is plugged into the PC, and stores it in the case that the same device will be re-plugged.

"Different Device" in this context means a different USB PID/VID (Product ID, Vendor ID) or serial number. As the connected devices are identical, with the same PID/VID, it is the serial number that is different. Windows 10 generates this number based on a UID (Unique ID) which is provided by the device MCU. Once this number had been disabled (firmware change) - the problem had gone.

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged usb port com ..

• The Overflow Blog
• What it’s like being a professional workplace bestie (Ep. 603)
• Journey to the cloud part I: Migrating Stack Overflow Teams to Azure
• Featured on Meta
• Moderation strike: Results of negotiations
• Our Design Vision for Stack Overflow and the Stack Exchange network

Hot Network Questions

• Inverse trigonometric functions
• Non-invasive bubble sensor
• Are there questions that science can't answer, but philosophy can?
• Is a Schmitt-trigger output’s rise time affected by input pulse’s rise time?
• What is this metal part that came with the MSI z790 Carbon Wifi?
• How to confirm two sets contain the same vectors in any order?
• Rounding down value
• Science fiction book about a war veteran who was resurrected and goes on to meet a crab alien brain that gets installed onto his ship
• Mapping named parameters to indices for PreparedStatement
• Should I inform the Editor that I won't resubmit after a "Reject and Resubmit" verdict?
• What does the sky look like from the moon?
• Connect dots on a grid with one continuous line 2.0
• Idiom for being watched after your bad actions
• How to add another noise node to this existing node configuration
• Easier proof that every finite scheme is affine. (Reference in the literature?)
• LVM: Creation difference between CentOS 7 and CentOS 6
• What is important to keep in mind in grading proof-based courses?
• Parameter estimation in linear regression
• Is philosophy bad for you (if taken too literally)?
• How to fix code to avoid warning -Wunsafe-buffer-usage
• Someone I don't know contributed to my program on GitHub. Can I still present that program as my Bachelor thesis?
• Terminal: How to move files to the last used directory conveniently?
• Generating matrices with a single command
• Why is there copper wire from a tv splitter to a water pipe in my house?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

How to Set Up Port Forwarding in Windows

Every now and then you'll stumble upon an app or game that requires you to do something called "port forwarding." Without port forwarding, "inbound" traffic and data coming in from the Internet won't be able to communicate with the app or game, and you won't be able to carry out certain Internet-based functions of that software. This tutorial shows you how to set up port forwarding in Windows.

Note : you may also need to set up port forwarding on your router , for which we have a separate guide.

Set Up Port Forwarding on Windows

Create new port rules, frequently asked questions.

To forward ports in Windows, follow the instructions below:

• Press the Win key on your keyboard, then type firewall into the Start search menu. Click "Windows Defender Firewall with Advanced Security."

• As port forwarding generally involves inbound traffic (i.e., traffic coming to your PC from a company’s data centers or servers), click on "Inbound Rules" in the left pane.

If you’ve had your PC for a while, you should see a long list of “Rules” in the middle pane, applying to the various apps, services, and software that you allow to deliver traffic to your PC.

• To get an idea of how ports work, right-click on an entry in the list, click "Properties," then open "Protocols and Ports."

You’ll see the protocol type (usually TCP or UDP, though there are various alternatives) as well as the “Local port” – the port in your firewall that you’re allowing the connection through.

The really important one here is the Remote port, which is the port the client (app or software that’s trying to connect with you) is using to connect.

With most apps, as with the images above, a remote port is randomly assigned by the client, so it just defaults to "All ports" on the Windows firewall.

To create a new port rule, follow these steps:

• In the "Windows Defender Firewall with Advanced Security" window, click on "Inbound Rules" in the left sidebar.

• Click on "New Rule" on the right side of the screen.

• In the "New Inbound Rule Wizard" window, select "Port," then tap "Next."

• Select "TCP" or "UDP" and enter the specific port number you want to forward. You can also select "All local ports" or specify an IP address or a range of addresses you want to forward the port to.

• Select "Allow the connection" and press "Next."

• Choose whether the connection should apply to your domain, your private home network, or a public network location (not recommended for security’s sake), and click "Next."

• Give the rule a name, such as "Port Forwarding," and click "Finish."

After completing these steps, the port should be forwarded to Windows, and any traffic that comes in on that port will be directed to the specified IP address.

The new rule will be added to the existing list of inbound rules in the Advanced Security window. From there, you can make modifications to the rule by double-clicking on it. You can also tailor it to apply only to certain programs and services, among other possible changes.

Note that at any point, you can right-click on the rule and select "Disable" or "Delete."

Tip : now that you know how to set up port forwarding in Windows, you should also make sure these apps are not on your Windows PC , and look at our assessment of Windows Defender and whether it's good enough to protect your PC .

Is Port Forwarding Safe?

Port forwarding is mostly safe, but it is dependent on the security of the server and machine at the other end. If, for example, you're setting up port forwarding to host an online game, it's worth quickly checking online whether there are security issues with that game or software.

If you set up, say, an online Minecraft server, then you'll want to make sure that server's kept up to date and that you and other users on the server are using firewalls and – ideally – NAT.

The key is to know the software that you're port forwarding to and that it's a trusted piece of software.

Can I use port forwarding to improve my Internet speed?

Port forwarding does not directly improve Internet speed . However, it can improve the performance of certain network services, such as online gaming or file sharing, by allowing them to bypass certain network restrictions and firewalls.

What happens if I forward a port that is already being used by another program?

If you forward a port that is already in use, it can cause conflicts and may prevent the other program from functioning properly. It's important to only forward ports that are not already being used by another program.

As a technophile, Farhad has spent the last decade getting hands-on experience with a variety of electronic devices, including smartphones, laptops, accessories, wearables, printers, and so on. When he isn’t writing, you can bet he’s devouring information on products making their market foray, demonstrating his unquenchable thirst for technology.

Our latest tutorials delivered straight to your inbox

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

How to configure RPC dynamic port allocation to work with firewalls

• 4 contributors

This article helps you modify the Remote Procedure Call (RPC) parameters in the registry to make sure RPC dynamic port allocation can work with firewalls.

Applies to:   Windows Server 2012 R2 Original KB number:   154596

RPC dynamic port allocation is used by server applications and remote administration applications, such as Dynamic Host Configuration Protocol (DHCP) Manager, Windows Internet Name Service (WINS) Manager, and so on. RPC dynamic port allocation instructs the RPC program to use a particular random port in the range configured for TCP and UDP, based on the implementation of the operating system used. For more information, see references below.

Customers using firewalls may want to control which ports RPC is using so that their firewall router can be configured to forward only these Transmission Control Protocol (UDP and TCP) ports.

Many RPC servers in Windows let you specify the server port in custom configuration items such as registry entries. When you can specify a dedicated server port, you know what traffic flows between the hosts across the firewall. And you can define what traffic is allowed in a more directed manner.

As a server port, choose a port outside of the range you may want to specify below. You can find a comprehensive list of Server ports that are used in Windows and major Microsoft products in Service overview and network port requirements for Windows .

The article also lists the RPC servers and which RPC servers can be configured to use custom server ports beyond the facilities the RPC runtime offers.

Some firewalls also allow for UUID filtering where it learns from an RPC Endpoint Mapper request for an RPC interface UUID. The response has the server port number, and a subsequent RPC Bind on this port is then allowed to pass.

Use the method that is described in this article only if the RPC server does not offer a way to define the server port.

The following registry entries apply to Windows NT 4.0 and above. They don't apply to previous versions of Windows NT. Even though you can configure the port used by the client to communicate with the server, the client must be able to reach the server by its actual IP address. You can't use DCOM through firewalls that do address translation. For example, a client connects to virtual address 198.252.145.1, which the firewall maps transparently to the server's actual address of, say, 192.100.81.101. DCOM stores raw IP addresses in the interface marshaling packets. If the client can't connect to the address specified in the packet, it won't work.

For more information, see Using DCOM/COM+ with Firewall .

More information

The values (and Internet key) discussed below don't appear in the registry. They must be added manually using the Registry Editor.

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information, see How to back up and restore the registry in Windows .

With Registry Editor, you can modify the following parameters for RPC. The RPC Port key values discussed below are all located in the following key in the registry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet\Entry name Data Type

Ports REG_MULTI_SZ

Specifies a set of IP port ranges consisting of either all the ports available from the Internet or all the ports not available from the Internet. Each string represents a single port or an inclusive set of ports.

For example, a single port may be represented by 5984, and a set of ports may be represented by 5000-5100. If any entries are outside the range of 0 to 65535, or if any string can't be interpreted, the RPC runtime treats the entire configuration as invalid.

PortsInternetAvailable REG_SZ Y or N (not case-sensitive)

If Y, the ports listed in the Ports key are all the Internet-available ports on that computer. If N, the ports listed in the Ports key are all those ports that aren't Internet-available.

UseInternetPorts REG_SZ Y or N (not case-sensitive

Specifies the system default policy.

If Y, the processes using the default will be assigned ports from the set of Internet-available ports, as defined previously. If N, the processes using the default will be assigned ports from the set of intranet-only ports.

In this example, ports 5000 through 6000 inclusive have been arbitrarily selected to help illustrate how the new registry key can be configured. It isn't a recommendation of a minimum number of ports needed for any particular system.

Add the Internet key under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc

Under the Internet key, add the values Ports (MULTI_SZ), PortsInternetAvailable (REG_SZ), and UseInternetPorts (REG_SZ).

For example, the new registry key appears as follows:

Ports: REG_MULTI_SZ: 5000-6000 PortsInternetAvailable: REG_SZ: Y UseInternetPorts: REG_SZ: Y

Restart the server. All applications that use RPC dynamic port allocation use ports 5000 through 6000, inclusive.

You should open up a range of ports above port 5000. Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM application(s). Furthermore, previous experience shows that a minimum of 100 ports should be opened, because several system services rely on these RPC ports to communicate with each other.

The minimum number of ports required may differ from computer to computer. Computers with higher traffic may run into a port exhaustion situation if the RPC dynamic ports are restricted. Take this into consideration when restricting the port range.

If there is an error in the port configuration or there are insufficient ports in the pool, the Endpoint Mapper Service will not be able to register RPC servers with dynamic endpoints. When there is a configuration error, the error code will be 87 (0x57) ERROR_INVALID_PARAMETER. This can affect Windows RPC servers as well, such as Netlogon. It will log event 5820 in this case:

For more information, see:

• Service overview and network port requirements for Windows
• How to configure a firewall for Active Directory domains and trusts
• Restricting Active Directory RPC traffic to a specific port
• The default dynamic port range for TCP/IP has changed since Windows Vista and in Windows Server 2008

Was this page helpful?

Submit and view feedback for

Additional resources

• Stack Overflow Public questions & answers
• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Talent Build your employer brand
• Advertising Reach developers & technologists worldwide
• Labs The future of collective knowledge sharing
• About the company

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

How to change/view the ephemeral port range on Windows machines?

In Linux I can view or change the ephemeral port range using the /proc/sys/net/ipv4/ip_local_port_range file.

How can I view or change the ephemeral port range on a Windows machine?

3 Answers 3

http://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html#Windows says:

As of Windows Vista and Windows Server 2008, Windows now uses a large range (49152-65535) by default, according to Microsoft Knowledgebase Article 929851 . That same article also shows how you can change the range if desired, but the default range is now sufficient for most servers.

For older Windows operating systems (Windows XP and older), Windows uses the traditional BSD range of 1024 through 4999 for its ephemeral port range. Unfortunately it appears that you can only set the upper bound of the ephemeral port range. Here is information excerpted from Microsoft Knowledgebase Article 196271 :

• Start Registry Editor (Regedt32.exe).
• Locate the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

On the Edit menu, click Add Value, and then add the following registry value:

Value Name: MaxUserPort Data Type: REG_DWORD Value: 65534 <for example>

Valid Range: 5000-65534 (decimal) Default: 0x1388 (5000 decimal)

Description: This parameter controls the maximum port number used when an application requests any available user port from the system. Normally, ephemeral (that is, short-lived) ports are allocated between the values of 1024 and 5000 inclusive.

• Quit Registry Editor.

Note: There is another relevant KB article ( 812873 ) which claims to allow you to set an exclusion range, which could mean that you could exclude ports 1024-9999 (for example) to have the ephemeral port range be 10000-65534. However, we have not been able to get this to work (as of October 2004).

ReservedPorts is not supported for versions > Windows Server 2003.

There is a hotfix to add the missing functionality via netsh.

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

This is an old question, and it seems that the answer has changed in newer Windows versions (I'm not sure which ones exactly).

On my Windows 10 PC, it shows:

To change it, eg:

Your Answer

Sign up or log in, post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct .

Not the answer you're looking for? Browse other questions tagged windows networking range port or ask your own question .

• The Overflow Blog
• What it’s like being a professional workplace bestie (Ep. 603)
• Journey to the cloud part I: Migrating Stack Overflow Teams to Azure
• Featured on Meta
• Moderation strike: Results of negotiations
• Our Design Vision for Stack Overflow and the Stack Exchange network
• Temporary policy: Generative AI (e.g., ChatGPT) is banned
• Discussions experiment launching on NLP Collective
• Call for volunteer reviewers for an updated search experience: OverflowAI Search

Hot Network Questions

• Can a company with a very large valuation still be held privately?
• Idiom for being watched after your bad actions
• How to stop long words with "+" in them from going into the margins?
• Did Einstein say "Do not worry about your difficulties in mathematics, I assure you that mine are greater"?
• Replacing outlet: six wires and three screws?
• The correct negative form (past participle)
• What's the difference between 写下 and 记下？
• How can I set a time zone on a Linux machine that has only very minimal cmds available?
• How to make a genus 3 surface?
• Easier proof that every finite scheme is affine. (Reference in the literature?)
• An industrial revolution without overt, visible pollution/alternatives to coal?
• Why do many AI bots feel the need to be know-it-alls?
• What did Canadians use to pay for goods or services between 1871 and 1935?
• Is it allowed to push a bicycle during a race?
• Is it true that people willingly provide their articles that were published in journals?
• Is gravitational binding energy or gravitational self-energy a source of gravity?
• Someone I don't know contributed to my program on GitHub. Can I still present that program as my Bachelor thesis?
• Parameter estimation in linear regression
• Should I inform the Editor that I won't resubmit after a "Reject and Resubmit" verdict?
• How did sulphur came up to the surface of moon?
• Can I combine Assurance and Risky Surgery to consistently get Critical Successes for Treat Wounds?
• LVM: Creation difference between CentOS 7 and CentOS 6
• Medrash about Adam originally not having fingers
• Did "Joe the Plumber" perform plumbing work for money between when he left the Air Force and October 2008?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

How to configure RPC to use certain ports and how to help secure those ports by using IPsec

This article describes how to configure RPC to use a specific dynamic port range and how to help secure the ports in that range by using an Internet Protocol security (IPsec) policy. By default, RPC uses ports in the ephemeral port range (1024-5000) when it assigns ports to RPC applications that have to listen on a TCP endpoint. This behavior can make restricting access to these ports challenging for network administrators. This article discusses ways to reduce the number of ports available to RPC applications and how to restrict access to these ports by using a registry-based IPsec policy. Because the steps in this article involve computer-wide changes that require the computer to be restarted, all these steps should be performed first in nonproduction environments to identify any application-compatibility issues that may occur as the result of these changes.

More Information

There are multiple configuration tasks that must be completed in order to relocate, reduce, and restrict access to RPC ports. First, the RPC dynamic port range should be restricted to a smaller, more manageable port range that is easier to block by using a firewall or IPsec policy. By default, RPC dynamically allocates ports in the range of 1024 to 5000 for endpoints that do not specify a port on which to listen. Note This article uses the port range of 5001 to 5021. This reduces the number of ports that are available to RPC endpoints from 3,976 to 20. The number of ports was selected arbitrarily and is not a recommendation for the number of ports that are needed for any specific system. Next, an IPsec policy must be created to restrict access to this port range to deny access to all hosts on the network. Finally, the IPsec policy can be updated to give certain IP addresses or network subnets access to the blocked RPC ports and to exclude all others. To start the task of reconfiguring the RPC dynamic port range, download the RPC Configuration Tool (RPCCfg.exe), and then copy it to the workstation or to the server that will be reconfigured. To do this, visit the following Microsoft Web site:

http://www.microsoft.com/download/details.aspx?FamilyID=0f9cde2f-8632-4da8-ae70-645e1ddaf369&DisplayLang=en To perform the subsequent tasks of creating an IPsec policy, download the Internet Protocol Security Policies Tool (Ipsecpol.exe), and then copy it to the workstation or to the server that will be reconfigured. To do this, visit the following Microsoft Web site:

http://www.microsoft.com/download/details.aspx?displaylang=en&FamilyID=7D40460C-A069-412E-A015-A2AB904B7361 Note To create an IPsec policy for Microsoft Windows XP or for a later version of the Windows operating system, use Ipseccmd.exe. Ipseccmd.exe is part of the Windows XP support tools. The syntax and usage of IPseccmd.exe are the same as the syntax and usage of Ipsecpol.exe. For more information about the Windows XP support tools, click the following article number to view the article in the Microsoft Knowledge Base:

838079 Windows XP Service Pack 2 Support Tools

Relocate and reduce the RPC dynamic port range by using RPCCfg.exe

To relocate and reduce the RPC dynamic port range by using RPCCfg.exe, follow these steps:

Copy RPCCfg.exe to the server that is to be configured

At the command prompt, type rpccfg.exe -pe 5001-5021 -d 0. Note This port range is recommended for use by RPC endpoints because ports in this range are not likely to be allocated for use by other applications. By default, RPC uses the port range of 1024 to 5000 for allocating ports for endpoints. However, ports in this range are also dynamically allocated for use by the Windows operating system for all Windows sockets applications and can be exhausted on heavily used servers such as terminal servers and middle-tier servers that make many outgoing calls to remote systems. For example, when Internet Explorer contacts a Web server on port 80, it listens on a port in the 1024-5000 range for the response from the server. A middle-tier COM server that makes outgoing calls to other remote servers also uses a port in this range for the incoming reply to that call. Moving the range of ports that RPC uses for its endpoints to the 5001 port range will reduce the chance that these ports will be used by other applications. For more information about ephemeral port usage in Windows operating systems, visit the following Microsoft Web sites.

For Windows 2000:

http://technet.microsoft.com/library/bb726981.aspx

For Windows Server 2003:

http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true

Use an IPsec or firewall policy to block access to the vulnerable ports on the affected host

In the commands in the following section, any text that appears between percent (%) signs is intended to represent text in the command that must be entered by the person who creates the IPsec policy. For example, wherever the text "%IPSECTOOL%" appears, the person who creates the policy should substitute that text as follows:

For Windows 2000, substitute "%IPSECTOOL%" with "ipsecpol.exe."

For Windows XP or a later version of Windows, substitute "%IPSECTOOL%" with "ipseccmd.exe."

For more information about how to use IPsec to block ports, click the following article number to view the article in the Microsoft Knowledge Base:

813878 How to block specific network protocols and ports by using IPSec

Block access to the RPC Endpoint Mapper for all IP addresses

To block access to the RPC Endpoint Mapper for all IP addresses, use the following syntax. Note On Windows XP and on later operating systems, use Ipseccmd.exe. On Windows 2000, use Ipsecpol.exe (Windows 2000).

Note Do not type "%IPSECTOOL%" in this command. "%IPSECTOOL%" is intended to represent the part of the command that must be customized. For example, on Windows 2000, type the following command from a directory that contains Ipsecpol.exe to block all incoming access to TCP 135:

On Windows XP and on later operating systems, type the following command from a directory that contains Ipseccmd.exe to block all incoming access to TCP 135:

Block access to the RPC dynamic port range for all IP addresses

To block access to the RPC dynamic port range for all IP addresses, use the following syntax. Note On Windows XP and on later operating systems, use Ipseccmd.exe. On Windows 2000, use Ipsecpol.exe (Windows 2000).

Note Do not type "%IPSECTOOL%" or "%PORT%" in this command. "%IPSECTOOL%" and "%PORT%" are intended to represent parts of the command that must be customized. For example, type the following command on Windows 2000 hosts to block all incoming access to TCP 5001:

To block all incoming access to TCP 5001, type the following command on Windows XP hosts and on hosts of later Windows operating systems:

Repeat this command for each RPC port that must be blocked by changing the port number that is listed in this command. Ports that must be blocked are in the 5001-5021 range. Note Do not forget to change the port number in the rule name (the -r switch) and in the filter (the -f switch).

Optional: Give access to the RPC Endpoint Mapper for specific subnets if access is needed

If you must give specific subnets access to the restricted RPC ports, you must first give these subnets access to the RPC Endpoint Mapper that you blocked earlier. To give a specific subnet access to the RPC Endpoint Mapper, use the following command:

Note In this command, the following statements apply:

"%IPSECTOOL%" represents the command to use. This command is either "ipsecpol.exe" or "ipseccmd.exe." Which command is used depends upon which operating system you are configuring.

"%SUBNET%" represents the remote IP subnet to which you want to give access, for example, 10.1.1.0.

"%MASK%" represents the subnet mask to use, for example, 255.255.255.0. For example, the following command enables all hosts from the 10.1.1.0/255.255.255.0 subnet to connect to port TCP 135. All other hosts will have their connections denied by the default block rule that was created earlier for this port.

Optional: Give access to the new RPC dynamic port range for specific subnets if access is needed

Each subnet that was given access to the RPC Endpoint Mapper earlier should also be given access to all the ports in the new RPC dynamic port range (5001-5021). If you enable subnets to reach the RPC Endpoint Mapper but not the dynamic port range, the application may stop responding, or you may experience other problems. The following command gives a specific subnet access to a port in the new RPC dynamic port range:

"%PORT%" represents the port in the dynamic port range to which to give access.

"%MASK%" represents the subnet mask to use, for example, 255.255.255.0. For example, the following command enables all hosts from the 10.1.1.0/255.255.255.0 subnet to connect to port TCP 5001. All other hosts will have their connections denied by the default block rule that was created earlier for this port.

Note This command should be repeated for each subnet and port in the new RPC dynamic port range.

Assign the IPsec policy

Note The commands in this section take effect immediately. After you create all the block rules and all the optional allow rules for the configured RPC ports, assign the policy by using the following command:

Note To immediately unassign the policy, use the following command:

Note To delete the policy from the registry, use the following command:

You must restart the host for the changes to take effect. Notes

The RPC configuration changes require a restart.

The IPsec policy changes take effect immediately and do not require a restart.

After the workstation or server restarts, any RPC interfaces that use the ncacn_ip_tcp protocol sequence and do not specify a specific TCP port to which to bind will have a port allocated from this range by the RPC runtime when the RPC server starts. Note The server may require more than 20 TCP ports. You can use the rpcdump.exe command to count the number of RPC endpoints that are bound to a TCP port and to increase this number if you must. For more information about how to obtain the RPC Dump tool, visit the following Microsoft Web site:

http://www.microsoft.com/download/details.aspx?displaylang=en&familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd

Need more help?

Want more options.

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Microsoft 365 subscription benefits

Microsoft 365 training

Microsoft security

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Ask the Microsoft Community

Microsoft Tech Community

Windows Insiders

Microsoft 365 Insiders

Was this information helpful?

Thank you for your feedback.

Avoiding TCP/IP Port Exhaustion

Avoiding tcp/ip port exhaustion apr 16, 2020 • knowledge, information.

Answer/Solution:

This article describes how to figure out if you are running out of Windows TCP client ports and how to change parameters to allow access to more client ports.  This article may be of use with busy MOVEit DMZ API or MOVEit Central applications, but it also can apply to third-party clients running on Windows machines.   How Do I Know If I'm Running Out of Client Ports?  If you are running out of client ports your client will often display messages like containing phrases like "no client ports available" or "TIME_WAIT".  Your client will also usually be free of these messages for a while after a reboot, but will begin to display them after a few minutes or hours.   To confirm that the system is "out of ports" while you are getting these messages on your client, open a command window and type the following command:  Open the Resource Monitor on the WhatsUp Server using the path below: %windir%\system32\perfmon.exe /res This will open the Resource Monitor

Click on the Network Tab and then expand the listening port section.  The listening Ports will show the following:

• Image name (process)
• Firewall Rules

How Can I Find Out What Application Is Using Up My Client Ports? 

• Click on the Network Tab, then select the listening ports.
• Sort the ports in ascending order to show lowest to greatest port numbers.
• Scroll to the largest number, if it is 65535, then port exhaustion is occurring.

How Can I Fix This?  Increase the available ports from the default 15000 to 30000 Open an administrator command prompt on the WhatsUp server and run the commands listed below. The start port is number, and the total number of ports is range. The following are sample commands:

• netsh int ipv4 set dynamicport tcp start=32769 num=32766
• netsh int ipv4 set dynamicport udp start=32769 num=32766
• netsh int ipv6 set dynamicport tcp start=32769 num=32766
• netsh int ipv6 set dynamicport udp start=32769 num=32766
• netsh int ipv4 show dynamicport tcp
• netsh int ipv4 show dynamicport udp
• netsh int ipv6 show dynamicport tcp
• netsh int ipv6 show dynamicport udp

Or you can use this method, although it requires a reboot. To do this, add the following HEX/DWORD entry to the local registry of your client system.  By default, the implicit value is "5000", which leads to a client source port range of 1024-5000.  You can pick a value of MaxUserPort up to "65535", but a lower value is recommended.   HKEY_LM\System\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort = 15000 (decimal)  A reboot is required to get this setting to take effect.  Faster Close After Connection Terminated  If most of the connections shown in "netstat" or "TcpView" are "TIME_WAIT" or "CLOSE_WAIT", you may need to shorten up the time connections "wait" before Windows really, really closes them.   To do this, add the following HEX/DWORD entry to the local registry of your client system.  By default, the implicit value is "120", which means a time out of 2 minutes.  You can pick a value of TcpTimedWaitDelay down to "1", but a higher value is recommended.   HKEY_LM\System\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay = 30 (decimal)  A reboot is required to get this setting to take effect.  Other Windows TCP Connection Parameters   The two registry entries covered above control what we feel are the most important Windows TCP performance settings, but there are a few other relatively safe changes that may have a positive effect on your system.      HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\  DisableIPSourceRouting = 2 (protects against packet spoofing)  EnableDeadGWDetect = 0 (disable; to avoid certain DOS attacks)  EnableICMPRedirect = 0 (disable; to avoid certain routing attacks)  KeepAliveTime = 300000 (5 minutes; implicit default is 1 hour)  TcpMaxDataRetransmissions = 4 (implicit default is 5)  A reboot is required to get any of these settings to take effect.  Also review the following Microsoft reference: https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-tcpip-port-exhaust

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Related Articles

• Number of Views 41.59K
• Number of Views 29.12K
• Number of Views 10.25K
• Number of Views 5.89K
• Number of Views 20.05K

Copyright © 2023 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use | Privacy Center | Trademarks | License Agreements | Careers | Offices