Recently I have had several computers running Windows 7 pro 32-bit having trouble connecting to the network. I support a number of computers on an internal network. The Microsoft ISATAP adapter seems to be at the root of the problem. When I run ipconfig /all, I find these details: Tunnel adapter isatap.(our domain): Media State . . . . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : (our domain) Description . . . . . . . . . . . . . . .: Microsoft ISATAP Adapter Physical Address . . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled . . . . . . . . . . . . : No Autoconfiguration enabled . . . . : Yes It seems that the adapter in our situation is trying to connect to an ISATAP server, but it doesn't exist and cannot connect to the server or the internet. This was originally affecting two Dell Optiplex 980s, but began to affect some laptops which were not able to connect to wireless, which suggests that this is an OS issue. I found that going into Device manager > View> Show Hidden Devices > Network Adapter and uninstalling the ISATAP drivers will get rid of the problem (at least so far). I am looking for more information about the Microsoft ISATAP adapter. What does it do? Why does it kick in at random times? Why are these widely problematic ISATAP drivers included in Windows 7? Is there a fix (better than the one I have been using) that we can include on our machine images so we do not have users reporting no internet connectivity?