We've started rolling Windows 7 RTM out across our organisation. This is working brilliantly for our desktop users, but for anyone who takes a laptop off the premises, it's become something of a nightmare. Every time one of our Windows 7 laptops is booted up (various installations of Enterprise and Ultimate) whilst not connected to our physical network, it spams the user with windows authentication dialogs. Our domain controller is pretty straightforward - A Server 2008 Enterprise machine with service pack 2, running all available updates - I can't see it being the DC. The problem manifests itself when connected, say, to a wireless home router, but not if the machine is plugged into a wireless broadband dongle. For this reason, our suspicion is falling upon the timing at which the internet connection is established - where the internet/LAN connection exists early in startup process, it's trying to authenticate. At a bit of a loss at the moment. Any suggestions?

Hi, It seems that the router cannot communicate with the laptops then establish the network in Windows 7 properly. Maybe after you upgrade the firmware of the router it can work properly. If there is no latest firmware update available, or the upgrade does not resolve the issue, we can only change the log in setting for users as a workaround. Please: 1. On the DC, put all Windows 7 laptops in one OU.2. Open Group Policy Management. Create new GPO under the Windows 7 laptop OU.3. Edit the GPO. Find the following policy: Computer Configuration\Administrative Template\System\Logon 4. In the right pane, find the policy Always wait for the network at computer startup and logon. Enable it. After change the setting, users may need to wait for longer time until the account logs on. However, the issue should not occur after logon.Arthur Xie - MSFT

We found aworkarounf forthis problem, but I would have thought that it would have been set by default. By ensuring that *.ourdomainname.com was included in the local intranet sites under the security tab of internet options, it "fooled" the machine into knowing that ourdomainname.com is indeed local to the computer.Robert Illing Services Manager Web Applications UK Ltd.