I reformulate what I understood:
1) You have a client/server application (I'll assume your use socket and TCP
connections to communicate bertween client and server since you ask in a
winsock newsgroup).
2) Your server is available from the internet, that is it has a public IP
address
3) The client workstations connect to the server thru their internet access
4) Sometimes the client can't connect to the server
5) You want to know if the client connection is up and running
6) To achieve (5), you'll have your client application connect periodically
to the server, just to verify the connection.
7) The server will "rememeber" when each client has connected the last time
and if this is too long since last connect, the server will trigger an
alaram (maybe will send you an email ?).
Did I reformulate correctly ?
What are you using for your communication ? Which component or which API ?
Have you designed both the client and the server ?
Which protocol are you using ?
Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html
