Port issue

Question

Port issue

Scott Huang 3,491

Hi,

How to resolve it below?

Get-NetTCPConnection : No MSFT_NetTCPConnection objects found with property 'LocalPort' equal to '7060'. Verify the

value of the property and retry.

At line:1 char:1

Get-NetTCPConnection -LocalPort 7060


    + CategoryInfo          : ObjectNotFound: (7060:UInt16) [Get-NetTCPConnection], CimJobException

    + FullyQualifiedErrorId : CmdletizationQuery_NotFound_LocalPort,Get-NetTCPConnection

0 comments

2 answers

Your answer

Answer 1

The error message you are encountering indicates that there are no TCP connections currently using the local port 7060. Here are a few steps you can take to troubleshoot and resolve this issue:

Verify the Port: Ensure that the application or service you expect to be using port 7060 is running. If the service is not active, there will be no TCP connections associated with that port.
Check Firewall Settings: Make sure that your firewall settings allow traffic on port 7060. Sometimes, firewall rules can block connections, leading to no active connections being found.
Use Different Parameters: If you are looking for established connections, you can try running the command without specifying the -LocalPort parameter to see all current TCP connections:
```
   Get-NetTCPConnection
```
This will help you determine if there are any connections at all.
Check for Listening Ports: You can check if any application is listening on port 7060 by using the following command:
```
   Get-NetTCPConnection -State Listen
```
This will show you if any application is set to accept connections on that port.
Restart the Service: If the application is supposed to be using port 7060 but is not showing up, try restarting the application or service that is expected to use that port.

If after these steps you still cannot find any connections on port 7060, it may indicate that the application is not configured correctly or is not running as expected.

Answer 2

AgaveJoe 31,181

It looks like there’s a misunderstanding regarding how you're connecting. If the application is hosted on a remote server, you cannot use localhost or check the local port on your client machine to verify the connection.

The Get-NetTCPConnection command you ran only looks at your local machine. You need to ensure you are using the server’s actual IP address or domain name in your connection string. Additionally, verify that the server's firewall is configured to allow traffic on port 7060 from external clients and that you have configure the binding on the remote server.

Scott Huang 3,491 Reputation points

2026-02-11T13:53:50.7233333+00:00

Yes, before this, I made use of the server's IP on the client side and had the issue. How to identify any existing filtering on the client side?
AgaveJoe 31,181 Reputation points

2026-02-11T22:56:37.2+00:00

Before troubleshooting client-side filtering, you must verify the server state. Can you remote into the server and run Get-NetTCPConnection -LocalPort 7060?

If that returns no results, the issue isn't a filter—it's that the service isn't listening. Please double-check your IIS site bindings to ensure port 7060 is correctly mapped and the application is active.
Scott Huang 3,491 Reputation points

2026-02-12T01:49:22.2733333+00:00

Yes, I got the issue below on the server.
AgaveJoe 31,181 Reputation points

2026-02-12T10:19:35.3133333+00:00

The error confirms that no service is listening on port 7060. For this to work on the server, the IIS bindings must be explicitly configured.

To assist further, we need the following details:

How did you configure the site bindings in IIS?

What specific steps did you take to deploy the ASP.NET application?

Without knowing the host configuration or seeing the IIS setup, we can't determine why the application isn't binding to the expected port. Please provide these details so we can move forward.
Scott Huang 3,491 Reputation points

2026-02-13T02:15:12.9+00:00

Should we enable 7060 on Binding, for the exact domain, by granting it with proper Https certificate, right?
AgaveJoe 31,181 Reputation points

2026-02-13T10:55:10.0533333+00:00

Before discussing HTTPS certificates or domain bindings, we must address the fact that the service is not yet responding on the server. As noted previously, the 'ObjectNotFound' error confirms that port 7060 is currently closed.

We cannot troubleshoot the certificate or domain until the following is confirmed:

Why Port 7060? Is there a specific requirement for this port? By default, IIS uses port 80 (HTTP) or 443 (HTTPS). If you are using 7060 simply because Visual Studio used it for local debugging, you should consider using the standard web ports for your server deployment.

IIS Bindings: Please provide a screenshot or a list of the current bindings for this site in IIS Manager.

Application State: Is the Application Pool started, and have you verified the site is running?

Without these details, we cannot move forward with SSL or domain configuration. Please provide the IIS binding information first.
Scott Huang 3,491 Reputation points

