I'm seeing this on two different machines in my office that running RC1Build 7100. One is 64 bit and the other is 32 bit. Both take close to two minutes to re-establish a connection to the network. Both machines are dual boot, one Vista and the other Windows XP and neither XP or Vista on the same hardware take more than a couple seconds after reaching the desktop to re-establish a connection. When I reboot either machine to Windows 7, they get to the desktop nice and quick, then the little network icon in the systray starts the animation, indicating that it is trying to acquire network access, but within 5 seconds puts a red X and claims their are no networks available. Then at about a minute to a minute and a half, the animation starts again and quickly flips to a yellow triangle, indicating limited access. Within another 10 to 30 seconds, the icon switches to a normal connected state and all networking is restored. Again, these are both dual boot machines, and connect withing seconds using XP or Vista. I've also read a multitude of similar posts on other tech groups saying that going to static IPs and disabling IPv6 does *not* fix this problem. So, my question is . . . Is there a fix for this, because two minutes after a reboot to get re-connected to my network is ridiculous.

Hi, First, I would like to confirm the following questions: 1. How do the computers connect to Internet, via DSL or router? Are they in a domain or a workgroup? 2. When the issue began to occur? Does the issue occur after installing Windows 7? At this stage, you can refer to the following steps to troubleshoot the issue. 1. Upgrade the NIC driver on each Windows 7 machine. Please go to Device Manager, right click your hardware device in the list and select Update Driver Software; then click Search automatically for updated driver software. Note: Drivers on the Windows Update site are directly provided by hardware manufacturers. Microsoft tests drivers in various environments before they are published; however, we cannot guarantee all drivers will work on all hardware platforms as there are too many different models, although their hardware ID are the same as the standard version. In some cases, due to hardware modifications by different manufacturers, the driver updates may cause some error. Alternatively, you can also download the latest compatible driver from the manufacturer website. 2. Bypass the router or switch (if it has) and connect to Internet directly to check the result. 3. Temporarily turn off firewall on each machine and router (if it has) for a test. 4. Configure the connection to obtain an IP address automatically ======================================= a. Click "Start", input "NCPA.CPL" (without quotation marks) to Start Search bar and press "Enter". b. Right-click the network connection and click "Properties". If you are prompted for an administrator password or confirmation, type the password or provide confirmation. c. Click to highlight "Internet Protocol Version 6 (TCP/IPv6)" and click "Properties". d. Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". e. Click "OK". f. Click to highlight "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties". g. Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". h. Click "OK". i. Reboot the computer. Thanks, Novak

Hi, First, I would like to confirm the following questions: 1. How do the computers connect to Internet, via DSL or router? Are they in a domain or a workgroup? 2. When the issue began to occur? Does the issue occur after installing Windows 7? At this stage, you can refer to the following steps to troubleshoot the issue. 1. Upgrade the NIC driver on each Windows 7 machine. Please go to Device Manager , right click your hardware device in the list and select Update Driver Software ; then click Search automatically for updated driver software . Note: Drivers on the Windows Update site are directly provided by hardware manufacturers. Microsoft tests drivers in various environments before they are published; however, we cannot guarantee all drivers will work on all hardware platforms as there are too many different models, although their hardware ID are the same as the standard version. In some cases, due to hardware modifications by different manufacturers, the driver updates may cause some error. Alternatively, you can also download the latest compatible driver from the manufacturer website. 2. Bypass the router or switch (if it has) and connect to Internet directly to check the result. 3. Temporarily turn off firewall on each machine and router (if it has) for a test. 4. Configure the connection to obtain an IP address automatically ======================================= a. Click "Start", input "NCPA.CPL" (without quotation marks) to Start Search bar and press "Enter". b. Right-click the network connection and click "Properties". If you are prompted for an administrator password or confirmation, type the password or provide confirmation. c. Click to highlight "Internet Protocol Version 6 (TCP/IPv6)" and click "Properties". d. Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". e. Click "OK". f. Click to highlight "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties". g. Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". h. Click "OK". i. Reboot the computer. Thanks, Novak Connecting to the internet is not actually my problem, although it is affected by my problem. My problem is that I cannot connect to my local area network in a reasonable amount of time after a reboot, and that's what I need the most. I'm a developer and all my Sourcesafe data lives on a network storage device that I have to be able to access to do my job. My LAN is a simple peer to peer workgroup based network with a Linksys router, and the two machines in question both are dual boot (one Vista and one XP), and running the exact same hardware on both computers, but booting XP or Vista, they both link up instantly to the router. Booting either machine up in Windows 7 takes 1.5 to 2 minutes to get linked back up to the router. Both machines are based on Asus mobos with Intel chipsets and Intel quad core CPUs. Both protocols (IPv4 and IPv6) were already set to obtain IPs and DNS addresses automatically. There was a driver update for the on board Atheros gigabit ethernet adapter, but it made no difference at all.

Please restart the Windows 7 machine to Safe Mode with Networking to check the result. Does the issue still persist? In addition, let's assign a static IP address for a test. 1) Click "Start", input "NCPA.CPL" (without quotation marks) and press Enter. 2) Right click on the connection that you use for the local connection, and then click "Properties". 3) Click to select "Internet Protocol Version 4 (TCP/IPv4)", and then click "Properties". 4) Please manually assign the IP address, subnet mask, default gateway and the DNS settings referring to the settings of the router or the good computer. -------------------------------------------------------------------------------- Novak Wu - MSFT