Speculator Posted March 28, 2011 Posted March 28, 2011 I'd like to add my voice to this one. We're experiencing the same problem on our Win 7 clients with our 2008 R2 DHCP server and Cisco DHCP Helpers. The symptoms are the same, with GP's being inconsistently applied. It's particularly serious for the Wireless policies on some of our laptops, as they don't always apply those policies, and fail to connect to the network. They can't reconnect until someone does a gpupdate on them over a wired connection. We've tried setting the DhcpConnForceBroadcastFlag, with little success. I assume MS haven't issued a fix for this, and if so, the only solution for us is to drastically change our DHCP setup. Does anyone know if this affects *nix DHCP servers? I assume using a multi-homed DHCP server will work if it has an interface in the problem VLAN, but that seems such an ugly solution. L8r.
Michael Posted March 28, 2011 Posted March 28, 2011 Looking at the date when this was started, does Windows 7 Service Pack 1 fix this issue? Can anyone confirm it?
simon636 Posted March 28, 2011 Posted March 28, 2011 SP1 for win 7 makes no difference at all, i find it hard to believe that this wasnt accomodated for by Microsoft, any organisation of a medium size will be using vlans with Cisco kit and msft DHCP servers. I also find the dhcp con flag solution to be intermittant, disabling the public profile seems the only constant fix, which isnt an option for me We have trunked vlans on wireless access points allocated to different ssid's, we have over 1200 clients with the netlogon error both wired and wireless.
Speculator Posted March 28, 2011 Posted March 28, 2011 SP1 for win 7 makes no difference at all, i find it hard to believe that this wasnt accomodated for by Microsoft, any organisation of a medium size will be using vlans with Cisco kit and msft DHCP servers. I also find the dhcp con flag solution to be intermittant, disabling the public profile seems the only constant fix, which isnt an option for me We have trunked vlans on wireless access points allocated to different ssid's, we have over 1200 clients with the netlogon error both wired and wireless. I have been working with a helpful chap, by the name of Brent (an MS employee) in the MS Technet forums recently, he has confirmed the case has been logged and offers some solutions to the problem, in this thread. These are one of, using the DhcpConnForceBroadcastFlag setting, disabling public profile, or firewall completely, or using the startup policy processing wait time. In my own testing I have confirmed that the DhcpConnForceBroadcastFlag setting is unreliable (although I haven't played with the associated DhcpConnEnableBcastFlagToggle yet, which may be required), and that disabling the public firewall profile does nothing. We had also employed a startup policy processing wait time, but it didn't seem to work, although I will revisit that before writing it off altogether. There is no fix forthcoming from MS. So, has anyone successfully managed to work around this problem yet?
TimmG6376 Posted May 17, 2011 Posted May 17, 2011 I have mitigated the Group Policy processing issues by tweaking the following GPO settings: Computer Configuration/Administrative Templates/System/Group Policy/Startup policy processing wait time Computer Configuration/Administrative Templates/System/Logon/Always wait for the network at computer startup and logon Computer Configuration/Administrative Templates/System/Net Logon/Expected dial-up delay on logon None of the suggested workarounds for the NetLogon errors have worked. Disabling the firewall did nothing. The DHCPConnForceBroadcastFlag can be implemented but the global setting only applies if the entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\ is deleted.
Speculator Posted May 17, 2011 Posted May 17, 2011 Are you experienceing the NETLOGON problem on a wired or wireless connection? We were able to stop it occurring on wired only. On wireless it still persists. I have found the global DHCPConnForceBroadcastFlag setting to be rather useless, seeing as you should set DhcpConnEnableBcastFlagToggle as well, which you can only do per interface GUID. It's a hard problem to manage. I've written a bit about it here, in my blog. I might have a followup soon with some similar issues we're seeing at boot on wireless PC's (however we still haven't fixed those problems completely). I have mitigated the Group Policy processing issues by tweaking the following GPO settings: Computer Configuration/Administrative Templates/System/Group Policy/Startup policy processing wait time Computer Configuration/Administrative Templates/System/Logon/Always wait for the network at computer startup and logon Computer Configuration/Administrative Templates/System/Net Logon/Expected dial-up delay on logon None of the suggested workarounds for the NetLogon errors have worked. Disabling the firewall did nothing. The DHCPConnForceBroadcastFlag can be implemented but the global setting only applies if the entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces\ is deleted.
TimmG6376 Posted May 18, 2011 Posted May 18, 2011 Are you experienceing the NETLOGON problem on a wired or wireless connection? We were able to stop it occurring on wired only. On wireless it still persists. I have found the global DHCPConnForceBroadcastFlag setting to be rather useless, seeing as you should set DhcpConnEnableBcastFlagToggle as well, which you can only do per interface GUID. It's a hard problem to manage. I've written a bit about it here, in my blog. I might have a followup soon with some similar issues we're seeing at boot on wireless PC's (however we still haven't fixed those problems completely). Wired gigabit. Not too concerned about the wireless connections as everyone with a laptop docks when at their desks so wireless is only used occasionally or for guests. I've tried the DHCPConnForceBroadcastFlag and DhcpConnEnableBcastFlagToggle to no avail. If it is working for you though I will submit this Powershell script that will allow you to push these entries out to multiple machines. As with any script use at your own risk and test before using in production # Replace with your subnet $IpSubnet = "10.1.1." # Use WMI query to get GUID for network adapter with IP address matching the IP subnet configured above $NIC = Get-WmiObject -query "select settingid, ipaddress from win32_networkadapterconfiguration WHERE IPEnabled = 'True'" | ? { $_.IpAddress -match $IpSubnet } $GUID = $NIC.SettingID.ToString() #Use GUID to set registry path to interface key $RegPath = "HKLM:\System\CurrentControlSet\services\TCPIP\Parameters\Interfaces\" + $GUID $RegKey = Get-Item $RegPath # Sets DhcpConnForceBroadcastFlag property value to 1 Set-ItemProperty $RegKey.PSPath -name DhcpConnForceBroadcastFlag -Value 1 # Checks for existence of DhcpConnEnableBcastFlagToggle property # If it does not exist create the property with value 0 # If it does exist set the value to 0 If ((Get-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -ErrorAction SilentlyContinue) -eq $null ) { New-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -Value 0 -PropertyType DWORD } Else { Set-ItemProperty $RegKey.PSPath -Name DhcpConnEnableBcastFlagToggle -Value 0 } I created a GPO on a test OU and configured this script as a Shutdown script. It configures the registry as desired, however, I'm still getting the NetLogon errors with my test machine.
TimmG6376 Posted May 18, 2011 Posted May 18, 2011 (edited) Ok I had completely ignored Windows 7 SP1 because I had read in multiple threads that it had no effect on this issue. We have not deployed SP1 as of yet, but unrelated to this issue I decided that it was time to install it on my PC and see if any issues arise. Incredibly after rebooting the NetLogon errors stopped. Disabled my GPO that modifies the registry. Set the registry back to defaults (DhcpConnForceBroadcastFlag = 0; deleted DhcpConnEnableBcastFlagToggle ). Cleared my System log. After another reboot still no NetLogon errors. I do still have the firewall disabled so that is my next test. CORRECTION: Seems to be a combination of SP1, completely the disabling firewall (domain,private,public), and the forcing broadcast flag via the registry. With all three of those I no longer get NetLogon errors on a wired connection. Will have to check wireless tomorrow. Edited May 18, 2011 by TimmG6376
Oops_my_bad Posted May 22, 2011 Posted May 22, 2011 Could I be affected by this as well? I am seeing the same errors and inconsistent GP application, but we are a single broadcast domain and DHCP server is 2008 :/ No DHCP helpers in use.. WOrkstations are not SP1'd yet.. just gonna try one now and see how that goes
Oops_my_bad Posted May 22, 2011 Posted May 22, 2011 Seems like a pretty fundamental flaw... how about we just don't pay our annual MS subs? If enough of us do that it might make M$ sit up and take notice.
TimmG6376 Posted May 23, 2011 Posted May 23, 2011 Could I be affected by this as well? I am seeing the same errors and inconsistent GP application, but we are a single broadcast domain and DHCP server is 2008 :/ No DHCP helpers in use.. WOrkstations are not SP1'd yet.. just gonna try one now and see how that goes There are a few NICs that can also exhibit this behaviour due to GP trying to process before link negotiation has completed. See the post from Brent Hu at the link below (about 11 posts down the page). Windows 7 Slow to Log on with Re-Directed Folders - Windows Server 2008 1
Oops_my_bad Posted May 23, 2011 Posted May 23, 2011 Hmm interesting. It seems this is only happening to some of our wireless laptops - atheros WIFI cards seem fine, I am only seeing this error on intel WIFI laptops. Maybe my issue is unrelated to this topic.. sorry.
teckedd Posted May 27, 2011 Author Posted May 27, 2011 (edited) Hi, Microsoft have now released a KB article with a work around, they are still looking into the possibility of releasing a hotfix. The KB is 2459530 Hope this helps, Edd Edited May 27, 2011 by teckedd 1
teckedd Posted June 6, 2011 Author Posted June 6, 2011 Hi, I have some possible good news regarding the hotfix; I have received a beta fix that I hope to test very shortly. Microsoft are hoping to release the public fix in August. Before anyone asks I cannot redistribute the fix as it’s a beta and Microsoft will hunt me down however, once tested I will let you know if there is light at the end of the tunnel! Edd
teckedd Posted June 13, 2011 Author Posted June 13, 2011 Hi All, Well some good news! I tested the hotfix today and it looks like it resolves the problem so I now need to continue the waiting game and wait for the public release before I can roll it out! I will post the link to the hotfix when it’s released. Edd
russdev Posted July 20, 2011 Posted July 20, 2011 I love this 12 month turn around on a fix . However at least light for people who are having the issue.
JasperK Posted August 12, 2011 Posted August 12, 2011 Hi all, It has been several months.. I experience the same problem. Has Microsoft created a hotfix yet? Greets Jasper
googlemad Posted August 16, 2011 Posted August 16, 2011 Getting similar errors on our workstations but not using Windows Firewall...when a static IP is set everything works great. Just when using DHCP? Any ideas...
Bitmapped Posted September 7, 2011 Posted September 7, 2011 I've been running into a case I think might be related to this issue. Win7 SP1 x64 machines joined to a domain, get their IPs through a Cisco helper. On system wake (seen it from sleep, not sure from full boot) have intermittent issues with "no log on servers" error. NIC shows it has a connection, but if I log in with a local account Windows tries to get an IP then gives up and actually tells me the network connection is unplugged. Reboot generally solves the problem. I went through the directions in the MSKB article and on my systems at least, the TCP-IP interface already had the force broadcast flag set to 1. I've tried different drivers and autonegotiation settings without luck. Trying now to disable the public-profile firewall in case that's the isuse. Any word on when Microsoft might make this hotfix available so I can test that? Trying to track down these issues in two computer labs is driving me crazy.
SYNACK Posted September 8, 2011 Posted September 8, 2011 I've been running into a case I think might be related to this issue. Win7 SP1 x64 machines joined to a domain, get their IPs through a Cisco helper. On system wake (seen it from sleep, not sure from full boot) have intermittent issues with "no log on servers" error. NIC shows it has a connection, but if I log in with a local account Windows tries to get an IP then gives up and actually tells me the network connection is unplugged. Reboot generally solves the problem. I went through the directions in the MSKB article and on my systems at least, the TCP-IP interface already had the force broadcast flag set to 1. I've tried different drivers and autonegotiation settings without luck. Trying now to disable the public-profile firewall in case that's the isuse. Any word on when Microsoft might make this hotfix available so I can test that? Trying to track down these issues in two computer labs is driving me crazy. Do the client machines have intel NICs in them, they have junky drivers and you need to go into the advanced driver settings and set wait for link to on rather than autodetect.
Bitmapped Posted September 8, 2011 Posted September 8, 2011 Do the client machines have intel NICs in them, they have junky drivers and you need to go into the advanced driver settings and set wait for link to on rather than autodetect. We basically have two groups of PCs, Dell Vostro 200s with Intel NICs and Vostro 230s with Broadcom Netlink 57xx NICs. The Intel NICs seem fine, it's the Broadcom ones that are having problems.
SYNACK Posted September 8, 2011 Posted September 8, 2011 We basically have two groups of PCs, Dell Vostro 200s with Intel NICs and Vostro 230s with Broadcom Netlink 57xx NICs. The Intel NICs seem fine, it's the Broadcom ones that are having problems. If the other brand are working fine then it is not related to the issue this thread deals with rather with drivers. Check for a simmilar setting to the one I recommended above in the broadcom drivers and if you can't find one disable the 'allow computer to turn off this device to save power' setting under the power tab in the driver. This will prevent the computer from sleeping the NIC when it goes into suspend and should prevent the issue.
Bitmapped Posted September 8, 2011 Posted September 8, 2011 (edited) If the other brand are working fine then it is not related to the issue this thread deals with rather with drivers. Check for a simmilar setting to the one I recommended above in the broadcom drivers and if you can't find one disable the 'allow computer to turn off this device to save power' setting under the power tab in the driver. This will prevent the computer from sleeping the NIC when it goes into suspend and should prevent the issue. Well, a clarification I guess. I have seen the log entries on the Intels but it is the Broadcoms that have been causing bigger usability problems. I've been through a variety of different driver versions and settings for auto-negotiation, although I haven't tried anything like "wait for link." I'm not seeing a setting like that on the Broadcom drivers. I've been loathe to disable allowing Windows to turn off the NIC because that also means my ability to Wake-on-LAN the computers goes away. A question: With this issue are you just seeing the log entries and/or Group Policy failures or are you getting real logon errors? For the Broadcoms, when users try to logon I will intermittently get "no logon server is available to service the logon request" if they try to use a domain account. As I mentioned above, if I login with a local account Windows acts like it is trying to get an IP/identify the network then it seems to give us and say we're unplugged. Edited September 8, 2011 by Bitmapped details regarding Broadcom drivers
AnnickIT Posted September 15, 2011 Posted September 15, 2011 Is there any further information on whether the Hotfix is now available? I am having this same problem. The main effect I am noticing, other than the Netlogon/GP/Time Service errors, is that after perhaps an hour my Win7 client drops all mapped drives and is unable to connect to the server (SBS 2003). It retains internet access. However, if I open a program that needs access to a database on the server BEFORE the connection is dropped, the client retains access to the server indefinitely whilst this program is running. Once the connection is dropped, the only way to reconnect is to log out and log back in (or restart, obv.). I am connected to the server via a switch. Will try the workarounds suggested above. I have 4 Win7 clients and 2 XP, and am only seeing the problem on 1 laptop. Haven't yet been able to narrow it down why - the only obvious difference is that it's an oldish machine with a slow processor, originally XP, reformatted and Win7 installed (have not yet updated to SP1). The ethernet NIC is not any of the models previously mentioned.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now