Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, January 18, 2015 9:30 PM
Clients connect to the DHCP and are assigned an address and correct gateway. They are not able to connect to the internet because the IP v4 DNS address is not pushed. As long as I set the DNS manually it works on the clients, but some devises are not working. I could blame the device, but the only difference from letting my router (Netgear WNDR3700) manage the DHCP duties the clients not getting a DNS address.
Connection-specific DNS Suffix . : BROUGHTON.local
Description . . . . . . . . . . . : Marvell AVASTAR 350N Wireless Network Controller
Physical Address. . . . . . . . . : 60-45-BD-EA-77-8E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f822:5c4b:6d72:e971%4(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.35(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, January 17, 2015 9:00:24 PM
Lease Expires . . . . . . . . . . : Wednesday, February 24, 2151 8:52:31 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.3
DHCPv6 IAID . . . . . . . . . . . : 341853629
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-E5-F1-73-00-00-00-00-00-00
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
This ipconfig /all from my Windows 8.1 laptop with DNS set to automatically get address has IPv6 DNS server addresses and I cannot connect to the internet.
I have followed best practices using the Server Manager wizard to setup DHCP and DNS on this server.
I have had this server running and my router managing DHCP and DNS for years. I wanted to configure the server to manage DHCP and DNS for my home network, but I will have to go back if these problems persist. I have normal consumer devises such as my smart TV and DirecTV recievers that are not working will with Server 2012 DHCP.
Thanks
Steve
All replies (8)
Monday, January 19, 2015 6:26 PM âś…Answered
That 006 DNS Servers Standard configuration was what my DHCP server was missing. Devices are now recognizing the network and connecting to the Internet.
Thanks
Sunday, January 18, 2015 10:22 PM | 1 vote
Hi,
Can you please post your scope options, like this
Option Name Vendor Value Policy Name
003 Router Standard x.x.10.1 None
006 DNS Servers Standard x.x.10.6 None
015 DNS Domain Name Standard root.x.com None
066 Boot Server Host Name Standard x.x.10.22 None
Select your dhcp server, and expand 'IPv4'->'your_scope'->'export to list'-and safe it to txt.
Best Regards,
Jesper Vindum, Denmark
Systems Administrator
Help the forum: Monitor(alert) your threads and vote helpful replies or mark them as answer, if it helps solving your problem.
Monday, January 19, 2015 12:27 AM
as well if you are running 2012 Essentials check this
Grey
Monday, January 19, 2015 2:58 AM
Check that page and my configuration, the only thing I had that was not in that setup was I had put my Routers IP as my secondary DNS.
I have removed it for now to match the setup, should I keep the Router as my secondary DNS?
Thanks
Steve
Monday, January 19, 2015 3:02 AM
Option Name Vendor Value Policy Name
003 Router Standard 192.168.1.1 None
006 DNS Servers Standard 192.168.1.3 None
015 DNS Domain Name Standard BROUGHTON.local None
I added the Option 006, it had not been setup during my initial configuration.
I switched my desktop to Automatic DNS and ran ipconfig /renew and then ipconfig /all and it listed the IPv4 DNS 192.168.1.3 which is the Server 2012. I will test my other equipment and update this post, but I believe that fixed the issue.
Thanks
Steve
Monday, January 19, 2015 7:10 PM
That 006 DNS Servers Standard configuration was what my DHCP server was missing. Devices are now recognizing the network and connecting to the Internet.
Thanks
You are most welcome.
Best Regards,
Jesper Vindum, Denmark
Systems Administrator
Help the forum: Monitor(alert) your threads and vote helpful replies or mark them as answer, if it helps solving your problem.
Wednesday, January 21, 2015 9:09 AM
Hi Steve,
Glad to hear that you have solved this issue and thanks for sharing in the forum. Your time and efforts are highly appreciated.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Sunday, April 22, 2018 8:23 PM
That 006 DNS Servers Standard configuration was what my DHCP server was missing. Devices are now recognizing the network and connecting to the Internet.
Thanks
Yep, this did it for me. More specifically I had migrated from a previous DNS Server and while the 006 entry had migrated, I had never updated it to the new DNS server's IP. Such a simple solution to a problem that plagued me for hours.