Re: USERENV error - Group Policy

From: AJ <ajsarkaria@xxxxxxxxx>
Date: Wed, 13 Jun 2007 00:02:04 -0000

Check SMB signing and make sure it matches with your DCs. The Server
Message Block (SMB) signing settings define whether the computers on
the network digitally sign communications.

Typical setting:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver
\parameters
enablesecuritysignature ==> 0x0
requiresecuritysignature ==> 0x0

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation
\parameters
enablesecuritysignature ==> 0x1
requiresecuritysignature ==> 0x0

This setting is actually controlled by a GP and the same can be found
at

Computer Configuration/Windows Settings/Security Settings/Local
Policies/Security Options

Microsoft network server: Digitally sign communications (always)
Microsoft network server: Digitally sign communications (if client
agrees)
Microsoft network client: Digitally sign communications (always)
Microsoft network client: Digitally sign communications (if server
agrees)

Should take effect only after you restart the Server and the
Workstation service.

Hope this information helps you~~

~Cheers,

Ajay Sarkaria

.

References:
- RE: USERENV error - Group Policy
  - From: Sean Mitchell

Prev by Date: Active Directory DC Hangs when lmcompatibility is set 4
Next by Date: Re: Directory Service logged NTDS replication (1083 and 1955) events
Previous by thread: RE: USERENV error - Group Policy
Next by thread: Re: MS - Active Directory Powerpoint
Index(es):
- Date
- Thread

Relevant Pages

Re: LDAP UDP Port Problem
... see that there is communication on 389/udp going to and from the server. ... Kerberos to tcp communications a few days ago without success. ... > You might want to do a network trace on both sides and watch the packets. ... >> Using ephemeral source port ...
(microsoft.public.win2000.networking)
Re: LDAP UDP Port Problem
... see that there is communication on 389/udp going to and from the server. ... Kerberos to tcp communications a few days ago without success. ... > You might want to do a network trace on both sides and watch the packets. ... >> Using ephemeral source port ...
(microsoft.public.windows.server.networking)
Re: LDAP UDP Port Problem
... see that there is communication on 389/udp going to and from the server. ... Kerberos to tcp communications a few days ago without success. ... > You might want to do a network trace on both sides and watch the packets. ... >> Using ephemeral source port ...
(microsoft.public.windows.server.active_directory)
Re: LDAP UDP Port Problem
... see that there is communication on 389/udp going to and from the server. ... Kerberos to tcp communications a few days ago without success. ... > You might want to do a network trace on both sides and watch the packets. ... >> Using ephemeral source port ...
(microsoft.public.windows.server.setup)
RE: The SMBMOUNT plot thickens
... (if server agrees)" are probably due to different windows ... Event viewer shows a successful logon by my mount.cifs client ... Microsoft network client - digitally sign communications - ...
(RedHat)