on Mon, Mar 18, 2002 at 07:54:07PM +0000, Paul wrote:
I've been trying to get a distributed application working over a network. Most of the inter-process communications are handled by a low level server using the TCP/IP stack. For remote processes, communications use port 5005. Not being particularly clued up on low level networking, how do I enable this port ?
You shouldn't need to. The "server" software calls bind(2) (try man 2 bind, for the gritty details) and then calls listen(2) and then the process goes to sleep, or does something else whilst it waits. When the TCP/IP stack receives a packet addressed to this port, the operating system sees that the software is listening on the port and address, specified by bind(2), and so wakes that process up, indicating there is a new connection for it to take care of. (I'm assuming it's using TCP, if it uses UDP, the process is similar but different.)
If you are running some kind of firewall, you may want to check the filtering.
If you get error messages like "Address already in use", netstat or fuser can probably locate the offending process.
Just throw an extra problem in, is there likely to be any problems communicating with a Windows box on this port ?
AFAIK, no. The port isn't IANA registered and so is unlikely to have any other service listening on it. A client might be using it, if so, just kill whatever is using that port (netstat is your friend.)