Skip to main content
added 352 characters in body
Source Link
grawity_u1686
  • 465.3k
  • 66
  • 977
  • 1.1k

If you get a Permission denied error message from SSH, that means you were successfuly talking to the SSH server up until that point – you connected to it, your client was able to start the authentication process and everything. Which means ports are definitely not the problem.

My old computer on my same home network is connecting with no issues so i wonder why would the server reject a request coming from the same IP? and what would be the issue that the server administrator need to correct on their end?

The rejection is not based on IP address, it's based on the user login information (password or SSH keypair) that you provided. Assuming you're providing the correct keypair (id_rsa, etc.), the server administrator can look at the server's sshd logs to find out why it is still being rejected.

(It's of course possible that your client just isn't sending the correct keypair, or the correct password. Check with ssh -v ... first.)

i used an ftp client and i got a new one, but i get refusal to connect.

FTP/FTPS is not SFTP. They're different protocols, hosted by different software, and they will be running on different ports (SFTP uses the SSH port).

Some clients support both (e.g. Cyberduck and Transmit certainly do SFTP in addition to FTP/FTPS), but even in those cases you need to specifically select SFTP (not to be confused with FTPS).

none of them is listed as an sftp port tho

Because it's listed as an SSH port, exactly like in your first nmap (the one with -p 22).

If you get a Permission denied error message from SSH, that means you were successfuly talking to the SSH server up until that point – you connected to it, your client was able to start the authentication process and everything. Which means ports are definitely not the problem.

My old computer on my same home network is connecting with no issues so i wonder why would the server reject a request coming from the same IP? and what would be the issue that the server administrator need to correct on their end?

The rejection is not based on IP address, it's based on the user login information (password or SSH keypair) that you provided.

i used an ftp client and i got a new one, but i get refusal to connect.

FTP/FTPS is not SFTP. They're different protocols, hosted by different software, running on different ports.

Some clients support both (e.g. Cyberduck and Transmit certainly do SFTP in addition to FTP/FTPS), but even in those cases you need to specifically select SFTP (not to be confused with FTPS).

none of them is listed as an sftp port tho

Because it's listed as an SSH port, exactly like in your first nmap (the one with -p 22).

If you get a Permission denied error message from SSH, that means you were successfuly talking to the SSH server up until that point – you connected to it, your client was able to start the authentication process and everything. Which means ports are definitely not the problem.

My old computer on my same home network is connecting with no issues so i wonder why would the server reject a request coming from the same IP? and what would be the issue that the server administrator need to correct on their end?

The rejection is not based on IP address, it's based on the user login information (password or SSH keypair) that you provided. Assuming you're providing the correct keypair (id_rsa, etc.), the server administrator can look at the server's sshd logs to find out why it is still being rejected.

(It's of course possible that your client just isn't sending the correct keypair, or the correct password. Check with ssh -v ... first.)

i used an ftp client and i got a new one, but i get refusal to connect.

FTP/FTPS is not SFTP. They're different protocols, hosted by different software, and they will be running on different ports (SFTP uses the SSH port).

Some clients support both (e.g. Cyberduck and Transmit certainly do SFTP in addition to FTP/FTPS), but even in those cases you need to specifically select SFTP (not to be confused with FTPS).

none of them is listed as an sftp port tho

Because it's listed as an SSH port, exactly like in your first nmap (the one with -p 22).

Source Link
grawity_u1686
  • 465.3k
  • 66
  • 977
  • 1.1k

If you get a Permission denied error message from SSH, that means you were successfuly talking to the SSH server up until that point – you connected to it, your client was able to start the authentication process and everything. Which means ports are definitely not the problem.

My old computer on my same home network is connecting with no issues so i wonder why would the server reject a request coming from the same IP? and what would be the issue that the server administrator need to correct on their end?

The rejection is not based on IP address, it's based on the user login information (password or SSH keypair) that you provided.

i used an ftp client and i got a new one, but i get refusal to connect.

FTP/FTPS is not SFTP. They're different protocols, hosted by different software, running on different ports.

Some clients support both (e.g. Cyberduck and Transmit certainly do SFTP in addition to FTP/FTPS), but even in those cases you need to specifically select SFTP (not to be confused with FTPS).

none of them is listed as an sftp port tho

Because it's listed as an SSH port, exactly like in your first nmap (the one with -p 22).