Connection data too fast

ns - Fri 18/04/2008 10:32:35 CEST +0200

I need a delay before a new line.

For example with username/password/command "username"/"password"/"command" I'll obtain something like this :

login: paodcomad

I tried with a vb script, same problem. I need a minimum delay, like that (not the same for each lines) :
set WshShell = CreateObject("WScript.Shell" )
WshShell.Run "\"C:\Program Files\PuTTY\kitty.exe\"" -load baby"
While WshShell.AppActivate("KiTTY") = FALSE : wscript.sleep 50 : Wend
wscript.sleep 150
WshShell.SendKeys "username{Enter}"
wscript.sleep 100
WshShell.SendKeys "password{Enter}"
wscript.sleep 1200
WshShell.SendKeys "exec username.profile{Enter}"
WshShell.SendKeys "cd /{Enter}ls{Enter}cd $HOME{Enter}ls{Enter}"

After login, I can use multiple lines as commands without problem.

Cyd - Fri 18/04/2008 12:13:15 CEST +0200

I have got the same problem that you have.
From now, the only delay I manage is the delay between the connection openning and the first command sending (see registry key [HKEY_CURRENT_USER\Software\9bis.com\KiTTY]). After that the whole script is sent to the session.
It works fine with many servers (all ssh !). But it is KO with one very slow telnet server.
I put this trouble into the wishlist. I think I can correct it by adding a second delay: seconds to wait between each lines of an autocommand script.
Look at this forum to be informed for the correction.

Cyd

Cyd - Sat 19/04/2008 16:11:05 CEST +0200

A new version is on line: kitty.exe.

I completly modify the auto-command managment.
From now, multi-lines commands are sent to the terminal line by line.
I've added two more delay parameters. They don't appear in the registry anymore, but in the kitty.ini file.

[KiTTY]
initdelay=2.0
commanddelay=0.1
bcdelay=5

• initdelay: it's the delay (in seconds) between KiTTY starting and the first autocommand line sending
• commandelay: it's the delay (in seconds) between two lines (the same between login and password, and password and command)
• bcdelay: it's the delay (in milliseconds) between each characters (should not be modify)

With this fix, I have no problems to connect my telnet server anymore.
Tell me if it is ok with you now ?

Cyd

ns - Tue 22/04/2008 09:49:26 CEST +0200

Perfect !

I tried to reduce delay. OK with :
initdelay=0.6
commanddelay=0
bcdelay=1

Then I changed "Background Style" from "Solid" to "Desktop" and I needed to change initdelay to 0.7.

Thanks a lot.

Cyd - Wed 23/04/2008 14:15:01 CEST +0200

Glad to see, it's ok with you now.

I guess delay depends on your machine, the protocol you use, and the server you want to reach. But if you find your right settings it's good.

sed - Tue 29/04/2008 10:25:07 CEST +0200

Hi there,

can this problem only be solved with VB scripts?

I\'m trying to make an automated command for the login (telnet) to cisco switches and afterwards directly go to enable modus. \n works for other commands but as soon as i put my password behind \n, it won\'t work anymore. If i test it on the console, I see, that there\'s a space sent before the PW.. Is there anything I can do to avoid this? (this problem appears on the first login and for enable modus.

---

Example:

registrykey: value= en \n 1234

output in cisco console while testing:
ciscoswitch#en
ciscoswitch# 1234
Translating \"1234\"...domain server (***.**.**.*)
% Unknown command or computer name, or unable to find computer address

normally it should be like this:
ciscoswitch>en
Password:

---

perhaps I\'m missing something...

thanks for any help..

Cyd - Tue 29/04/2008 12:19:30 CEST +0200

Hi sed
With telnet protocol there are two ways to make automation commands.

1) into Connection/Data panel
set Auto-login username with your login
set Auto-login password with your pass
set Command with your automatic command

2) into Connection/Data panel
put everything into your Command setting
ex: Command=login\n\ppassword\n\pcommand\n
\n: means send the characters
\p: means wait for 1 second (you can add several \p if you need)

Cyd

Answer

The forum is actually closed