#39 Connect to telnet via CMD bug

[Mikhail N. Karpov]

Hello!
PuttyND v.7.2 - v.7.4
Doesn't connect in new created tab to telnet via CMD, ex. putty -telnet 192.168.0.1
(v.7.1 works fine)
Thnx and sorry for my english.

[Noodle]

Oh, you have made it clear. I am not a native English speaker either.
I have some tests and found a issue: when connecting from cmdline, it will update the default protocol/port. This is wrong in a multi-tabs env. Though I have some test with telnet protocol on the 22 port, I am not sure if it fixs the issue you reported. So could you help to verify it with the attachment?

[Mikhail N. Karpov]

It still not connect via cmd.
Some tests:

I changed port on the telnet server to 22 - not connect too.
Changed back, ssh - port 22, telnet - port 23.

'putty -telnet 192.168.0.1 -port 22'
have some connect -
'So the password of the key, if any, is required for ea...
SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8'

But 192.168.0.1 is not ubuntu server!

'putty -ssh 192.168.0.1'
open connect, but not to 192.168.0.1, its opened default server at start window of puttynd.

[Noodle]

I see.

When you see SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8. It is connected to ssh server with telnet. Those words are raw data in ssh protocol.

And this would help. When the session is newed via cmdline, the putty-nd will store it as tmp/ip:port(in the case of "putty -telnet 192.168.0.1", it is tmp/192.168.0.1:23). So would you have a check on the session config. If it is ok, you could remove the sensitive info and export it for me? And another stupid question, could you have a check on the server that it is really listening on 23?

[Mikhail N. Karpov]

And another stupid question, could you have a check on the server that it is really listening on 23?
I have over 1000 devices with telnet servers in network, port 23 is default. 192.168.0.1 is a test sample.

Now I am at work, and here another default session but same problem.
No matter what server I wrote in cmd line - I am connected to server in "default session" with all its parameters, exclude protocol. In cmd line work protocol (-ssh/-telnet) and "-port" parameters. Destination address taken from default session ever.

PuttyND not create 'tmp/192.168.0.1:23' when I use cmdline and connect to 192.168.0.1, only when I normal connect via GUI .

I send reg and cfg files of default setings.

[Noodle]

wait a minute, I just open my computer.

[Noodle]

Please delete the defautsettings from the reg, the host and protocol is saved by mistake.

[Mikhail N. Karpov]

Thank you! It works now!

[Noodle]

And here comes the updated putty:

1. making the Default Settings's protocol/hostname/portnum unsavable.
2. disable the flag TOOLTYPE_HOST_ARG_CAN_BE_SESSION in cmdline to avoid the missed-saving of the tmp/session.