wodSSH cannot connect as telnet client to my AIX s (wodSSH / wodSSH.NET)
by Christophe, Wednesday, October 06, 2004, 10:58 (7364 days ago)
Hi,
I have an application in which I use wodSSH to connect with Telnet to Unix hosts. It works fine with Solaris and Linux, but it fails with my AIX 4.3 server.
I have also tried the samples that comes with wodSSH and I have exactly the same problem.
I am able to telnet this same AIX host using another telnet client tools.
Please help !
Re: wodSSH cannot connect as telnet client to my A
by wodSupport, Wednesday, October 06, 2004, 11:32 (7364 days ago) @ Christophe
Christope,
what exactly happens? Why it cannot connect? Do you get any errors?
Could we try to connect from here to duplicate the problem?
Re: wodSSH cannot connect as telnet client to my A
by Christophe, Wednesday, October 06, 2004, 13:09 (7364 days ago) @ wodSupport
Christope,
what exactly happens? Why it cannot connect? Do you get any errors?
Could we try to connect from here to duplicate the problem?
I have wrote a simple VB project with which I have the problem also:
Dim wodSSH1 As WODSSHCOMLib.wodSSHCom
wodSSH1 = New WODSSHCOMLib.wodSSHCom
wodSSH1.Protocol = WODSSHCOMLib.ProtocolsEnum.Telnet
wodSSH1.Blocking = True
wodSSH1.Hostname = AIX43
wodSSH1.Login = ocante
wodSSH1.Password = ocante
wodSSH1.Port = 23
wodSSH1.Timeout = 30
wodSSH1.Command = echo Hello
wodSSH1.Connect()
Print(wodSSH1.Receive)
After 30 seconds I have the following messages:
An unhandled exception of type 'System.Runtime.InteropServices.COMException' occurred in VB_Telnet.exe
Additional information: The current connection has timeout.
You will not be able to connect from outside.
I have recorded the network traffic while trying to telnet and I can see that something is coming from my AIX to my client host: AIX version 4
Copyrights...
Connexion : , but nothing is sent after that.
If it can help I can send you this network traffic (you can open it using ethereal: http://www.ethereal.com/). Tell me where I can send an attachment.
Re: wodSSH cannot connect as telnet client to my A
by wodSupport, Wednesday, October 06, 2004, 13:16 (7364 days ago) @ Christophe
Christophe,
this is very unusual. We will have to figure the way we can test this.
I would suggest you go to command prompt and enter
telnet your_server_name
but I assume this will work, right? You have tried it? Server is really accessible?
Can you please send us email to techsupport@weonlydo.com . We will create tunnel to your AIX so I need some info from you.
Regards.
Re: wodSSH cannot connect as telnet client to my A
by Christophe, Wednesday, October 06, 2004, 14:11 (7364 days ago) @ wodSupport
Yes it works from command prompt.
Unfortunatly I cannot let you access this machine from outside.
Here is the telnet negotiation between client (10.1.1.103) and server (10.1.2.199):
--------------------------------------------------------
10.1.2.199 -> 10.1.1.103
Telnet
Command: Don't Authentication Option
Command: Do Terminal Type
--------------------------------------------------------
10.1.1.103 -> 10.1.2.199
Telnet
Command: Won't Authentication Option
Command: Will Terminal Type
--------------------------------------------------------
10.1.2.199 -> 10.1.1.103
Telnet
Command: Do Terminal Type
Suboption Begin: Terminal Type
Send your Terminal Type
Command: Suboption End
--------------------------------------------------------
10.1.1.103 -> 10.1.2.199
Telnet
Command: Will Terminal Type
Suboption Begin: Terminal Type
Here's my Terminal Type
Value: vt100
Command: Suboption End
--------------------------------------------------------
10.1.2.199 -> 10.1.1.103
Telnet
Command: Will Echo
Command: Will Suppress Go Ahead
Command: Do Negotiate About Window Size
Command: Won't <unknown option>
Command: Do Echo
Data:
Data:
Data: telnet (chien)
Data:
00
Data:
Data:
00
--------------------------------------------------------
10.1.1.103 -> 10.1.2.199
Telnet
Command: Do Echo
Command: Do Suppress Go Ahead
Command: Will Negotiate About Window Size
Suboption Begin: Negotiate About Window Size
Width: 80
Height: 25
Command: Suboption End
Command: Don't <unknown option>
Command: Won't Echo
--------------------------------------------------------
10.1.2.199 -> 10.1.1.103
Telnet
Command: Don't Echo
--------------------------------------------------------
10.1.2.199 -> 10.1.1.103
Telnet
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
Data:
00
Data: AIX version 4
Data:
00
Data: (C) Copyrights by IBM and by others 1982, 1996.
Data:
00
Data: Connexion :
--------------------------------------------------------
and nothing more...
Hope it helps.
Re: wodSSH cannot connect as telnet client to my A
by wodSupport, Wednesday, October 06, 2004, 14:22 (7364 days ago) @ Christophe
Christophe,
what if you don't set Login and Password? Does your AIX at all send 'login:' prompt? Perhaps this is the reason it fails?
Re: wodSSH cannot connect as telnet client to my A
by Christophe, Wednesday, October 06, 2004, 14:43 (7364 days ago) @ wodSupport
Christophe,
what if you don't set Login and Password? Does your AIX at all send 'login:' prompt? Perhaps this is the reason it fails?
'login: ' is never prompted, my AIX use french language, 'Connexion :' is prompted instead of 'login: '
Can it be the problem ?
Re: wodSSH cannot connect as telnet client to my A
by wodSupport, Wednesday, October 06, 2004, 14:48 (7364 days ago) @ Christophe
Yes it can. It waits for 'login' or 'username' prompt. If you don't set corresponding properties, then wodSSH will just pass whatever is received to you - so you can login by yourself.
So, can you clear out Login and Password properties? Does that work?
Re: wodSSH cannot connect as telnet client to my A
by Christophe, Wednesday, October 06, 2004, 15:26 (7364 days ago) @ wodSupport
Yes it works, but how can I know when to send the login and password ? This time I was prompted for 'Connexion :' but it can change if I connect to another host.
Re: wodSSH cannot connect as telnet client to my A
by wodSupport, Wednesday, October 06, 2004, 15:47 (7364 days ago) @ Christophe
My point exactly - you cannot know this. Nor wodSSH can know. We typically wait for regular 'login' and 'username' prompts. Humans are smart and recognize when they're asked for a prompt, machines aren't.
Perhaps you can send it blindly upon connection, perhaps that would work.
But, on the other hand, you can't even be sure you will be asked for a prompt at all - telnet is so open and different among computers.