|
Secure Shell
Re: remote port forwarding unstable Oct 20 2009 05:53AM Adriana Rodean (adrya1984 gmail com) (2 replies) Re: remote port forwarding unstable Oct 20 2009 05:03PM Quintin Beukes (quintin skywalk co za) (1 replies) |
|
|
Privacy Statement |
> Hey,
>
> How do you close the console? And, can you share the command with the
> list please.
The reason I'm asking this is that the fact it is a bind: address
already in use error, means the bind() call failed. So according to
the networking stack that port is still bound. A netstat command on
the remote server should definitely show this. The commands Greg
listed (the lsof -i :1026 and netstat -antp) will give you this
information.
Remember to run the 2 commands as root (lsof needs to be root, and for
netstat's -p to work as well).
Further, you can also try: netstat -antpl | grep :1026
This will filter into only showing matching listening ports. I often
do this because it's so easy to miss it among all those ports.
Q
[ reply ]