Prev: Mis-using DNS for solving WWW browser problems.
Next: Outside dns not changin
From: Poutnik on 29 Mar 2010 14:55
In article <0NqdnSV4Vd9NQS3WnZ2dnUVZ_tydnZ2d(a)earthlink.com>, rmoore85
@ix.netcom.com says...

> >
> >> At the same time, Comodo tells me only about ports 2523& 2521:
> >> TCP Listening:2523
> >> TCP Listening:2521
> >>
> >> Does this help to figure out what is going on with those two ports opened
> >> up by Firefox?
> >
> > I see nothing like this on any copy or version of Firefox that I've used on
> > any of several PCs. As has been suggested, ask on a Mozilla forum.
> >
>
> Granted that I don't know much about all this, but isn't it possible
> FF needs a couple of open ports for information about updates to
> extensions, browser, etc? Just a thought...
>
It is pretty normal behavior for Firefox,
same as for Thunderbird and for plenty of other programs.

My FF have always 2-32 local FF2FF connections,
same as TB has 2 local TB2TB connections.

If process is listening on localhost ( 127.0.0.1 ) interface,
nothing but local processes can connect to it.

Imagine it as you extra network card,
that is available only to programs running on your PC.

If you monitor connections by sysinternals TCPview utility,
always notice yourself
what interface IP address a process is listening on.

--
Poutnik
The best depends on how the best is defined.
From: Poutnik on 29 Mar 2010 14:57
In article <MPG.261b1611e61b84749898e1(a)127.0.0.1>, me(a)privacy.net
says...
>
> My FF have always 2-32 local FF2FF connections,
>
A typo, should be 2-3, not 2-32

--
Poutnik
The best depends on how the best is defined.
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Mis-using DNS for solving WWW browser problems.
Next: Outside dns not changin