Server Automation Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

Global Shell telnet issue

Valued Contributor

Global Shell telnet issue

Hi,

 

Im having issue when using the default Terminal Client command for windows telnet :

 

cmd /c start /w cmd /c "(telnet %h %p || echo > nul) && echo %m && pause > nul"

 

when i click "test" it opened the cmd but displays 'telnet' is not recognized as an internal or external command,

but when trying the telnet locally it is ok.

 

 

Do you have any idea about this?

 

 

 

 

 

sdeff

4 REPLIES
Highlighted
HPE Expert

Re: Global Shell telnet issue

[ Edited ]

Hi sdeff,

 

Possibly your native telnet client on your windows machine is not turned on.

On Win 7 it is disabled by default.

 

You may want to have a look at this topic :

 

http://social.technet.microsoft.com/wiki/contents/articles/910.enabling-telnet-client-in-windows-7.aspx

 

 


Cheers,

Lyubo


Lyubomir MInchev
SA Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution. Also, if you liked this post please consider providing Kudos at the left-hand side.
Valued Contributor

Re: Global Shell telnet issue

hi lyubo,

 

Im sure telnet feature is on because when trying telnet locally it works. But when trying to test the telnet in SA it doesn't work.

 

 

Regards,

Sdeff

HPE Expert

Re: Global Shell telnet issue

[ Edited ]

Hi sdeff,

 

You can also use putty instead:

 

"C:\\path-to-the-installed-putty\\putty.exe" -telnet %h %p

 


Cheers,

Lyubo

 

 

 


Lyubomir MInchev
SA Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution. Also, if you liked this post please consider providing Kudos at the left-hand side.
Trusted Contributor

Re: Global Shell telnet issue

Hello Sdeff,

 

This could be a problem related to syswow64 in windows 64-bit. You can search for that, it is a Windows feature. So bottom line is it is possible that the telnet command is a 64-bit executable and the java client is a 32-bit executable. The 32-bit executables don't have access to 64-bit space, so telnet is not found. You could test this by running a 32-bit cmd.exe from C:\windows\SysWOW64 and if it happens it is because telnet exists in the 64-bit system32 but not in the 32-bit.

 

This is the same feature governing Program Files (x86) and Program Files, from a 32-bit process the (x86) folder becomes "C:\Program Files\"

 

Using putty will eliminate the problem provided it is in a 32-bit accessible path. Alternatively you can copy telnet.exe to be accessible within syswow64 (eg: the path C:\windows\SysWOW64 )

 

Hope this helps,

Filippos Chalvatzoglou

 

 

--
Filippos Chalvatzoglou
Server Automation & BSA Essentials Support
HP Software

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.

Help us keep these forums active!