|
Posted by Roger Abell [MVP] on November 30, 2005, 10:45 pm
Please log in for more thread options You do need to coordinate the settings so that it is possible for
the two parties to negotiate an agreed upon, common choice.
The security/hardening and threats and countermeasures guides
have some discussion for these policies and their implications
(at least the W2k3/XP generation of papers do).
--
Roger Abell
Microsoft MVP (Windows Server : Security)
> Whenever I have tried turning these options on in a Windows 2000 domain
> running W2K native mode and all W2K member servers, literally everything
> breaks. Clients won't talk to each other and won't talk to the DC
> either.
> Various references I saw online said this is a common result without
> saying
> why or how to fix it, aside from turning off the signing and encryption.
>
> What are some possible causes for that behavior?
>
> --
> Will
>
>
>> microsoft.public.windows.server.security news group, Will <westes-
>> usc@noemail.nospam> says...
>>
>> > Do the Group Policy Security options for client and server signing and
>> > encrypting of secure channel data require that you have a public key
>> > infrastructure setup with a dedicated PKI server?
>> >
>>
>> No.
>>
>> --
>> Paul Adare
>> MVP - Windows - Virtual Machine
>> http://www.identit.ca/blogs/paul/
>
>
|