The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
What may be wrong?
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
We have two smartphones, a Samsung S10 and a Samsung A53. On both phones
I installed a SSH server. ón my pc (Windows 10 Pro) I have an FTP
client, CuteFTP 9.3. With this client I can make a connection with the
A53 phone, after starting up the SSH server. Very easy!
However, with the S10 phone it won't work. The same SSH server, a
different user name and password. If I try to make a connection, there
is an error. This shows up in the client on the pc:
STATUS:> [04/02/2024 13:45:21] Getting listing ""...
STATUS:> [04/02/2024 13:45:21] Connecting to SFTP server...
192.168.1.160:2222 (ip = 192.168.1.160)...
ERROR:> [04/02/2024 13:45:22] Disconnect: key exchange failed.
ERROR:> [04/02/2024 13:45:22] Check security settings; make sure that
the username and password are correct, and that the chosen encryption
algorithms are supported by server.
STATUS:> [04/02/2024 13:45:22] Can't connect to 192.168.1.160:2222. >> STATUS:> [04/02/2024 13:45:22] SFTP connection closed.
The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
Something is failing in the negotiation when you connect, but not enough
info to be clear what it is.
Open a Windows command prompt or Powershell and type:
ssh -vvv -p 2222 phone_username@192.168.1.160
(assuming that is the IP of the phone, replacing phone_username with the username you configured on the phone)
and post the log here.
As a wild guess it's possible the SSH server is configured to use SSH keys rather than password authentication, but I'm not familiar with the way CuteFTP logs things to be sure.
Theo
Fokke Nauta, 2024-02-04 14:02:
[...]
The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
What may be wrong?
Just to be sure that it's not a issue with the client, try FileZilla:
<https://filezilla-project.org/>
Hi all,
We have two smartphones, a Samsung S10 and a Samsung A53. On both phones
I installed a SSH server. ón my pc (Windows 10 Pro) I have an FTP
client, CuteFTP 9.3. With this client I can make a connection with the
A53 phone, after starting up the SSH server. Very easy!
However, with the S10 phone it won't work. The same SSH server, a
different user name and password. If I try to make a connection, there
is an error. This shows up in the client on the pc:
STATUS:> [04/02/2024 13:45:21] Getting listing ""...
STATUS:> [04/02/2024 13:45:21] Connecting to SFTP server... 192.168.1.160:2222 (ip = 192.168.1.160)...
ERROR:> [04/02/2024 13:45:22] Disconnect: key exchange failed. ERROR:> [04/02/2024 13:45:22] Check security settings; make sure that the username and password are correct, and that the chosen encryption algorithms are supported by server.
STATUS:> [04/02/2024 13:45:22] Can't connect to 192.168.1.160:2222. STATUS:> [04/02/2024 13:45:22] SFTP connection closed.
The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
On 05/02/2024 11:51, Theo wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
Hi all,
We have two smartphones, a Samsung S10 and a Samsung A53. On both phones >>> I installed a SSH server. ón my pc (Windows 10 Pro) I have an FTP
client, CuteFTP 9.3. With this client I can make a connection with the
A53 phone, after starting up the SSH server. Very easy!
However, with the S10 phone it won't work. The same SSH server, a
different user name and password. If I try to make a connection, there
is an error. This shows up in the client on the pc:
STATUS:> [04/02/2024 13:45:21] Getting listing ""...
STATUS:> [04/02/2024 13:45:21] Connecting to SFTP server... >>> 192.168.1.160:2222 (ip = 192.168.1.160)...
ERROR:> [04/02/2024 13:45:22] Disconnect: key exchange failed.
ERROR:> [04/02/2024 13:45:22] Check security settings; make >>> sure that
the username and password are correct, and that the chosen encryption
algorithms are supported by server.
STATUS:> [04/02/2024 13:45:22] Can't connect to
192.168.1.160:2222.
STATUS:> [04/02/2024 13:45:22] SFTP connection closed.
The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
Something is failing in the negotiation when you connect, but not enough
info to be clear what it is.
Open a Windows command prompt or Powershell and type:
ssh -vvv -p 2222 phone_username@192.168.1.160
(assuming that is the IP of the phone, replacing phone_username with the
username you configured on the phone)
and post the log here.
As a wild guess it's possible the SSH server is configured to use SSH
keys
rather than password authentication, but I'm not familiar with the way
CuteFTP logs things to be sure.
Theo
Thanks.
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
Fokke
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
Fokke Nauta, 2024-02-05 12:11:
[...]
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
You should also be able to select the text in the command prompt windows
and copy it without redirecting the output of ssh to a file.
how do I select the text in the command prompt window?
Fokke Nauta wrote:
how do I select the text in the command prompt window?
Drag a rectangular area with the mouse to select, press enter to copy
On 05/02/2024 11:51, Theo wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
On 2024-02-05 12:11, Fokke Nauta wrote:
On 05/02/2024 11:51, Theo wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
I opened the command prompt and saw a long log text, but I didn't
manage yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
Do you have a formatted floppy in the drive?
On 05/02/2024 20:23, Carlos E.R. wrote:
On 2024-02-05 12:11, Fokke Nauta wrote:
On 05/02/2024 11:51, Theo wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
I opened the command prompt and saw a long log text, but I didn't
manage yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
Do you have a formatted floppy in the drive?
Floppy? Floppy drive?
We don't have this for many years!
Carlos E.R. wrote:
Do you have a formatted floppy in the drive?
Floppy? Floppy drive?
We don't have this for many years!
On 2024-02-05 21:16, Fokke Nauta wrote:
On 05/02/2024 20:23, Carlos E.R. wrote:
On 2024-02-05 12:11, Fokke Nauta wrote:
On 05/02/2024 11:51, Theo wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
I opened the command prompt and saw a long log text, but I didn't
manage yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
Do you have a formatted floppy in the drive?
Floppy? Floppy drive?
We don't have this for many years!
Then why do you tell the shell to dump the text to a floppy? It is
clearly there:
... > A:\msg.txt
Fokke Nauta wrote:
Carlos E.R. wrote:
Do you have a formatted floppy in the drive?
Floppy? Floppy drive?
We don't have this for many years!
traditionally A: was a floppy drive ...
Fokke Nauta, 2024-02-05 12:11:
[...]
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
You should also be able to select the text in the command prompt windows
and copy it without redirecting the output of ssh to a file.
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2[snip]
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug1: Connection established.
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/id_rsa error:2
debug2: PTY allocation request accepted on channel 0
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
:/ $
There are errors, but I don't know how this works.
[C:\Program Files\JPSoft\TCCLE14x64] ssh -vvv -p 2222 slauf@192.168.1.160 OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug3: finish_connect - ERROR: async io completed with error: 10060, io:000002AAF3CBF930
debug1: connect to address 192.168.1.160 port 2222: Connection timed out
ssh: connect to host 192.168.1.160 port 2222: Connection timed out
Fokke Nauta <usenet@solfon.nl> wrote:
You probably need something like:-
I opened the command prompt and saw a long log text, but I didn't manage
yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
ssh -vvv -p 2222 slauf@192.168.1.160 >A:\msg.txt 2>&1
The '2>&1' redirects stderr to stdout (which is already going to msg.txt)
On 05/02/2024 15:02, Chris Green wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
You probably need something like:-
I opened the command prompt and saw a long log text, but I didn't manage >> yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
ssh -vvv -p 2222 slauf@192.168.1.160 >A:\msg.txt 2>&1
The '2>&1' redirects stderr to stdout (which is already going to msg.txt)
I tried this in the command prompt. It asked for the password, which I entered. And indeed, this worked. Thanks. I will copy the content here.group14-sha1,ext-info-c
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug1: Connection established.
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version SSH Server
- Banana Studio
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group1-sha1
debug2: host key algorithms: ecdsa-sha2-nistp256
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96 debug2: MACs stoc: hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96
debug2: reserved 0
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: Authentications that can continue: password,keyboard-interactive,publickey
debug3: start over, passed a different list password,keyboard-interactive,publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
Password authentication
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to 192.168.1.160 ([192.168.1.160]:2222).
:/ $
There are errors, but I don't know how this works.
Fokke Nauta <usenet@solfon.nl> wrote:group14-sha1,ext-info-c
On 05/02/2024 15:02, Chris Green wrote:
Fokke Nauta <usenet@solfon.nl> wrote:
You probably need something like:-
I opened the command prompt and saw a long log text, but I didn't manage >>>> yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
ssh -vvv -p 2222 slauf@192.168.1.160 >A:\msg.txt 2>&1
The '2>&1' redirects stderr to stdout (which is already going to msg.txt) >>>
I tried this in the command prompt. It asked for the password, which I
entered. And indeed, this worked. Thanks. I will copy the content here.
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug1: Connection established.
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version SSH Server
- Banana Studio
debug3: order_hostkeyalgs: prefer hostkeyalgs:
ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug2: KEX algorithms:
curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-
rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsadebug2: host key algorithms:
ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,
debug2: ciphers ctos:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc:
chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc:
umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: peer server KEXINIT proposal
debug2: KEX algorithms:
diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group1-sha1
debug2: host key algorithms: ecdsa-sha2-nistp256
debug2: ciphers ctos:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,aes128-cbc,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos:
hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96
debug2: MACs stoc:
hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5,hmac-sha1-96,hmac-md5-96
debug2: reserved 0
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256
compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256
compression: none
debug1: Authentications that can continue:
password,keyboard-interactive,publickey
debug3: start over, passed a different list
password,keyboard-interactive,publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
Password authentication
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to 192.168.1.160 ([192.168.1.160]:2222).
:/ $
There are errors, but I don't know how this works.
SSH is negotiating various options - you would never have every possibility set up but it looks to find something the client and server can agree on.
I trimmed the list above which shows you successfully got in. As to why CuteFTP doesn't work we don't know in the absence of a similar log, but a stab in the dark might be the limited range of KEX (key exchange), host key algorithms, ciphers and HMACs. In the second block the client says which algorithms it supports, then the third block the server says what it can do, and in the fourth block they settle on a subset that both can do. In this case the list from the server looks a bit limited, and I wonder if CuteFTP also supports a limited and non-overlapping list. If that happens they couldn't agree on a subset and the connection would fail.
You could try and see if the CuteFTP config has any options to enable ciphers/KEX/host key algs/HMACs and tick them all. Failing that, maybe there's an option in CuteFTP to give a more detailed log of what it's trying to do and possible to spot what's going wrong.
Theo
Fokke Nauta wrote:
[C:\Program Files\JPSoft\TCCLE14x64] ssh -vvv -p 2222 slauf@192.168.1.160
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug3: finish_connect - ERROR: async io completed with error: 10060,
io:000002AAF3CBF930
debug1: connect to address 192.168.1.160 port 2222: Connection timed out
ssh: connect to host 192.168.1.160 port 2222: Connection timed out
Is this to the "other" phone?
can you open s terminal window in that phone itself (i.e. not across the network)
Is one phone rooted and the other is not?
Fokke Nauta wrote:
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2[snip]
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug1: Connection established.
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/id_rsa error:2
debug2: PTY allocation request accepted on channel 0
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
:/ $
There are errors, but I don't know how this works.
The errors I see are just from it looking for optional files which don't exist in your case, but it looks like it actually succeeded and you
arrive at a $ prompt
What happens when you type shell commands after that?
On 07/02/2024 10:48, Andy Burns wrote:
Fokke Nauta wrote:No, this is the same phone, the S10. None of the phones are rooted.
[C:\Program Files\JPSoft\TCCLE14x64] ssh -vvv -p 2222
slauf@192.168.1.160
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug3: finish_connect - ERROR: async io completed with error: 10060,
io:000002AAF3CBF930
debug1: connect to address 192.168.1.160 port 2222: Connection timed out >>> ssh: connect to host 192.168.1.160 port 2222: Connection timed out
Is this to the "other" phone?
can you open s terminal window in that phone itself (i.e. not across
the network)
Is one phone rooted and the other is not?
Fokke
A:\msg.txt 2>&1.
On 05/02/2024 16:20, Arno Welzel wrote:
Fokke Nauta, 2024-02-05 12:11:
[...]
I opened the command prompt and saw a long log text, but I didn't manage >> yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
You should also be able to select the text in the command prompt windows and copy it without redirecting the output of ssh to a file.
Thanks. That worked! The result:
[C:\Program Files\JPSoft\TCCLE14x64] ssh -vvv -p 2222 slauf@192.168.1.160 OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug3: finish_connect - ERROR: async io completed with error: 10060, io:000002AAF3CBF930
debug1: connect to address 192.168.1.160 port 2222: Connection timed out
ssh: connect to host 192.168.1.160 port 2222: Connection timed out
Which commands should I use? In the command prompt?
Fokke Nauta <usenet@solfon.nl> wrote:
On 05/02/2024 16:20, Arno Welzel wrote:
Fokke Nauta, 2024-02-05 12:11:
[...]
I opened the command prompt and saw a long log text, but I didn't manage >>>> yet to get it into a text file.
I used ssh -vvv -p 2222 slauf@192.168.1.160 > A:\msg.txt
There is a file called msg.txt but it is empty.
Perhaps I should use Powershell?
You should also be able to select the text in the command prompt windows >>> and copy it without redirecting the output of ssh to a file.
Thanks. That worked! The result:
[C:\Program Files\JPSoft\TCCLE14x64] ssh -vvv -p 2222 slauf@192.168.1.160
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug3: Failed to open file:C:/Users/Fokke Nauta/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolve_canonicalize: hostname 192.168.1.160 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.1.160 [192.168.1.160] port 2222.
debug3: finish_connect - ERROR: async io completed with error: 10060,
io:000002AAF3CBF930
debug1: connect to address 192.168.1.160 port 2222: Connection timed out
ssh: connect to host 192.168.1.160 port 2222: Connection timed out
Maybe your phone changed IP and isn't 192.168.1.160 any more?
Fokke Nauta wrote:
Which commands should I use? In the command prompt?
pwd
ls
would be good to start with
Tried it in the command prompt:
[C:\Program Files\JPSoft\TCCLE14x64]pwd
TCC: Unknown command "pwd"
[C:\Program Files\JPSoft\TCCLE14x64]ls
TCC: Unknown command "ls"
Hi all,
We have two smartphones, a Samsung S10 and a Samsung A53. On both phones
I installed a SSH server. ón my pc (Windows 10 Pro) I have an FTP
client, CuteFTP 9.3. With this client I can make a connection with the
A53 phone, after starting up the SSH server. Very easy!
However, with the S10 phone it won't work. The same SSH server, a
different user name and password. If I try to make a connection, there
is an error. This shows up in the client on the pc:
STATUS:> [04/02/2024 13:45:21] Getting listing ""... STATUS:> [04/02/2024 13:45:21] Connecting to SFTP server... 192.168.1.160:2222 (ip = 192.168.1.160)...
ERROR:> [04/02/2024 13:45:22] Disconnect: key exchange failed. ERROR:> [04/02/2024 13:45:22] Check security settings; make sure that the username and password are correct, and that the chosen
encryption algorithms are supported by server.
STATUS:> [04/02/2024 13:45:22] Can't connect to 192.168.1.160:2222. STATUS:> [04/02/2024 13:45:22] SFTP connection closed.
The user name and password is OK, no problem there. The chosen
encryption algorithms are the same on both phones, as the configuration
of the SSH servers on the phone is the same, apart from the user names
and passwords. But they are correct.
What may be wrong?
Many thanks in advance for your help.
With regards,
Fokke Nauta
Fokke Nauta wrote:
Tried it in the command prompt:
[C:\Program Files\JPSoft\TCCLE14x64]pwd
TCC: Unknown command "pwd"
[C:\Program Files\JPSoft\TCCLE14x64]ls
TCC: Unknown command "ls"
When you use your ssh command, do you end-up at a dollar prompt
debug2: shell request accepted on channel 0
:/ $
or is that some sort of slanted smiley that you typed?
What is a slanted smiley?
On 04/02/2024 14:02, Fokke Nauta wrote:
Hi all,
I'm almost there!
On the S10 phone I removed the SSH server and installed a FTP server.
And this works, apart from the fact that there is a problem with the directory where the photo's are.
I installed Total Commander File Explorer on the phone and found out
where the photo's are:
/storage/emulated/0/DCIM/Camera
I programmed this in my FTP client on the PC, but it comes with an error:
STATUS:> [07/02/2024 16:45:47] This site supports LANG. COMMAND:> [07/02/2024 16:45:47] OPTS UTF8 on
[07/02/2024 16:45:47] 200 Command OPTS okay. STATUS:> [07/02/2024 16:45:47] This site can resume broken downloads.
COMMAND:> [07/02/2024 16:45:47] MODE Z
[07/02/2024 16:45:47] 200 Command MODE okay.
COMMAND:> [07/02/2024 16:45:47] REST 0
[07/02/2024 16:45:47] 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer.
COMMAND:> [07/02/2024 16:45:47] CWD /storage/emulated/0/DCIM/Camera
[07/02/2024 16:45:47] 550 No such directory. ERROR:> [07/02/2024 16:45:47] Requested action not taken (e.g., file or directory not found, no access).
What may be wrong?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 10:49:05 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,371 |