hyper v domian controler no internet connection

I have setup an Hyperv server and a VM as a domain controller with dhcp and dns. After doing this the server can no longer access the internet. I have verified dhcp and dns are working and I have setup server options for the router 003 and dns 006 but It still wont connect to the internet. A second vm that is not on the domain connects just fine. Any suggestions?
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

fbetagConnect With a Mentor Author Commented:
I was able to resolve the issue. There was a network device on the network with the same IP address preventing DNS from working. Thanks for your Suggestions.
Sajid Shaik MSr. System AdminCommented:
what is the gateway ip and DNS on the DHCP as well as the Domain server? what is the gateway ip of domain?
it shoud be your internet gateway ip (i.e Modem/router IP)

go to DNS and configure ad DNS forwarder for the internet DNS ip

because the DNS of the local domain points to your Local lan then how the internet traffic will find...

when you create DNS forwarder then it'll forward internet traffic to the outside..

all the best
fbetagAuthor Commented:
do you have a better description on "go to DNS and configure ad DNS forwarder for the internet DNS ip "
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Sajid Shaik MSr. System AdminCommented:
1 way:

initially change the Network ip on the domain network or Internet modem/router ..
i.e   192.168.2.x  or any other

both networks should be different sub net...

go to domain DNS open DNS - rightclick dns - properties - edid - add ip of Internet DNS server - OK

now ping to external networks - it should get reply.

see the picture dns
all the best

the other way

on the modem / router  point the internal DNS server to your Domain and add additional DNS to your Modem.

but he dns forwarder is the best practice.
all the best
Neil RussellTechnical Development LeadCommented:
Are you saying that the Domain Controller VM can not connect to the internet?
The domain controller should ONLY ever point to itself and another ADDC if you have one for DNS.

The AD DNS should then be configured to forward DNS requests to tour ISP DNS address.

I assume that your DC has a static IP configuration yes?

And I have no idea why Shaik is advising you to use a different IP Subnet. Stick with your 192.168.1.x
fbetagAuthor Commented:
yes the VM domain controller can not connect to the internet.
I have added the google forwards but it cant resolve the FQDN.
Under the DNS properties interfaces it shows a address as well as the DC address. I have unchecked the 169 address but the issue still persists. I believe this has to do with the console port in some way the DNS wants to use that port. The DC is staticly assigned. The nics are teamed so they should not have different ip addresses.
Neil RussellTechnical Development LeadCommented:
Teamed nics in the DC?  Never a good idea.
The DC DNS will use whatever you configure it to.

The ONLY Nic on the DC should point to itself for DNS.

Your DNS Server configuration on the DC (ROLES->DNS) should then be configured to forward to your ISP or and/or
fbetagAuthor Commented:
I found the solution to the issue.
All Courses

From novice to tech pro — start learning today.