In reply to a post by Anonymous:

My better half is supposed to download her work from a mail server on port 22.
We have turned off all firewalls, but can't 'telnet' it.
...
The Swiss company swears the server is working and accesible on port 22.
...
Can anyone here "telnet 212.243.7.194 22" ?

It is highly unusual to configure a mail server to use port 22, rather that is the assigned port for SSH communication. A SSH server does not respond to an initial connection, but waits dumbly for the client to initiate the handshake - See RFC4256, para. 3 et seq here. That would explain your inability to get any response from port 22 via telnet. More information on SSH can be found here.

Assuming that you are using Windows, a very good SSH client programme is PuTTY which can be found here. Note that the suite also includes both a SCP and a SFTP programme for transferring files using SSH.

If you are able to connect via SSH using your partner's username and password, you will need to be familiar with the command line interface on the remote server in order to achieve anything useful. That will also depend upon the user permissions assigned to your partner's login. In that case, you will need to talk to the company in Switzerland to find out the relevant filenames and folders and exactly what commands to use in order to transfer the files you need.

OP here.

Sorry, I should not have said 'mail server', it's only that
nslookup of 212.243.7.194 says mail.cls-communication.com

but in reality it's file download via Across translation software.
But in order for it to work, telnet on port 22 must be working.

For us the telnet on port 22 will NOT connect at all.
(while port 25 responds as 'gateway01.cls.communication.com')

What we REALLY NEED to know is:
(you may need to turn off your firewall(s))

can you telnet 212.243.7.194 22 ?

Is so please tell me what ISP / connection you are using.
THANKS, regards,
Martin

PS. Yes, they *could* just email the file, but that involves someones time = money, then some again when returning the file,
so at the moment, my better half does NOT get the work !

It's not a mail server. Others have suggested a Lotus Notes server.

john@mercury:~$ telnet 212.243.7.194 22 |od -x -a
0000000    7254    6979    676e    3220    3231    322e    3334    372e
          T   r   y   i   n   g  sp   2   1   2   .   2   4   3   .   7
0000020    312e    3439    2e2e    0a2e    6f43    6e6e    6365    6574
          .   1   9   4   .   .   .  nl   C   o   n   n   e   c   t   e
0000040    2064    6f74    3220    3231    322e    3334    372e    312e
          d  sp   t   o  sp   2   1   2   .   2   4   3   .   7   .   1
0000060    3439    0a2e    7345    6163    6570    6320    6168    6172
          9   4   .  nl   E   s   c   a   p   e  sp   c   h   a   r   a
HELO [email protected]
0000100    7463    7265    6920    2073    5e27    275d    0a2e    058b
          c   t   e   r  sp   i   s  sp   '   ^   ]   '   .  nl  vt enq
0000120    2999    f873    3bb9    3303    7928    ac5b    3d96    198f
         em   )   s   x   9   ; etx   3   (   y   [   , syn   =  si  em
0000140    1b66    41bb    8c16    6ae4    0c18    93f1    cc2b    3280
          f esc   ;   A syn  ff   d   j can  ff   q dc3   +   L nul   2
0000160    65a9    8dd6    cb77    a4cf    ea81    5e4d    cd4f    d22e
          )   e   V  cr   w   K   O   $ soh   j   M   ^   O   M   .   R
Connection closed by foreign host.
0000200    8062    d0c7    2ad7    318a    4124    cc31    7713
          b nul   G   P   W   *  nl   1   $   A   1   L dc3   w
0000216

Refer back to work support, suspect their instructions are not complete and they expect you to use not the translation software but some other software to do the file get.

Using telnet to get a file from a remote machine is very unusual.

Email if its under 5MB-10MB would be simplest, above that FTP is by far the simplest

In reply to a post by Anonymous:

OP here.
...
For us the telnet on port 22 will NOT connect at all.
(while port 25 responds as 'gateway01.cls.communication.com')
...
can you telnet 212.243.7.194 22 ?

Port 22 is assigned to SSH. Why are you insisting upon ignoring that and continuing to try to use Telnet? Your failure to see what is staring you in the face can only ever lead to doom and despair.

Telnet will never work as a SSH client. A SSH server will never respond to a telnet connection. Nobody can test the connection for you because it needs an authorised username in order to get any sort of response from the SSH server and it will not request that or even present a login interface. A SSH connection must be initiated by the client programme. That is how SSH is deliberately designed to work.

SSH might be described as "secure Telnet" since it uses a SSL/TLS transport mechanism to create an encrypted connection, which telnet cannot understand, but which achieves the same end as telnet - a console connection to the remote computer. I've already pointed you towards a Windows client SSH application (PuTTY). I'm sure you can research an alternative for yourself if using a different OS.

The use of telnet possibly arises as telnet to a port and getting a blank screen response rather than immediate return to command prompt, usually indicates the ability to get a TCP connection on that port.

Also worth adding that port assignments while following conventions are not hard coded, and thus it is possible for people to run whatever server they desire on whatever port.

In short, this is at the refer back to the firms IT department

In reply to a post by MrSaffron:

The use of telnet possibly arises as telnet to a port and getting a blank screen response rather than immediate return to command prompt, usually indicates the ability to get a TCP connection on that port.

Also worth adding that port assignments while following conventions are not hard coded, and thus it is possible for people to run whatever server they desire on whatever port.

In short, this is at the refer back to the firms IT department

And if the OP won't even try a SSH connection on a port which just happens to be assigned to SSH ..... ?

The telnet connects but nothing meaningfull happens in terms of telnet

For the IP address/port given, telnet elicits a response, ssh does not.

In reply to a post by john2007:

For the IP address/port given, telnet elicits a response, ssh does not.

Ok, guys, I won't bang my head against this particular wall any longer.