Solved

hyper v domian controler no internet connection

Posted on 2014-09-05
8
359 Views
Last Modified: 2014-11-12
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?
0
Comment
Question by:fbetag
  • 4
  • 2
  • 2
8 Comments
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 40307266
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
0
 
LVL 1

Author Comment

by:fbetag
ID: 40307306
Gateway 192.168.1.1
DC , DHCP, DNS, 192.168.1.2
do you have a better description on "go to DNS and configure ad DNS forwarder for the internet DNS ip "
0
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 40307309
1 way:

initially change the Network ip on the domain network or Internet modem/router ..
i.e   192.168.2.x  255.255.255.0  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
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 37

Expert Comment

by:Neil Russell
ID: 40307436
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
0
 
LVL 1

Author Comment

by:fbetag
ID: 40307560
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 169.254.39.155 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.
0
 
LVL 37

Expert Comment

by:Neil Russell
ID: 40307621
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 8.8.8.8 and/or 8.8.4.4
0
 
LVL 1

Accepted Solution

by:
fbetag earned 0 total points
ID: 40308093
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.
0
 
LVL 1

Author Closing Comment

by:fbetag
ID: 40316500
I found the solution to the issue.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The reason that corporations and businesses use Windows servers is because it supports custom modifications to adapt to the business and what it needs. Most individual users won’t need such powerful options. Here I’ll explain how you can enable Wind…
In previous parts of this Nano Server deployment series, we learned how to create, deploy and configure Nano Server as a Hyper-V host. In this part, we will look for a clustering option. We will create a Hyper-V cluster of 3 Nano Server host nodes w…
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

713 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question