Posted by nycram on 01/19/07 14:10

Chris wrote:
> On 18 Jan 2007 09:08:56 -0800 nycram <gvellenzer@gmail.com> wrote:
>
> > *From:* "nycram" <gvellenzer@gmail.com>
> > *Date:* 18 Jan 2007 09:08:56 -0800
> >
> > Chris wrote:
> > > On Wed, 17 Jan 2007 21:25:40 GMT AlmostBob
> > > <anonymous1@discussions.microsoft.com> wrote:
> > >
> > > > 'You' decide what numbers you use, and your pc tells the network
> > > > that
> > > > those ports are available
> > > > 'They' decide what numbers they use, and their pc likewise
> > > >
> > > > then your pc connects its outgoing port to 'their' incoming port,
> > > > and
> > > > 'your' incoming port to their outgoing port
> > >
> > > Ok.
> > > So, assume you have selected (say) port 12345, but they are using the
> > > default 6699. If your ISP blocks port 6699 will this still block a
> > > connection from you to them?
> >
> > No. Your ISP can't block their ports---else the whole internet would
> > come crashing down because pretty soon nobody could connect to anybody
> > else. But they can block your ports. If they block your 6699, and you
> > go to 12345 (a bad choice BTW) you can receive other people's messages
> > on YOUR chosen port (12345) and they can receive your messages on their
> > chosen port (no change from before).
>
> Ok, I understand now. Thanks for the explanations.
> (oh, and I would not actually use port 12345 :-) )

As I said, I worried about the same thing until I figured out how
things work.

In another part of this thread, somebody suggested using the SSL ports.
Port 119 is dedicated to usenet ("the newsgroups") so it's alternative
good low port to use, unless you are actually using usenet.

[Back to original message]