Issue with ports 12000 for udp and port 13000 for tcp

Hello,

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 127.0.0.1:13000 external connections would not be possible and you would need to change the bind address to 0.0.0.0:13000.

Hope that this helps!

Best,

Bobby

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.

Regards,

Alex

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.