Hello We are getting Events 5719 from NETLOGON with the message "currently no logon servers available" and also event 1129 from GroupPolicy, both at boot time. The computer eventually gets a DHCP address and logs onto the domain after a short while. Each machine only logs one of each of these events at boot. These events appear only to occur to Windows 7 machines that are not on the same subnet as the DHCP server and DCs (we have multiple subnets for our three campuses). The computers are all connected to Cisco 2950 and 2960 switches with default switch port roles assigned, that is with spanning-tree set to portfast. Routing between subnets is performed by a Cisco 3550-12G. Assigning any affected computer a fixed IP address also resolves the problem, which leads me to think that it is probably a DHCP routing issue or a timing problem with the Windows 7 workstation giving up on getting a DHCP address before the DHCP server can respond. The DHCP server is also a DC running in an ESXi 4 cluster. I've read a bit online regarding event 5719 and have tried various things: 1. Updated NIC drivers. I experimented with our HP DC7800s, installing HPs latest driver as well as the latest driver from Intel (for the 82566DM-2), but without positive result. 2. Disabled media sensing on the NIC. 3. Disabled auto speed detection on the NIC and switch port and fixed at 100mb full duplex. 4. Changed TCPTimerWaitDelay and MaxUserPort settings in the registry. 5. Disabled WiredAutoConfig service 6. Disabled IPv6 on the workstation 7. Upgraded the Cisco Switch IOS to the latest version. None of this has solved the problem. The VLAN configuration for the 3550 specifies several ip helper-addresses: the DHCP server, our SCCM server and another server that runs various licensing applications. interface Vlan41 description MS ip address 10.4.0.1 255.255.0.0 ip helper-address 10.1.1.13 ip helper-address 10.1.1.9 ip helper-address 10.1.1.68 ip directed-broadcast 101 I'm hoping someone might have some advice as to how to proceed with this one.

Andrew Chapman wrote: Hello We are getting Events 5719 from NETLOGON with the message "currently no logon servers available" and also event 1129 from GroupPolicy, both at boot time. The computer eventually gets a DHCP address and logs onto the domain after a short while. Each machine only logs one of each of these events at boot. These events appear only to occur to Windows 7 machines that are not on the same subnet as the DHCP server and DCs (we have multiple subnets for our three campuses). The computers are all connected to Cisco 2950 and 2960 switches with default switch port roles assigned, that is with spanning-tree set to portfast. Routing between subnets is performed by a Cisco 3550-12G. Assigning any affected computer a fixed IP address also resolves the problem, which leads me to think that it is probably a DHCP routing issue or a timing problem with the Windows 7 workstation giving up on getting a DHCP address before the DHCP server can respond. The DHCP server is also a DC running in an ESXi 4 cluster. I've read a bit online regarding event 5719 and have tried various things: 1. Updated NIC drivers. I experimented with our HP DC7800s, installing HPs latest driver as well as the latest driver from Intel (for the 82566DM-2), but without positive result. 2. Disabled media sensing on the NIC. 3. Disabled auto speed detection on the NIC and switch port and fixed at 100mb full duplex. 4. Changed TCPTimerWaitDelay and MaxUserPort settings in the registry. 5. Disabled WiredAutoConfig service 6. Disabled IPv6 on the workstation 7. Upgraded the Cisco Switch IOS to the latest version. None of this has solved the problem. The VLAN configuration for the 3550 specifies several ip helper-addresses: the DHCP server, our SCCM server and another server that runs various licensing applications. interface Vlan41  description MS  ip address 10.4.0.1 255.255.0.0  ip helper-address 10.1.1.13  ip helper-address 10.1.1.9  ip helper-address 10.1.1.68  ip directed-broadcast 101 I'm hoping someone might have some advice as to how to proceed with this one. What about the Group Policy "Always wait for the network on computer startup and logon" under Computer Configuration/Administrative Templates/System/Logon ? That would be my first thought on Win7 PCs with those issues. Wolfgang

Thanks Wolfgang. Do you mean to enable or disable the policy? Either way, I've tested it enabled and not, but the NETLOGON error persists.

Andrew Chapman wrote: Thanks Wolfgang. Do you mean to enable or disable the policy? Either way, I've tested it enabled and not, but the NETLOGON error persists. I'd enable that policy. This policy is really working only after the first reboot after applyig that policy, because it obviously can't be set before group policy processing takes place. Wolfgang