We have about 100 Windows 7 machines composed of 3 different models of computer. The newest two models are logging NETLOGON Event ID 5719 at startup. This has the knock on effect of causing group policy processing to fail at startup which in turn stops all group policy deployed MSIs being installed. If we assign a static IP to the machine the error goes away. On some machines if we disable the firewall and set the network connection to 1Gbps rather than auto the error goes away. Obviously these aren't very useful solutions. The oldest of the computers don't seem to have this problem as they take longer to boot up, which seems to allow the network connection time to become fully operational before netlogon starts. I've tried a number of 'fixes' that don't work: setting NETLOGON ExpectedDialupDelay to 200 via both group policy and the registry setting the NETLOGON service to be dependant on various other services including DNS, DHCP client, TermService, Firewall.. set Kerberos to use TCP using the MaxPacketSize registry value The computers are plugged into a mix of 100Mbps and 1Gbps managed switches. Spanning tree is not enabled. Our 600 or so Windows XP clients are unaffected. Any help would be greatly appreciated. netlogon.log 05/07 16:21:09 [INIT] Command line parsed successfully ... 05/07 16:21:09 [INIT] Netlogon.dll has been unloaded (recover from it). 05/07 16:21:09 [PERF] NlInit: New NlPcGlobalTotalInstance (00000000003B18B8): "_Total" 05/07 16:21:09 [SITE] Setting site name to 'Site-Name' 05/07 16:21:09 [CRITICAL] IPV6SocketAddressList is too small 0. 05/07 16:21:09 [SESSION] Winsock Addrs: (0) List is now empty. 05/07 16:21:09 [SESSION] V6 Winsock Addrs: (0) 05/07 16:21:09 [CRITICAL] Address list changed since last boot. (Forget DynamicSiteName.) 05/07 16:21:09 [SITE] Setting site name to '(null)' 05/07 16:21:09 [DNS] Set DnsForestName to: domain.com 05/07 16:21:09 [DOMAIN] NETBIOS_DOMAIN: Adding new domain 05/07 16:21:09 [DOMAIN] Setting our computer name to PC102208 PC102208.domain.com 05/07 16:21:09 [DOMAIN] Setting Netbios domain name to NETBIOS_DOMAIN 05/07 16:21:09 [DOMAIN] Setting DNS domain name to domain.com. 05/07 16:21:09 [DOMAIN] Setting Domain GUID to d223f5a8-385f-4fe2-bbc9-5af707aa581a 05/07 16:21:09 [CRITICAL] C:\Windows\system32\config\netlogon.ftj: Unable to open. 2 05/07 16:21:09 [INIT] Getting cached trusted domain list from binary file. 05/07 16:21:09 [LOGON] NlSetForestTrustList: New trusted domain list: 05/07 16:21:09 [LOGON] 0: NETBIOS_DOMAIN domain.com (NT 5) (Forest Tree Root) (Primary Domain) (Native) 05/07 16:21:09 [LOGON] Dom Guid: d223f5a8-385f-4fe2-bbc9-5af707aa581a 05/07 16:21:09 [LOGON] Dom Sid: S-1-5-21-270630105-1620790853-1846952604 05/07 16:21:09 [INIT] Starting RPC server. 05/07 16:21:09 [MISC] NlpInitializeTrace succeeded 0 05/07 16:21:09 [SESSION] NETBIOS_DOMAIN: NlSessionSetup: Try Session setup 05/07 16:21:09 [SESSION] NETBIOS_DOMAIN: NlDiscoverDc: Start Synchronous Discovery 05/07 16:21:09 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine. 05/07 16:21:09 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1 05/07 16:21:09 [MAILSLOT] Sent 'Sam Logon' message to NETBIOS_DOMAIN[1C] on all transports. 05/07 16:21:09 [CRITICAL] NlBrowserSendDatagram: No transports available 05/07 16:21:09 [CRITICAL] NetpDcGetNameNetbios: NETBIOS_DOMAIN: Cannot NlBrowserSendDatagram. (1C) 53 05/07 16:21:09 [MISC] NetpDcGetName: NetpDcGetNameNetbios returned 1355 05/07 16:21:09 [CRITICAL] NetpDcGetName: NETBIOS_DOMAIN: IP and Netbios are both done. 05/07 16:21:09 [CRITICAL] NETBIOS_DOMAIN: NlDiscoverDc: Cannot find DC. 05/07 16:21:09 [CRITICAL] NETBIOS_DOMAIN: NlSessionSetup: Session setup: cannot pick trusted DC 05/07 16:21:09 [MISC] Eventlog: 5719 (1) "NETBIOS_DOMAIN" 0xc000005e 7f14dcc8 6c48a92f f9c5d616 c111129e ..../.Hl........ 05/07 16:21:09 [MISC] DsGetDcName function called: Dom:NETBIOS_DOMAIN Acct:(null) Flags: DS NETBIOS RET_DNS 05/07 16:21:09 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine. 05/07 16:21:09 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1 05/07 16:21:09 [MISC] NetpDcGetName: NETBIOS_DOMAIN similar query failed recently 16 05/07 16:21:09 [MISC] DsGetDcName function returns 1355: Dom:NETBIOS_DOMAIN Acct:(null) Flags: DS NETBIOS RET_DNS 05/07 16:21:09 [SESSION] NETBIOS_DOMAIN: NlSetStatusClientSession: Set connection status to c000005e 05/07 16:21:09 [SESSION] NETBIOS_DOMAIN: NlSessionSetup: Session setup Failed 05/07 16:21:09 [INIT] Started successfully 05/07 16:21:09 [MISC] DsGetDcName function called: Dom:(null) Acct:(null) Flags: 05/07 16:21:09 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine. 05/07 16:21:09 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1 05/07 16:21:09 [MISC] NetpDcGetName: NETBIOS_DOMAIN similar query failed recently 16 05/07 16:21:09 [MISC] DsGetDcName function returns 1355: Dom:(null) Acct:(null) Flags: 05/07 16:21:09 [MISC] NlWksScavenger: Can be called again in 15 minutes (0xdbba0) 05/07 16:21:09 [MISC] DsGetDcName function called: Dom:NETBIOS_DOMAIN Acct:(null) Flags: DS NETBIOS RET_DNS 05/07 16:21:09 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine. 05/07 16:21:09 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1 05/07 16:21:09 [MISC] NetpDcGetName: NETBIOS_DOMAIN similar query failed recently 78 05/07 16:21:09 [MISC] DsGetDcName function returns 1355: Dom:NETBIOS_DOMAIN Acct:(null) Flags: DS NETBIOS RET_DNS 05/07 16:21:09 [MISC] DsGetDcName function called: Dom:NETBIOS_DOMAIN Acct:(null) Flags: DS RET_DNS 05/07 16:21:09 [DNS] NlDnsHasDnsServers: DNS Server is NOT configured on this machine. 05/07 16:21:09 [MISC] NetpDcInitializeContext: DSGETDC_VALID_FLAGS is c01ffff1

