Support Questions

Find answers, ask questions, and share your expertise

Who agreed with this solution

avatar
Master Collaborator

Although that thread sounds similar, I don't think it's the same thing. Failing to bind is not a failure to connect to a remote host. It means the local host didn't allow the process to listen on a port. The two most likely explanations are:

 

- an old process is still listening on that port, or at least, another still-running process is

- you appear to be binding to a non-routable address (192.168.x.x) This might be OK but worth double-checking

View solution in original post

Who agreed with this solution