Re: Re: Event IDs 1030 & 1058 (again)

From: Mark Renoden [MSFT] (markreno_at_online.microsoft.com)
Date: 05/31/04


Date: Tue, 1 Jun 2004 07:43:46 +1000

One last thing ... after installing the hotfix, you need to add the
following registry value:

    HKLM\Software\Microsoft\Windows
NT\CurrentVersion\Winlogon\WaitForNetwork REG_DWORD value of 1

Kind regards

-- 
Mark Renoden [MSFT]
Windows Platform Support Team
Email: markreno@online.microsoft.com
Please note you'll need to strip ".online" from my email address to email 
me; I'll post a response back to the group.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Renoden [MSFT]" <markreno@online.microsoft.com> wrote in message 
news:%23kJ7hc1REHA.2412@TK2MSFTNGP09.phx.gbl...
> Hi again
>
> I realised after I posted my response yesterday that this advice makes the 
> assumption that the 1030 and 1058's contain certain information in the 
> event description.  Specifically, the 1058's should raise "(Access is 
> denied)" as the cause for failure.  If you're seeing something else, 
> please post the actual event descriptions that you're seeing.
>
> Kind regards
>
> -- 
> Mark Renoden [MSFT]
> Windows Platform Support Team
> Email: markreno@online.microsoft.com
>
> Please note you'll need to strip ".online" from my email address to email 
> me; I'll post a response back to the group.
>
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>
>
> "Mark Renoden [MSFT}" <markreno@online.microsoft.com> wrote in message 
> news:unf3X4sREHA.2496@TK2MSFTNGP11.phx.gbl...
>> Hi Anthony
>>
>> To my knowledge, there are a number of factors that may be the cause of 
>> this issue.  One of these is a bug but it's best to check the following 
>> before obtaining the related fix from Microsoft:
>>
>> 1. That both DC's point to the same server as the preferred DNS server.
>>
>> 2. Ensure that "Digitally sign server communication (always)" and 
>> "Digitally sign server communication (when possible)" match on all DC's 
>> in the "Local Security Policy" -> Windows Settings -> Security 
>> Settings -> Local Policies -> Security Options.  Default settings are:
>>
>>   Microsoft Network Client: Digitally Sign Communication (always)
>>   Microsoft Network Client: Digitally Sign Communication (if server 
>> agrees)
>>   Microsoft Network Server: Digitally Sign Communication (always)
>>   Microsoft Network Server: Digitally Sign Communication (if client 
>> agrees)
>>
>> 3. In the "Domain Controller Security Policy", ensure that Windows 
>> Settings -> Security Settings -> Local Policies -> User Rights Assignment 
>> includes the "Everyone" group.
>>
>> 4. If any DC's use a Gigabit NIC, try updating the driver or an alternate 
>> device?
>>
>> 5. Ensure that the Netlogon service on all DC's is set to "Automatic" 
>> startup and that the service is successfully starting.
>>
>> 6. Ensure that the Distributed File System service on all DC's is set to 
>> "Automatic" startup and that the service is successfully starting.
>>
>> 7. Ensure that Administrators and System have Full Control access to the 
>> GPT.INI file and the full directory path specified in the events?
>>
>> 8. Provided you don't currently have anything important set in the 
>> Default Domain or Default Domain Controllers policies, try running the 
>> following on the PDC emulator.  NOTE:  This will completely replace the 
>> existing policies with the defaults.
>>
>>    dcgpofix /target:both
>>
>> 9. Ensure that Remote Desktop Sharing is not enabled (Properties of My 
>> Computer -> Remote Tab -> Uncheck "Allow users to connect remotely to 
>> this computer."  Click OK.
>>
>> 10. Ensure that Offline Files are enabled (Open Windows Explorer -> Tools 
>> Menu -> Folder Options -> Offline Files Tab -> check "Enable Offline 
>> Files" and "Synchronize all offline files when logging on.").  Click OK.
>>
>> Failing these steps, contact Microsoft and request the hotfix associated 
>> with knowledge the following knowledge base article:
>>
>>    830676 Group Policy processing fails with Events 1058 and 1030 in 
>> Windows
>>    http://support.microsoft.com/?id=830676
>>
>> While this article does not specifically state there is a hotfix 
>> available for the issue, I've provided it in a couple of cases and this 
>> has resolved the problem.
>>
>> Kind regards
>> -- 
>> Mark Renoden [MSFT]
>> Windows Platform Support Team
>> Email: markreno@online.microsoft.com
>>
>> Please note you'll need to strip ".online" from my email address to email 
>> me; I'll post a response back to the group.
>>
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>> <boxster@antamy.com> wrote in message 
>> news:pVOdnTIESfMMASXd3cwC-g@speakeasy.net...
>>> Yes - I have run dfsutil / purgemupcache many times, with no effect,
>>>
>>> Thanks
>>>
>>> Anthony
>>
>>
>
> 


Relevant Pages

  • Re: Re: Event IDs 1030 & 1058 (again)
    ... I realised after I posted my response yesterday that this advice makes the ... That both DC's point to the same server as the preferred DNS server. ... > Microsoft Network Client: Digitally Sign Communication ... > Microsoft Network Client: ...
    (microsoft.public.windows.group_policy)
  • Re: Re: Event IDs 1030 & 1058 (again)
    ... That both DC's point to the same server as the preferred DNS server. ... Microsoft Network Client: Digitally Sign Communication ... Ensure that Offline Files are enabled (Open Windows Explorer -> Tools ...
    (microsoft.public.windows.group_policy)
  • Re: Re: Event IDs 1030 & 1058 (again)
    ... The hotfix is now correctly packaged and associated with the following ... >> appear by default on Windows Server 2003. ... >> Windows Platform Support Team ... >>>> Microsoft Network Client: ...
    (microsoft.public.windows.group_policy)
  • Re: * 1058 and 1030
    ... That both DC's point to the same server as the ... Ensure that "Digitally sign server communication ... > Microsoft Network Client: Digitally Sign Communication ... Ensure that Offline Files are enabled (Open Windows ...
    (microsoft.public.windows.group_policy)
  • Re: Re: Event IDs 1030 & 1058 (again)
    ... >>Windows Platform Support Team ... appear by default on Windows Server 2003. ... As I mentioned in a follow up post earlier, the hotfix ... > Communication (if server ...
    (microsoft.public.windows.group_policy)