From: alexandre.abreu@... (Alexandre Abreu) Date: 2002-01-09T02:00:09+09:00 Subject: Re : Once again, Net::Telnet problems with QNX 4.24 >>>>> "ts" writes: A>> This Ruby code fails with a timeout while trying to connect A>> (even with a greater timeout value (400)) on a QNX 4.24 node : ts> Well, have you try to have a dump log, to see why it fail ? ts> Perhaps, it don't find the right prompt A>> $session = Net::Telnet.new( {'Host' => '192.1.1.101', 'Timeout' => 10, A>> "Telnetmode" => true } ) ts> , "Dump_log" => "name_of_the_dump_file"}) A>> p serverResponse = $session.login('', '') Thank you for your answer, I tried your suggestion and came up with the following results : QNX 6.1 (SUCCESS) login part : < 0x00000: 6c 6f 67 69 6e 3a 20 login: > 0x00000: 6e 74 75 73 65 72 0d 00 ntuser.. < 0x00000: 6e 74 75 73 65 72 0d 0a ntuser.. < 0x00000: 50 61 73 73 77 6f 72 64 3a Password: > 0x00000: 6e 74 75 73 65 72 0d 00 ntuser.. < 0x00000: 0d 0a .. < 0x00000: 0d 0a 54 75 65 20 4a 61 6e 20 20 38 20 30 32 3a ..Tue Jan 8 02: < 0x00010: 34 39 3a 34 34 20 32 30 30 32 20 6f 6e 20 2f 64 49:44 2002 on /d < 0x00020: 65 76 2f 74 74 79 70 31 0d 0a 4c 61 73 74 20 6c ev/ttyp1..Last l .... blablabla ... QNX 4.24 (FAILURE) login part : < 0x00000: 57 65 6c 63 6f 6d 65 20 74 6f 20 51 4e 58 20 34 Welcome to QNX 4 < 0x00010: 2e 32 34 0d 0a 43 6f 70 79 72 69 67 68 74 20 28 ..24..Copyright ( < 0x00020: 63 29 20 51 4e 58 20 53 6f 66 74 77 61 72 65 20 c) QNX Software < 0x00030: 53 79 73 74 65 6d 73 20 4c 74 64 2e 20 31 39 38 Systems Ltd. 198 < 0x00040: 32 2c 31 39 39 37 0d 0a 6c 6f 67 69 6e 3a 20 2,1997..login: > 0x00000: 6e 74 75 73 65 72 0d 00 ntuser.. < 0x00000: 6e 74 75 73 65 72 0d 0a ntuser.. < 0x00000: 70 61 73 73 77 6f 72 64 3a password: .... and nothing. Ruby does not seems to send the password ... and it waits until timeout. Here the code : $session = Net::Telnet.new( {'Host' => '192.1.1.101', 'Timeout' => 10, "Telnetmode" => true, "Dump_log" => "log_telnet.txt"}) p serverResponse = $session.login( { 'Name' => '', 'Password' => '' } ) p $session.cmd( 'uname -a' ) Can you think of a reason for such a behaviour ? Thank you for your efforts .. Alexandre Abreu