"FromTheRafters" <!(E-Mail Removed)> wrote in
news:(E-Mail Removed):
>
> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
> news
VYZa.1791$(E-Mail Removed)...
>> Wrong again !
>>
>> WinME is the *best*, and the last, of the Win9x family and is NOT
>> affected by the vulnerability.
>>
>> DCOM has been around since Win95. The vulnerability *only* affects
>> NT based OS's (WinNT4, Win2K, WinXP, WinXP/64, Win2003 and
>> Win2003/64).
>
> So, you can install RPC DCOM on the Win9x machines, but it is
> a different animal than that used with the NT kernels?
>
>
>
http://www.microsoft.com/com/tech/dcom.asp
It allows a client machine to make calls to dll's setting on a
centralized server machine (it doesn't have to be a O/S server) -- a
workstation too. The dll's which are a library of program routines can be
business objects, database objects, etc. The client machines make calls
to the dll's through an exe that is on the client machine to do
processing. The point of failure is at one point instead of the dll's
being deployed to all machines (a fat client machine) as apposed to a
(thin client machine exe only). DOCOM allows the client machines to
connect to the server machine via TCP/IP to the server machine and share
the dll's.
Win 95 to NT machines can be setup to do this. Win 2k workstation can be
set with DCOM to go find a NT machine that is the server of the dll(s)
too. M$'s move towards centralized processing.
Now the move is towards Win 2K or XP Pro workstations COM+ and a COM+ O/S
Win2k server, Win 2k ADV or 2K3 server. It's the same thing just a
different tune.
Duane
--
The protection of the machine is a process and not a given!