Hello Markus,
I haven't yet a failure message or so
if a socket can't connect then onsessionconnect is fired with an error
code. then onsessionclose is fired, eventually also with an error code.
I assume you keep these errorcodes in an errorlog file or so. you have
to give this so we can see
Hello,
thanks Wilfried for your answer. Some things I can already say out of my
head while the error codes I've to check.
The PC is a W2K PC with no firewall and no anti virus set up since it's
not connected to our company network.
It has 2 network interfaces but only one is physically
Hello,
I can see that the other app is listining via netstat.
It says: listening
Greetings
Markus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Hello,
I'm wrining a 2-part application where both parts use a TWSocket to
communicate with each other.
The one part is started and creates a listining socket on localhost's
port 8999 where the other will connect to.
Now on some PCs (Windows 2000 at least in one case) this fails. The user
has
Markus Humm wrote:
Hello,
I'm wrining a 2-part application where both parts use a TWSocket to
communicate with each other.
The one part is started and creates a listining socket on localhost's
port 8999 where the other will connect to.
Now on some PCs (Windows 2000 at least in one
