Ah, I was thinking a local firewall was blocking it. Sorry other than that I don't understand why it is not servicing any clients. I have my second DC running as a VM on Hyper-V and it is servicing DHCP and DNS both. The Hyper-V machine is only a host. Everything else runs as VM's
Jon On Wed, Jun 17, 2009 at 10:58 AM, Carl Houseman <[email protected]>wrote: > Where? I've proven that W2K3 server is servicing DNS requests from > other clients. I've proven that HVS08 is able to resolve DNS with a > non-W2K3 server. Nothing but a dumb LAN connecting all this hardware. > > > > Carl > > > > *From:* Jon Harris [mailto:[email protected]] > *Sent:* Wednesday, June 17, 2009 10:53 AM > *To:* NT System Admin Issues > *Subject:* Re: Hyper-V server DNS client problem > > > > Checked for blocked ports? > > > > Jon > > On Wed, Jun 17, 2009 at 10:45 AM, Carl Houseman <[email protected]> > wrote: > > I'm having issues using W2K3 as DNS server for Hyper-V Server 2008 > (hereafter HVS8). Many months ago I ran HVS8 on this same hardware and > didn't have this problem. So I don't think it's the hardware. > > > > Symptoms are: nslookup times out trying to access the W2K3 server, DNS > resolution uses the secondary server instead of the primary (W2K3 server). > > > > Nothing else on the network, including Vista and W7, has any problem using > the W2K3 server for DNS. > > > > Both HVS8 RTM and HVS8 R2 RC exhibit the same problem. > > > > The Hyper-V hardware can ping the W2K3 server but can't map a drive to it > by IP address. > > > > I guess I could try installing full Windows 2008 on the platform and see if > it's any different. Any other ideas? > > > > Thanks, > > Carl > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
