🚀 go-pugleaf

"Chris" <computer@programmer.com> wrote in message
news:45a5011b$1@newsgroups.borland.com...

> I have a Server Socket Program and I have a Client Socket
> program. On my LAN these two programs work like a charm, but
> when I try to access my Server Socket from a computer outside
> of the Network(over the internet) I get an error:

As you should be.  Your client needs to connect to the router's public
IP/Port, not the server's private IP/port.  And the router needs to be
configured for port forwarding as well.  Which it sounds like you are
doing, so something else has to be blocking the connection.

> On the router, which is the only firewall we are using, we use port
> forwarding to connect to the ServerSocket computer. Therefore the
> address of 123.45.67.89:6111 should connect me to 192.168.1.17
> from outside of the LAN. This does, in fact, work for other programs
> like Ultra VNC, but not for my SocketServer program.

Then you are doing something else wrong.  Make sure that your client
really is trying to connect to 123.45.67.89:6111 and not
192.168.1.17:6111, and that the SocketSever program really is
listening on 192.168.1.17 on the port that is being forwarded to.
What kind of server socket component are you using (if any)?  How are
you binding it when starting to listen for connections?


Gambit