Firewall rules to allow Windows 2000 updates

Where can one find firewall rules to allow Windows 2000 updates?
Specifically, which applictions will be reaching out, input or output,
the type of access/data (TCP, UDP, etc.), which executable will be
doing this, the swath of IP addresses which it could contact, and the
ports? I've got my automatic updates to only notify me, not download
and install. I do that manually.

Thanks!

PA
Thu Apr 10 18:20:22 CDT 2008

<QP>
Transmission protocols and ports: The transmission protocols and ports used
are HTTP 80 and HTTPS 443.
</QP>
Source and more:
http://www.microsoft.com/technet/prodtechnol/windows2000pro/maintain/w2kmngd/17_2kupd.mspx
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

AndyHancock wrote:
> Where can one find firewall rules to allow Windows 2000 updates?
> Specifically, which applictions will be reaching out, input or output,
> the type of access/data (TCP, UDP, etc.), which executable will be
> doing this, the swath of IP addresses which it could contact, and the
> ports? I've got my automatic updates to only notify me, not download
> and install. I do that manually.
>
> Thanks!

AndyHancock
Sat Apr 12 02:44:57 CDT 2008

Hmm. The choice for the firewall is TDP, UDP, ICMP, or other. Would
HTTP[S] be implemented on top of one of first two?

I accessed the the website you referenced, and the relevant solution
seems to be Microsoft Software Update Services (SUS). All links link
to a webpage for Windows 2000 Server, which I don't run (this is for a
home computer).

I was wondering what Microsoft had in mind for home users using a
firewall. Such users need to create rules based on the specific
outreaching application, protocol, IP addresses to be contacted,
direction (in/out), and ports (which you've provided).

On Apr 10, 7:20 pm, "PA Bear [MS MVP]" <PABear...@gmail.com> wrote:
> <QP>
> Transmission protocols and ports: The transmission protocols and
> ports used are HTTP 80 and HTTPS 443.
> </QP>
> Source and
> more:http://www.microsoft.com/technet/prodtechnol/windows2000pro/maintain/...
>
>AndyHancock wrote:
>> Where can one find firewall rules to allow Windows 2000 updates?
>> Specifically, which applictions will be reaching out, input or
>> output, the type of access/data (TCP, UDP, etc.), which executable
>> will be doing this, the swath of IP addresses which it could
>> contact, and the ports? I've got my automatic updates to only
>> notify me, not download and install. I do that manually.

PA
Sat Apr 12 14:53:51 CDT 2008

HTTP(S)

AndyHancock wrote:
> Hmm. The choice for the firewall is TDP, UDP, ICMP, or other. Would
> HTTP[S] be implemented on top of one of first two?
>
> I accessed the the website you referenced, and the relevant solution
> seems to be Microsoft Software Update Services (SUS). All links link
> to a webpage for Windows 2000 Server, which I don't run (this is for a
> home computer).
>
> I was wondering what Microsoft had in mind for home users using a
> firewall. Such users need to create rules based on the specific
> outreaching application, protocol, IP addresses to be contacted,
> direction (in/out), and ports (which you've provided).
>
> On Apr 10, 7:20 pm, "PA Bear [MS MVP]" <PABear...@gmail.com> wrote:
>> <QP>
>> Transmission protocols and ports: The transmission protocols and
>> ports used are HTTP 80 and HTTPS 443.
>> </QP>
>> Source and
>> more:http://www.microsoft.com/technet/prodtechnol/windows2000pro/maintain/...
>>
>> AndyHancock wrote:
>>> Where can one find firewall rules to allow Windows 2000 updates?
>>> Specifically, which applictions will be reaching out, input or
>>> output, the type of access/data (TCP, UDP, etc.), which executable
>>> will be doing this, the swath of IP addresses which it could
>>> contact, and the ports? I've got my automatic updates to only
>>> notify me, not download and install. I do that manually.