Article View: borland.public.cppbuilder.internet.socket
Article #5448Re: Through FireWall
From: Hans Galema
Date: Sun, 12 Sep 2004 10:54
Date: Sun, 12 Sep 2004 10:54
25 lines
2111 bytes
2111 bytes
minoy wrote: > I actually want to know this : > A client(C) in LAN behind the Firewall/route(F) want to > connect to a Server(S) in WAN.Suppose that we use the UDP. > Now,Client connects to Server directly use S's IP,and > Send a Message To Server, > The Server receive the Client's Message,then Send the response Message to Client,Now, > I confused,The Server must connect to Client No. Why are you thingking so ? The client just connected to the server using the port where the server is listening on. The communication then goes over a different port indeed. That port is proposed by the client. The IP is the IP as seen by the server. > use Firewall's IP,But use Which Port? You have no influence on the proposed port(number). As far as I know: when a client can connect with the server than the recommunication will be ok too. Do you have other experiences? > If they connect next time,does the Port change? The communication port can be different each time yes. Hans.
Technical Details
Message-ID:
<41442a47$1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!fr.ip.ndsoftware.net!npeer.de.kpn-eurorings.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<41414382$1@newsgroups.borland.com> <4141485f$1@newsgroups.borland.com> <41418641$1@newsgroups.borland.com> <4142b1b4$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11508e,82d1fc96f1dc2486 X-Google-Attributes: gid11508e,public X-Google-Language: ENGLISH,ASCII-7-bit Date: Sun, 12 Sep 2004 12:54:48 +0200 From: Hans Galema <dontusethis@dontusethis.nl> User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: borland.public.cppbuilder.internet.socket Subject: Re: Through FireWall References: <41414382$1@newsgroups.borland.com> <4141485f$1@newsgroups.borland.com> <41418641$1@newsgroups.borland.com> <4142b1b4$1@newsgroups.borland.com> In-Reply-To: <4142b1b4$1@newsgroups.borland.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit NNTP-Posting-Host: 129.125.201.248 Message-ID: <41442a47$1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1094986311 129.125.201.248 (12 Sep 2004 03:51:51 -0700) Lines: 25 Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!proxad.net!fr.ip.ndsoftware.net!npeer.de.kpn-eurorings.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail