HTTP(S)
AndyHancock wrote:<span style="color:blue">
> Hmm. The choice for the firewall is TDP, UDP, ICMP, or other. Would
> HTTP 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:<span style="color:green">
>> <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/prodtechn...00pro/maintain/...
>>
>> AndyHancock wrote:<span style="color:darkred">
>>> 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. </span></span></span>