If I setup a winsock control to be listening on a particular port, it will fire if a connection from the outside is made to it. What I want to know if it works the other way around, will it fire if a program from the inside (i.e. a program this is running on the local machine) tries to open that port to make a connection to the outside world.
The other question that I have is how do I obtain as much information about the machine trying to connect to my machine? I can get the ip address and the dns name (if it has one), but I would like to be able to gather more information. I would like to know what there ISP is and information similar to that.
Also, is it better to use winsock API or the winsock control? And, is it infeasible to listen to all 65535 ports at the same time?
Regards,
Troy Williams B.Eng.
fenris@hotmail.com
The other question that I have is how do I obtain as much information about the machine trying to connect to my machine? I can get the ip address and the dns name (if it has one), but I would like to be able to gather more information. I would like to know what there ISP is and information similar to that.
Also, is it better to use winsock API or the winsock control? And, is it infeasible to listen to all 65535 ports at the same time?
Regards,
Troy Williams B.Eng.
fenris@hotmail.com