From: Ellen K. 

I mean the latter but I'm a belt-and-suspenders person.   (As could be
noted from my reply to your recent question about separate user names and
passwords everywhere.)   The tech that's doing the Windows Update on
a box might decide to check his webmail, open one with a link, click on it...

On Sun, 13 Feb 2005 20:00:30 -0800, "Rich"  wrote in message
:

>   It's still unclear what you mean by "internet access".  Do you mean,
accessible from the Internet as is suggested by your mention of a firewall
blocking ports or the more common usage where the local machine can access
the internet but not the reverse.  I hope you mean the latter in which case
I don't see the problem.
>
>Rich
>
>  "Ellen K."  wrote in message
news:ob70119tt0lp5b1sr95gvv2gv7gnfhtvhh{at}4ax.com...
>  Unfortunately our operation isn't that sophisticated.   All the Windows
>  servers have internet access and go to WindowsUpdate to get patched.
>  So if I could wave a magic wand, I would have us receive a
>  Windows-Update-On-A-CD from Microsoft whenever new patches or service
>  packs come out.
>
>  On Sun, 13 Feb 2005 15:45:51 -0800, "Rich"  wrote in message
>  :
>
>  >   I think Internet access is being used in distinct ways here.  There is
no need for a direct connection to the Internet nor any incoming connection
at all.  Whatever firewall you use on your network should have no
relevance.
>  >
>  >   What is needed to use Windows Update, but not some of the other
supported update mechanisms, is the ability to access the internet such as
via proxy, VPN, or whatever mechanism works for you.
>  >
>  >Rich
>  >
>  >  "Ellen K."  wrote in message
news:6vhv01dsvdep48mkooe154s5cr5d0m73cv{at}4ax.com...
>  >  I have to say it actually does bother me that my SQL Server boxes at
>  >  work have internet access in order to go to WindowsUpdate.  I would
>  >  prefer that they not have internet access, even though ports 1433 and
>  >  1434 are blocked at the firewall.

--- BBBS/NT v4.01 Flag-5