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

there is a response on port 22, from a bt connection here;
ok it just clears the screen, and if I type anything, a few seconds later get some gibberish, but a connection no doubt.

from a bt dynamic address, 86.144.y.z

In reply to a post by Renfrew:

A SSH server will never respond to a telnet connection.

That's not technically correct..

pob:~ mattm$ telnet xx.xx.net.uk 22
Trying 91.199.xx.xx...
Connected to xx.xx.net.uk.
Escape character is '^]'.
SSH-2.0-OpenSSH_4.3

The SSH responded with the greeting, you just can't do anything with it.

Matt

Ditto.

john@mercury:~$ telnet mercury 22
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
SSH-2.0-OpenSSH_5.5p1 Debian-6

In reply to a post by Renfrew:

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

You are missing the point! The OP was instructed by their Swiss server to 1st test the desired connectivity to the server by checking if TELNET Port 22 works before using the translation software. They are not expected to do the analysis and procurement of further s/ware that you propose.

For all of us, TELNET Port 22 does work to the extent that it shows Port 22 is live; we might even be able to use it had we OP's credentials and s/ware .

All OP wants is for his TELNET Port 22 to connect like ours. As, presumably, the only diff between us is our ISPs, therein must lie the issue. Can any other PLusnet user get the TELNET Port 22 to work?

It connects (Plusnet user), then halts at a blank cursor.

OP here again.

Thanks for all your help.

Just to clear things up:
We are meant to use the Across translation software (german...) to access the server and download file(s) to translate, the IP and port No. is in a setup file sent to us, we can't edit that, and shouldn't have to.
Across (the software) just reports it can't connect on 212.243.7.194 port 22.
The Across support people said to test if we can telnet that IP on port 22.
The response we get is:
"Could NOT OPEN connection to the host on port 22: Connect failed"
However other people get different response, e.g. ggremlin in an earlier post.
WHY ?

Today I have been advised by PlusNet to use
htttp://serversniff.net to do tcp-traceroute.
It works, it says IP [open] in the last step.

So, it would appear that we can REACH the server, but can't make it to respond to our telnet
or Across software.
Apparently other translators can, Across swears that they have tested it with our setup file.
So here we are,
STALEMATE...
no solution, no work !
Regards,
Martin

In reply to a post by Anonymous:

Across (the software) just reports it can't connect on 212.243.7.194 port 22.
The Across support people said to test if we can telnet that IP on port 22.
The response we get is:
"Could NOT OPEN connection to the host on port 22: Connect failed"

Today I have been advised by PlusNet to use
htttp://serversniff.net to do tcp-traceroute.
It works, it says IP [open] in the last step.

So, it would appear that we can REACH the server

No it doesn't, it means you can't reach the server. However serversniff.net can, so the server is up, but it is being blocked by your firewall or Plusnet.

Have you tried a proxy?

http://www.daveproxy.co.uk/

try a vpn i had a same prob and it sorted it out

In reply to a post by Anonymous:

Today I have been advised by PlusNet to use
htttp://serversniff.net to do tcp-traceroute.
It works, it says IP [open] in the last step.

There was no doubt whether the server's IP as a whole was reachable. It was whether its particular port 22 was reachable from you.