Hi! I am just starting to learn about Windows Server and the associated technologies. Here is what I've done so far: Setup WS2008R2 Hyper-V. No other services run under this OS, only under the Hyper-V clients. I've created a few Hyper-V clients: AD DS and DNS Server WSUS Server Configured AD DS and DNS. I can access the internet from all client Hyper-Vs. I am trying to use WSUS, but it keeps timing out. I turned OFF all firewalls. No luck. I temporarily gave up on this. I have been trying to do updates directly from Microsoft. The Hyper-V host can update, no problem. The clients time out. Any ideas on what is going on? I tried manually going to update.microsoft.com and it seems to work. windowsupdate.com fails or goes really slow. Thanks in advance for any help!

Can you post and unedited ipconfig /all from DNS server and problem client? Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

1. You are doing to many steps. If you install operating system, the first task after reaching Internet connectivity is update oof all operating system.s Do it before any role or fea iture is configured (and repeat it again after roles/features are configured). Be sure, that iyper-V integration tools are installed. 2. You have not mentioned what is your connection to Internet. If you go through proxy server, then you need to set the following: netsh winhttp set proxy myproxy.domain.com:3128 (FYI the reverse path is netsh winhttp reset proxy myproxy.domain.com:3128

@Dave Patrick: I am going to try from a clean install with no AD DS or DNS servers between the VM and the real world. If I get this working and have problems with the AD DS and DNS, I'll let you know! (but there is plenty more reading I can do before pinging the forum again :) 1) Great idea! The host VM was all up to date before I started the Hyper-V but I did another update just to make sure. Only one recommended update: .NET 4 which I installed. I just created a new VM and turned off all of the other ones. I tried to do a Windows Activation - fail, reports error 80072EE2. Same for Windows Update. I researched error 80072EE2 but I am able to access any website using IE (including update.microsoft.com which launches Windows Update). I remoted into my Windows 8 laptop to post the ipconfig /all here: Windows IP Configuration Host Name . . . . . . . . . . . . : WIN-CS84LE1A5CI Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada pter Physical Address. . . . . . . . . : 00-15-5D-DF-7A-06 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::1112:b83:cabc:3701%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.14(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, January 15, 2012 5:33:16 PM Lease Expires . . . . . . . . . . : Monday, January 16, 2012 5:33:16 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 234886493 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-A5-2D-7E-00-15-5D-DF-7A-06 DNS Servers . . . . . . . . . . . : 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{D6F2EBA2-E973-495C-82A4-8EDC15DABA49}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:24de:3ab8:3f57:fef1(Pref erred) Link-local IPv6 Address . . . . . : fe80::24de:3ab8:3f57:fef1%13(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled 2) No proxy server to deal with, just a DHCP server at 192.168.1.1.

Looks like you're using a dsl router for DNS which is going to be problematic. Basically your DHCP server must hand out static address of AD server as primary DNS server address so clients can find DC. Then put the ISP's DNS addresses in the forward lookup of your DNS server so clients can find internet. Also make sure your server has static IP address outside of DHCP Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

Okay! I have figured it out!! My problem stems from sharing a network adapter with host and guest systems. The following posts helped me find a solution: http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/186debd5-c43f-40b7-b482-e9f8d3bbfee7 http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/ea7495a7-59bf-4e80-8302-57927a7c91ec Instead of the following the above solutions exactly, I used Bridged Connections. Here are the steps: Setup Hyper-V system on a server with only 1 network adapter Create an Internal network - this will create a second network adapter Start -> "View Network Connections" Select both network adapters (the local area connection and the Virtual Adapter), right click and select "Bridge Connections" DONE!