Clovertech

localhost connection refused

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › localhost connection refused

  • Creator
    Topic
  • June 18, 2014 at 4:33 pm #54269
    James Cobane
    Participant

      I’m wondering if anybody has experienced this scenario:

      Configured a pair of localhost connections in NetConfig – i.e. a client and server with tcp_mlp, but unable to connect (Can’t connect to 127.0.0.1:31035 – Connection refused).

      Yet, running hcitcptest with the same configuration (one session acting as the server, another session acting as the client), we are able to connect no problem.

      Then when attempting to connect to the listening thread (in NetConfig) via hcitcptest (as the client), the connection does not connect.

    • Creator
      Topic
    Viewing 4 reply threads
    • Author
      Replies
      • June 19, 2014 at 3:29 pm #80797
        David Barr
        Participant

          Does netstat show the port in a LISTENING state?

        • June 19, 2014 at 3:46 pm #80798
          James Cobane
          Participant

            Yep, which makes it all the more puzzling… 🙂

          • June 19, 2014 at 4:28 pm #80799
            David Barr
            Participant

              Are you listening on all IP addresses? Did you fill in “local binding address” on the server thread? Do you have a firewall turned on? Are you using localhost or 127.0.0.1, and do you have an entry in /etc/hosts for localhost?

              I’m not sure what’s going on either. I’m just trying to tell you what I would look at.

            • June 19, 2014 at 6:49 pm #80800
              Robert Milfajt
              Participant

                I suspect a port conflict with some other interface or OS process.  The netstat command should help you find this out.  The following should work in any OS (UNIX/Windows) I think, but in UNIX pipe the results to grep to find your particular port number.

                Code:

                netstat -an

                Hope this helps,

                Robert Milfajt
                Northwestern Medicine
                Chicago, IL

              • June 19, 2014 at 8:05 pm #80801
                James Cobane
                Participant

                  Thanks for the feedback.  I had done all the routine trouble-shooting previously (netstat looking for potential conflicts, etc.).  It turns out the local binding address was configured on the server port, which was causing the issue – good catch, David!

                  Thanks,

                  Jim Cobane

                  Henry Ford Health

              • Author
                Replies
              Viewing 4 reply threads
              • The forum ‘Cloverleaf’ is closed to new topics and replies.