OpenVMS: Connecting and Issuing Commands - WeOnlyDo Discussion board

OpenVMS: Connecting and Issuing Commands (wodSSH / wodSSH.NET)

by mmorton, Friday, July 03, 2009, 20:02 (3392 days ago)

Hi,

I am currently trying to connect to an OpenVMS system using the wodSSH.Net component. When I connect I get the following message.

SET-W-NOTSET, error modifying TNA199: -SET-I-UNKTERM, unknown terminal type

I have tried setting the TerminalType to tty, dumb and vt100 but none of them work. If I try to ignore the message and issue some commands it doesnt work as it just echos the command back and nothing else.

I have run the same code successfully on Tru64, HP-UX etc so I am assuming that its the intial message that is causing the problem.

Has anyone got any ideas on how to fix this?

Thanks in advance
Mike

Re: OpenVMS: Connecting and Issuing Commands

by wodDamir, Friday, July 03, 2009, 20:10 (3392 days ago) @ mmorton

Hi Mike,

What if you try some other client? I.e: Putty?

Does it work?

If so, can you please try setting TerminalType property to xterm and try it out?

Regards,
Damba

Re: OpenVMS: Connecting and Issuing Commands

by mmorton, Friday, July 03, 2009, 20:16 (3392 days ago) @ wodDamir

Hi,

I have tried xterm and it is still the same.

I can successfully connect and issue commands using the windows telnet client and putty.

Regards
Mike

Re: OpenVMS: Connecting and Issuing Commands

by wodDamir, Friday, July 03, 2009, 20:23 (3392 days ago) @ mmorton

Mike,

Is there any chance we could connect to that server?

We need to somehow duplicate this behaviour on our side. Is that possible?

If so, you can send any private data to techsupport@weonlydo.com

Regards,
Damba

Re: OpenVMS: Connecting and Issuing Commands

by mmorton, Friday, July 03, 2009, 20:27 (3392 days ago) @ wodDamir

Hi,

Unfortunatly its an internal server and so I could not give you access. If I connect through putty I get the standard company logon banner etc but through wodSSH.NET I get the error and nothing else.

Is there any troubleshooting steps I could follow or try?

Thanks
Mike

Re: OpenVMS: Connecting and Issuing Commands

by wodDamir, Friday, July 03, 2009, 21:07 (3392 days ago) @ mmorton

Mike,

What protocol does this happen with? SSH or Telnet?

If it occurs with SSH, can you please do telnet your_server 22 and tell me what you receive back?

Regards,
Damba

Re: OpenVMS: Connecting and Issuing Commands

by mmorton, Friday, July 03, 2009, 21:23 (3392 days ago) @ wodDamir

Hi,

I connecting using telnet.

If I uncomment the following lines from my code I recieve the correct bannor and dont get an error message.

[code]
sshConnection.Authentication = weOnlyDo.Client.SSH.Authentications.Password
sshConnection.Login = auth_details.UserName
sshConnection.Password = auth_details.Password
[/code]

Does this mean that wodSSH.net is not successfully passing the username and password?

The banner has some text 'blah blah blah'. Then the prompt is 'Username: ' (without the quotes).

Thanks
Mike

Re: OpenVMS: Connecting and Issuing Commands

by wodDamir, Friday, July 03, 2009, 21:40 (3392 days ago) @ mmorton

Mike,

I can't really say without reproducing the same issue. What If you login manually?

Can you execute commands?

Regards,
Damba

Re: OpenVMS: Connecting and Issuing Commands

by mmorton, Tuesday, July 07, 2009, 14:36 (3388 days ago) @ wodDamir

Hi,

Unfortunatly the terminaltype error message was not causing the problem of not being able to connect and issue commands.

It turns out that I had to use vbCrLf in VB.NET at the end of each command.

I have been using Chr(10) and vbLf on the other UNIX systems and this works however this isnt the case on OpenVMS.

So all fixed.

Thanks
Mike

Re: OpenVMS: Connecting and Issuing Commands

by mmorton, Tuesday, July 07, 2009, 23:16 (3387 days ago) @ mmorton

Hi,

If anyone ever has this error message then you can resolve this by responding to the escape chars that VMS sends out. Not sure if this is relevant to any other OS types.

[code]
sshConnection.Connect()
sshConnection.WaitFor(Chr(27) & [c )
sshConnection.Execute(Chr(27) & [?1;1c , regex:[$ #>] , 30)
[/code]

This resolves the issue and tells VMS the terminal type.

Regards
Mike