IE wants to use outgoing localhost ports

[Guest]

Win XP Home SP2, IE6, with latest updates for both.
When I run IE, my firewall says it keeps trying to
access outgoing localhost ports.
The port numbers start around 1900 and increase
into the 2000's and 3000's as I deny access.
When access is denied, IE seems to run very slowly
(takes a long time to connect to a web page).
When I use a firewall rule to allow access, IE runs normally.
What is IE doing with these ports ?
Why does it need them to run properly ?
What range of port numbers should I enable in the firewall ?

 

[N. Miller]

Win XP Home SP2, IE6, with latest updates for both.
When I run IE, my firewall says it keeps trying to
access outgoing localhost ports.
The port numbers start around 1900 and increase
into the 2000's and 3000's as I deny access.
When access is denied, IE seems to run very slowly
(takes a long time to connect to a web page).
When I use a firewall rule to allow access, IE runs normally.
What is IE doing with these ports ?

I am not really sure; something with password security, I think. It doesn't
matter, localhost connections are loopback connections; they don't leave
the computer.

Why does it need them to run properly ?

Security issues, I think. It doesn't matter, localhost connections are
loopback connections; they don't leave the computer.

What range of port numbers should I enable in the firewall ?

1024 to 5000 works for me in Kerio Personal Firewall 2.1.5. These are also
known as the ephemeral ports; the TCP/IP stack uses them for outbound
connections, and uses sequential ports up through 5000. The ports that are
closed after use are not available for re-use until some period of time
after closure. Normally, they start being recycled before you pass port
5000; but, if the recycle timeout period is not reached before port 5000 is
used, ports higher than 5000 will be used. I have only done that once, or
twice.