2026-02-14T06:43:50.1633333+00:00

Yes, it is IIS manager and the existing Https site is functioning well.
AgaveJoe 31,181 Reputation points

2026-02-14T14:51:13.68+00:00

I’m glad to hear the site is now functioning. Because we haven't received the specific IIS binding details or the configuration data requested, I'll assume you were able to resolve the port conflict independently. If the site is working as expected, there’s nothing more to troubleshoot here. I'll mark this as resolved.
Scott Huang 3,491 Reputation points

2026-02-14T14:59:28.04+00:00

As the current way is using 7060 port, do you mean we can change it to 443 port (or others)?

Are you sure no need to have the exact certificate on 7060 port?
AgaveJoe 31,181 Reputation points

2026-02-14T15:03:29.4233333+00:00
Whether you should change to port 443 depends entirely on your hosting requirements.

In standard web production environments:

Port 443 is the industry standard for HTTPS. It is usually open by default on most firewalls and allows users to access the site without typing a port number in the URL (e.g., https://yourdomain.com).

Port 7060 is a non-standard port. If you use it, users must explicitly type it into the URL (e.g., https://yourdomain.com:7060), and you must manually ensure that the server’s firewall and any corporate firewalls allow traffic on that specific port.

Since your HTTPS site is 'functioning well' as you stated, there is no technical requirement to change it unless you want to follow standard web conventions. Without knowing your specific network or business requirements, I cannot tell you which port you must use, only which one is standard.
Scott Huang 3,491 Reputation points

2026-02-14T15:09:25.1066667+00:00

So simply we no need to consider 7060 port (unless we really one day need that), and still go ahead with the current configuration, correct?

Thanks to you!
AgaveJoe 31,181 Reputation points

2026-02-14T15:17:47.11+00:00

If your current configuration is working on the standard HTTPS port (443) and your users can access the site, then yes—there is generally no reason to use port 7060.

However, because you haven't shared your specific IIS bindings, firewall settings, or architectural requirements, I cannot definitively confirm if your current setup is 'correct' for your environment.

The general rule is: Use port 443 for production HTTPS traffic unless you have a specific technical requirement to do otherwise. If the site is accessible and functioning on the standard port, you are following standard practice.
Scott Huang 3,491 Reputation points

2026-02-14T15:29:21.8266667+00:00

OK. I will share more regarding the binding (I will revert further).

For something like the port below, we can still adjust it to use the default one - 443 (like what we just talked about)?
AgaveJoe 31,181 Reputation points

2026-02-14T16:04:12.0233333+00:00

The WebApp1.http file you are editing is simply a testing tool within Visual Studio for sending local requests; it is not a configuration file for the IIS server or the application's actual behavior.

Changing a port number in a .http file only updates where the "Send Request" test button points. It does not open that port on the server, change your IIS bindings, or configure the production environment. To move to port 443, you must physically add that binding in IIS Manager and ensure your server's firewall is open.

The community, still, does not know how you've configured your remote IIS host or even if a remote host actually exists. Given your response, I'm not sure what is going on. But good luck.
Scott Huang 3,491 Reputation points

2026-02-16T02:30:27.6633333+00:00

It is fine below to run the project on the server and should I have the proper certificate on port 7060 to ensure that I can achieve the same on the client?
AgaveJoe 31,181 Reputation points

2026-02-16T12:54:38.43+00:00

The screenshot and your new comments don't address the core issue. You still haven't provided the environment details or answered the questions the community has asked. Please re-read my previous posts; until those points are addressed, we can't help you further.
Scott Huang 3,491 Reputation points

2026-02-16T15:30:46.7266667+00:00

The IIS server currently is working fine on port 443 since I can deploy the other projects on IIS server. What other change is needed to switch to port 443 for the current project?
AgaveJoe 31,181 Reputation points

2026-02-16T16:10:24.01+00:00

Hosting multiple projects on port 443 requires specific IIS Site Bindings with unique Host Headers and SNI enabled for each. Being able to deploy other projects only confirms IIS is installed; it doesn't mean this specific project's environment variables or launch settings are aligned with your server's bindings.

I've asked many times for the project configuration and each time you've share a client tool. Given that your responses are not on the same subject, I'm not convinced that you have an actual remote server. I'm sorry but I can no longer provide assistance.