i want to stop receiving ur email.or i should say i want to be out of this group.
On 12/3/10, Mike Fry <[email protected]> wrote: > On 2010/12/03 11:43, Jamie Fraser wrote: >> The point in NAT is that if the remote router is NAT-ing, then you don't >> need >> to do anything. > >> On Mon, Nov 15, 2010 at 9:23 AM, TyBreaker <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, I'm planning on a network application where multiple clients connect >> but >> some may share a home network thus their external IP adress would be the >> same >> - assuming their router is NATing. What is best practice for handling >> such >> scenarios and so distinguish between each client? >> >> I envisage someone opts to be the server and they may also have clients on >> their home network. The remote clients may also be coming from a single >> home >> network, or from different networks. >> >> I'm assuming that besides the IP address each client would have to >> identify >> itself in some unique way. Is there managed code for this or do you need >> to >> manage them in some manual way yourself? > > That's right! And unless there's something in the data coming from the > remote > router, you are never going to be able to tell one client using the same > router, > from another. > > -- > Regards, > Mike Fry > Johannesburg >