Hi, I would like to share the following site: A “Netlogon event ID 5719” event message is logged when you start a Windows based computer Best Regards Dale

Thanks Dale. It turned out the solution was to set "Startup policy processing wait time" in group policy. It's located under Computer Configuration | Policies | Admin Templates | System | Group Policy. Although it states the default is 30 seconds for Vista it appears Windows 7 doesn't wait at all. The computers now pause for a few seconds at "Applying computer settings" and then correctly process group policy.

DJL, Hoping you'll get alerted by my reply - do you have any article or evidence that Windows 7 doesn't wait at all? I'm getting the same errors, having my networking guys look into the "spanning" thing from that article but your GPO fix seems worthwhile as well. I'd rather not slow down the bootup\logon process anymore though if I don't have to... thanks, JordanLawfirm IT guy

Hi Jordan, No - I couldn't find any evidence to support my theory. However I've recreated the problem on half a dozen AD domains and the GPO fix worked in each case. The GPO setting literally adds about 2s to the boot time - which is probably down to processing the group policies properly rather than actually waiting for the network to start. The setting doesn't affect logon performance at all. Regards, Daniel

Thanks for the quick reply back then btw, I am finally getting around to testing this. I've set this policy: "Startup policy processing wait time" to 30 seconds. First let me say, I have the exact same conditions you described, during startup I get NETLOGON Event ID 5719 followed shortly after by a Group Policy error - shortly after that Group Policy would seccessfully apply though. I really just want clean event logs. All Windows 7 Lenovo desktops. same image across the board. When I turn on that policy, the group policy error goes away but I still get the NETLOGON error. If I change to Static IP, that error is gone as well but that's obviously not an option. Do I need to set it higher than 30? I notice when I enabled it, the default time pre-populated in the field was 120 - not 30. Even though the explanation does say 30 like you say. What did you set yours to? any other ideas?Lawfirm IT guy

Hi, Did you find any solutions about NETLOGON errors? rgds Sven

Nope, just been living with it.Lawfirm IT guy

Hi, I found one solution that worked for me. Setting NIC property "Wait for Link" from Auto to On I'm using Intel DQ57TM motehrboard with integrated 82578DM Gigabit Network Adapter. I'm connected to Hewlett Packard 2626 1Gbps port. LACP disabled. rgds Sven