Weirdest thing I've seen. Brand new W2K8 R2 Enterprise server, hypervisor install went fine. Built a new VM (also W2K8 R2), went to register Windows and got timeout error 0x80072EE2. Windows update failed with 8024402F. The hypervisor can hit microsoft.com, register, update and the like with no problems. Guest OS can hit google in a browser with no problem. Can ping other sites by name or IP with no error, but a ping attempt at MS does a DNS resolution and times out on the ping.
Basically the OS will just NOT communicate with MS anything. Kind of sounds like virus in the hosts file type behavior...but isn't. It's a brand new build. Haven't even added roles, RDP, shares, or anything. Disabled the on-system firewall and still no luck. Filtering not happening via our perimeter routing/firewall system either.
Blew away the VM, and started from scratch. Same behavior on the second and third attempts.
Not sure if this is significant, but it's an HP OEM version of the OS.
Completely at a loss for what could be causing this.
Thanks in advance for any pointers,