This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 63%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJO%3C/text%3E%3C/svg%3E)
I created a VM with Windows 10 O.S. to use as a server. It turns out that the accuracy of a connection through port 7777 (TCP and UDP), has already been created as security rules both in the machine's firewall and in the Azure portal. The problem is that, when testing, it always gets the return that the port is closed or inaccessible. Could anyone/know how to help me with this situation?
is the port open locally? if it's Windows, test it using netstat
netstat -anb | findstr LISTENING
see if the port is listening
You can also test with telnet “, like:
Telnet localhost 7777
I ran the command instructed and this was the result:
I ran the command instructed and this was the result:
These are all open ports on that server, I don't see 7777, the application that was supposed to work on that port must be stopped.
try to
netstat -anb | findstr 7777
and see if something appears, make the same test with 3389
netstat -anb | findstr 3389
You will notice that the 3389 will show information that it is open and the 7777 will not
In this case the rules in nsg and firewall are right, the application is not running.
try to check if the application is started, or if it is not working on another port (the command netstat -anb will show all the service names on the respective ports)
I don't understand why port 7777 doesn't appear in the list. I created the security rule for it in the Azure portal and in the firewall of the machine
Hi @João Víctor Monteiro
the service you installed to work with that port must not be started or running.
The problem is not a firewall, the problem is the service that is not running
"o serviço que você instalou para funcionar com essa porta, não deve ter iniciado ou estar rodando.
O problema ai não é firewall, o problema é o serviço que não está rodando"
I haven't put any services to run yet, because every time I test if the port is open I get the return of an unreachable port
@João Víctor Monteiro
The rule is right, you have opened the door for access, but there is no door yet.
As soon as you install the service the access will work
actually the result was what you mentioned... port 7777 is apparently not open.
Do you have any documentation to guide me in creating this port?
@João Víctor Monteiro
These are two different concepts,
1 - open the port for external connection
2 - create a service and leave the port listening
You've already done the first step, the rules are right, but the connection doesn't work because step 2 wasn't done.
To do step 2, you need to install the service/app that will work on that port. For example:
Install IIS or SQL and change the default ports to this one.
So, whoever installs the service that will run on that port will have no problem, when you install the application and the port will work externally
Got it, I'll check it and later come back here with the result.
Thanks in advance for the clarifications
Get in touch if you need more help with this issue.
--please don't forget to "[Accept the answer]" if the reply is helpful--