🚀 go-pugleaf

Hey, if OnConnect is not called, then the darn thing ain't connecting! It's as
simple as that!

It sounds like you are not able to connect client to server. If the server is
just listening for connections, ie. :-
ServerSocket1->Open();
then a Client ought to be able to connect to it and fire off the client's
OnConnect event (as well as the server's!). There can only be one thing
wrong - the port and/or IP address you are trying to connect through do not
allow the connection. You can test this with my mathspenknife.exe application
at http://www.jacobsm.com#sft (download the exe and run it - fill in IP
address and Port number, and then press Connect. A diagnostic error message is
reported if there is a problem (usually "the remote machine is not
listening"). This utility employs the blocking socket mode of operation of the
same components you are using, and it is a useful way of telling if you can
connect on certain port numbers. You may be able to ping your client or server
from each other, but that is not the same as sending packets on port numbers
that may be blocked by a firewall somewhere. HTH,
-- 
Mark Jacobs
DK Computing
http://www.dkcomputing.co.uk

"duncan" <nospam@nospam.com> wrote in message
news:4198b1a6$1@newsgroups.borland.com...
| the client OnLookup and OnConnecting methods get called but the
| client OnConnect method never gets called. Do I need something
| else on the server side to do this?