Search results

Thanks you all people especially Medu as we took his suggestion and added a -H parameter before the -S socket number in our parameters file. We used "0.0.0.0" as the hostname. Dougcu

We are just trying to listen for requests on a particular socket 5555. we were not using a -H hostname but now we have tired that -H parameter and it will not listen on the localhost for that port and we would like it to listen on the port for both the localhost and the host. Thanks in advance...

It is with multi-user, remote client we were just using the -S parameter. We were given a work-around (use the -H parameter as well) but then we can't (on this system) connect to the locahost. Any ideas? Dougcu

That is with a socket server. We did not yet but could try and use the '-H hostxyz' parameter. Thanks for your interest! -D

Thank you Heavy for your reply - We do not currently use the -H or any startup parameters. We went from 8.2C as 8.2C was old and limited. The error that bothers me when someone tries to connect is: "connect to address 192.168.1.2: Connection refused" We can connect to 127.0.0.1 only. the tcp...

Help! We used to be able to open a server-socket ie: (tcp)port 55555 and once started anyone could connect to our server using that port number. Now with OpenEdge 10.1C It refuses the connection except when trying the 127.0.0.1 "loop back" from the Linux server itself. Any idea what if anything...