Posted by Jon Sacks on November 25, 2003 at 09:29:39:
In Reply to: Re: IP Addresses connected to an Anywhere Host posted by Brian Levantine on November 25, 2003 at 08:52:40:
If I run the command NET STAT -n at a command prompt I get back a list of the users connected to my machine that includes:
Protocol, Local Address, Foreign Address, State.
Example:
Proto Local Address Foreign Address State
TCP 172.16.0.15:1073 172.16.0.51:11750 ESTABLISHED
TCP 172.16.0.15:1074 172.16.0.51:11752 ESTABLISHED
TCP 172.16.0.15:1075 172.16.0.51:139 ESTABLISHED
TCP 172.16.0.15:1076 172.16.0.17:139 ESTABLISHED
TCP 172.16.0.15:1077 172.16.0.13:139 ESTABLISHED
TCP 172.16.0.15:11751 172.16.0.1:19220 ESTABLISHED
TCP 172.16.0.15:11751 172.16.5.61:1076 ESTABLISHED
Is it unreasonable to ask Comet to maintain the IP address of the remote machine by partition? Could IP address be part of the IDMaint data? Why session ID vs. IP address?
Comet is aksing me to set up two sets of tracking. Each machine has a unique IP address and I can refer back to my tables to find out who the remote user is, now I need to create a second table based on session ID that I must maintain. It is also unclear to me in the documentation what a work station with two anywhere sessions running looks like from a "session ID" standpoint. When I look at the IP address I can examine who the user is and if they have requests open on more than one port (i.e. multiple sessions). I'm not sure I can tell this from a "session ID" standpoint.
Thanks,
JSACKS<<