Hi Richard Perhaps "enabling the port" was the wrong phrase. I haver the server app running on one machine and it accepts local connections without any problems. When the remote client attempts to connect, the connection is refused on port 5005. There is no firewall, and system security is as lax as I know how to make it. It could be a bug in the server/client software, I'm just working through the various possibilties at the moment. Regards, Paul. On Monday 18 March 2002 23:04, Richard Kettlewell wrote:
There's no such concept as "enabling" a TCP port.
on Mon, Mar 18, 2002 at 11:32:05PM +0000, Paul wrote:
Perhaps "enabling the port" was the wrong phrase. I haver the server app running on one machine and it accepts local connections without any problems. When the remote client attempts to connect, the connection is refused on port 5005. There is no firewall, and system security is as lax as I know how to make it.
Is it possible the server app is only binding to local addresses? eg, it's listening on 127.0.0.1:5005 but should be listening on 0.0.0.0:5005? (0.0.0.0 being "anything") netstat -an would show you this. Adding -p might show you what process owns each entry, depending on versions, etc.
participants (2)
-
Paul -
xs＠kittenz.org