Re: Connecting to Windows Server 2003



On 31 Aug, in message <4da327ae3cmlongley@xxxxxxxxxxxxx>
Martin Longley <mlongley@xxxxxxxxxxxxx> wrote:

[snip]

> Local Policies -> Security Options
>
> Find Microsoft network Client: Digitally sign communications (always) and set
> it to disabled
> If that fails then
> Microsoft Network server: Digitally sign communications (always) and disable
> that.
>
> Got both set here and it works.
>
> Shouldn't be a security issue if your network is behind a firewall.

. . . and you trust everyone else who's behind that firewall with you.

Mike
--
Mike Sandells
Work: mikejs@xxxxxxxxx http://www.liv.ac.uk/csd
Home: mike@xxxxxxxxxx http://www.mikejs.com/
.



Relevant Pages

  • RE: SMBmount conspiracy
    ... Local Policies - Security Options - Microsoft network client - digitally ... sign communications - DISABLED ... Local Policies - Security Options - Microsoft network server - digitally ...
    (RedHat)
  • RE: SMBmount conspiracy
    ... My local security policy settings are like this: ... Microsoft network client - digitally sign communications - ... Microsoft network server - digitally sign communications - ...
    (RedHat)
  • Re: SMB packet and secure channel signing
    ... Signing is that once all that security and authentication has been applied to establish the communication, SMB Signing puts a tag on each and every network packet to identify packet by packet that each packet is genuine. ... Microsoft network client: Digitally sign communications Disabled ... Microsoft network server: ...
    (microsoft.public.windows.server.sbs)
  • Re: disable digital signing
    ... "Microsoft Network Client: Digitally sign communications " ... "Microsoft Network Server: Digitally sign communications ". ...
    (microsoft.public.windows.group_policy)
  • Cannot create trust between Server 2003 AD and WinNT4 domain.
    ... Microsoft network client: Digitally sign communications Enabled ... Microsoft network server: Digitally sign communications Enabled ...
    (microsoft.public.windows.server.active_directory)