IBM i Global

IBM i Global

Connect, learn, share, and engage with IBM Power.

 View Only

  • 1.  VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Sat February 17, 2024 07:07 AM

    Hi,

    While trying to connect IBM i ip address using VS Code I am getting this error :- "'Not connected to ip address while waiting for handshake'

    How to resolve this error?

    Thanks



    ------------------------------
    jerry ven
    ------------------------------


  • 2.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 01:57 AM

    Have you checked your ip address configured in your Code for IBM i connection? Can you ping the ip address from your workstation? Have you checked the documentation for Code for IBM i? If you're unable to solve your configuration problem yourself by searching the documentation or checking the Issues section for similar problems and solutions to this, please raise a new issue.

    The best support for open source applications are typically found via the open source repository - for Code for IBM i, it's here:https://github.com/codefori/vscode-ibmi



    ------------------------------
    Christian Jorgensen
    IT System Administrator
    Network of Music Partners A/S
    ------------------------------

    Original Message


  • 3.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 02:24 AM

    Here's another link to check - the requirements, especially the SSH server on IBM i... which is the basis for Code for IBM i communication.

    Without it, no connection...



    ------------------------------
    Christian Jorgensen
    IT System Administrator
    Network of Music Partners A/S
    ------------------------------

    Original Message


  • 4.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 02:28 AM

    Sorry for double-posting ;)



    ------------------------------
    Sylvain Manceau
    ------------------------------

    Original Message


  • 5.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 02:27 AM

    Hi,

    You must have SSH enabled and running on your IBM i: https://codefori.github.io/docs/#/./README?id=requirements.

    Also, what gives an ordinary SSH connection to your IBM i, using a terminal emulator like PuTTY?



    ------------------------------
    Sylvain Manceau
    ------------------------------

    Original Message


  • 6.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 02:43 AM

    Hi,

    I can connect to IBM i ( using same ip address, user name and password) using RDI ( can open it in editor/brows mode and can open 5250 emulator as well here) and ACS also i can open 5250 emulator but here using VS Code getting this error.

    to run this command 'STRTCPSVR *SSHD' on ibm i command line do i need admin autority any impact on executing this command on production system or any impact on any jobs becuase of this command?

    Thanks



    ------------------------------
    jerry ven
    ------------------------------

    Original Message


  • 7.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 02:54 AM

    No safe answer can be given, without precise knowledge of your context :/

    Better ask your administrator if possible.



    ------------------------------
    Sylvain Manceau
    ------------------------------

    Original Message


  • 8.  RE: VS Code IBM i Connection error -'Not connected to ipaddress while waiting for handshake'

    Posted Mon February 19, 2024 01:42 PM

    Hi!

    Connecting through RDi and ACS will not help you troubleshoot since both don't use SSH to connect to IBM i.

    Running 'STRTCPSVR *SSHD' will try to start the SSH server on your LPAR. If you don't have enough authority, it will just refuse to start it. Otherwise, it will either start the SSH server or say it's already running.

    You should get in touch with your sysadmin though and ask them what's the SSH status on your LPAR before going any further.



    ------------------------------
    Sébastien Julliand
    R&D Advisor
    ------------------------------

    Original Message