I found one way to temporarily listen to the port. I opened a remote shell and entered:
This technically creates a service that listen to port 7890. Now the nmap command shows,
Apparently, the port is now open, but no service is listening to it. I try to telnet to port 7890 both locally on the server and remotely from my local machine, but it fails.
The telnet connection from my local machine to the server also times out.
Since it times out, would it be proper to say that the issue is not related to the open/close ports anymore, but something else?
Code:
$ ls | nc -l -p 7890Code:
nmap localhost -p 7890Starting Nmap 7.93 ( https://nmap.org ) at 2024-07-25 09:37 UTCNmap scan report for localhost (127.0.0.1)Host is up (0.00013s latency).Other addresses for localhost (not scanned): ::1PORT STATE SERVICE7890/tcp open unknownNmap done: 1 IP address (1 host up) scanned in 0.04 secondsCode:
telnet localhost 7890Trying ::1...Connection failed: Connection refusedTrying 127.0.0.1...telnet: Unable to connect to remote host: Connection timed outSince it times out, would it be proper to say that the issue is not related to the open/close ports anymore, but something else?
Statistics: Posted by debber — 2024-07-25 10:13