Issue with ports 12000 for udp and port 13000 for tcp

  • Posted on February 10, 2022
  • SuPaAsked by Su Pa

I have opened these ports in networking/firewalls but when i run: telnet 13000 returns: Unable to connect to remote host: Connection refused

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 10, 2022


As already mentioned in order for you to be able to connect to one of those reports, you need to actually have a service listening on the specific ports.

You can check this with the netstat command:

netstat -plant | grep 13000

Also, note that if the service has a bind address as external connections would not be possible and you would need to change the bind address to

Hope that this helps!



Site Moderator
Site Moderator badge
February 10, 2022

Hello @sungpak,

Another thing to mention is that both ports need to be open for outgoing connections on your machine (PC or laptop) as well. You can temporary disable your local Firewall and perform the telnet connection again and see if there is any difference.



Site Moderator
Site Moderator badge
February 10, 2022

Hey @sungpak,

Is something actually listening on those ports? In order to connect to a certain port or in your case use telnet(again connect to it), there must be something that’s listening on it.

Let’s say you want to connect to port 80 on which usually either Apache or Nginx are listening. In neither are listening on the port 80 and port 80 is not used for anything, you won’t be able to telnet to it, same goes for ports 12000 and 13000.