sglee
asked on
DNS/Name Server
Hi,I need to re-configure this existing Windows 2012 Essentials server (192.168.1.5) network. Currently:
(1) DNS server is running on the server.
(2) DHCP is currently running off Linksys Router. The previous IT person had Maraki router that went dead so I replaced it with my Linksys router. Since I did not see DHCP server on W2012 server, I assumed that Meraki router was running it in the past, so I simply enabled DHCP function in Linksys. Unfortunately workstation PC is looking at Linksys router(LAN IP: 192.168.1.1) as DHCP and DNS.
Here is TCP/IP information that each domain joined workstation PC receives:
Connection-specific DNS Suffix . : columbus.rr.com
IPv4 Address. . . . . . . . . . . : 192.168.1.103
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
To correct the situation, I need to run DHCP server on W2012 server, disable DHCP server in Linksys router and keep DNS server on W2012.
Here is my question: As I create DHCP server in W2012, I am going to set 192.168.1.5 as DNS server, 192.168.1.1 as Gateway, should I keep DNS server (8.8.8.8) in Server TCP/IP properties? If I keep 8.8.8.8, the what might been the reason to have 192.168.1.5 and 25.112.86.132 in DNS/[Name Servers Tab]?
While keeping 8.8.8.8 as it is in W2012 TCP/IP as DNS servers, can I just have workstation PC point to W2012 (192.168.1.5) as its DNS server and remove 192.168.1.5 and 25.112.86.13 from DNS manager/forward lookup Zones Properies/Name Servers tab?
DNS---Name-Servers.PNG
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
no idea what 25.112.86.13 is. your company's public DNS?
ASKER
I have no idea. I just took over this network recently.
Not only it had 25.112.86.13 which does not resolve, but there was additional entry192.168.1.3 which does not exist on this network.
Not only it had 25.112.86.13 which does not resolve, but there was additional entry192.168.1.3 which does not exist on this network.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The primary DNS should be the same IP address that you are assigning to that new box. .5
Too bad the meraki went dead. Great hardware.
Too bad the meraki went dead. Great hardware.
ASKER
@LockDown32
Your suggestion is typically how I do it.
But while googling 8.8.8.8, I found this link on the first page:
This person claims that using 8.8.8.8/8.8.4.4 as DNS forwarders is faster than using ISP provided DNS.
http://serverfault.com/questions/169279/how-can-i-choose-between-using-my-isps-dns-or-googles-8-8-8-8
Is there some truth to that?
Your suggestion is typically how I do it.
But while googling 8.8.8.8, I found this link on the first page:
This person claims that using 8.8.8.8/8.8.4.4 as DNS forwarders is faster than using ISP provided DNS.
http://serverfault.com/questions/169279/how-can-i-choose-between-using-my-isps-dns-or-googles-8-8-8-8
Is there some truth to that?
ASKER
I just installed DHCP using Add roles in Server Manager and ran DHCP server.It is strange to see 169.254.80.118 instead of FQDN which is fileserver.domain_name.loc
Any idea why 169.254.80.118 is showing up under DHCP name?
8.8.8.8 and 8.8.4.4 are Google's public DNSs. You can use them as forwarders on the DNS server on the server but it is suggested to use the DNS servers the ISP gave you first.
No idea why 169.254.80.118 is showing up as the dhcp server name. Try deleting the dhcp server then when you add it back specify it by fqdn.
No idea why 169.254.80.118 is showing up as the dhcp server name. Try deleting the dhcp server then when you add it back specify it by fqdn.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I deleted 169.254.80.118 and created a new one with 192.168.1.0. At that time, 169.254.80.118 was gone.After adding IP Range, Scope options, I disabled DHCP server from Linksys Router.
I ran "ipconfig /renew" on one of the workstations, but it failed to get a new IP information from the new DHCP server running off W2012 with following error.
--------------------------
C:\Users\user>ipconfig /renew
Windows IP Configuration
No operation can be performed on Wireless Network Connection 2 while it has its
media disconnected.
No operation can be performed on Bluetooth Network Connection while it has its m
edia disconnected.
An error occurred while renewing interface Wireless Network Connection : unable
to contact your DHCP server. Request has timed out.
--------------------------
So I rebooted the PC, but the same problem. It still maintains the IP information obtained from Linksys DHCP server as below and of course, this computer name does not show up in DHCP/IPv4/Scope (192.168.1.0)/Address Leases section.
--------------------------
IPv4 Address. . . . . . . . . . . : 192.168.1.198(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, May 30, 2016 11:43:26 AM
Lease Expires . . . . . . . . . . : Tuesday, May 31, 2016 2:20:29 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
--------------------------
I closed DHCP server, re-opened it, and I still saw 169.254.80.118. I wonder if I should have rebooted W2012 after adding new DHCP server with Scope and scope options?
You shouldn't have to reboot after adding a DHCP Server. Double check the IP Address on the server. Post a screen shot.
Also double check the Linksys and make sure the DHCP Server is disabled on it. You don't per chance have a second linksys somewhere do you?
The error you are getting on the workstation is that the network cable is unplugged and when you do a ipconfig /renew it is always a good idea to do a release first
ipconfig /release
then
ipconfig /renew
Also double check the Linksys and make sure the DHCP Server is disabled on it. You don't per chance have a second linksys somewhere do you?
The error you are getting on the workstation is that the network cable is unplugged and when you do a ipconfig /renew it is always a good idea to do a release first
ipconfig /release
then
ipconfig /renew
Just a thought on the Linksys. As a rule you have to "save" the settings. After you disable the DHCP on the Linksys make sure you save the change.
ASKER
I just opened up 192.168.1.1(Linksys router) and confirmed that DHCP server is NOT enabled.I can't do ipconfig /release on this particular computer because I am not onsite, rather connected to it remotely. So if I release current IP information, then I will loose the connection and there would not be anyone onsite that can run ipconfig /renew for me at this point.
I have remote access to a computer that has both wireless and LAN connections. I will try those commands on that computer.
ASKER
Fyi, I rebooted the linksys router after making the change.
You got the linksys done. Understood about working remotely. Can you post a screen shot of the IP setting on the server?
ASKER
here it is
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry I forgot to update TCP/IP DNS server addresses. But I had ISP's Name server addresses in in DNS Server Manager.But these won't have caused the workstation PCs from detecting a new DHCP server as it restarted, won't it?
ASKER
I just reopened the DHCP server from W2012 and I am seeing some workstation PCs.Maybe it is working, but do I have to worry about 169.254.80.118?
ASKER
Here is ipconfig /all from one of the computer that was listed in DHCP address leases list
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, May 18, 2016 3:25:03 AM
Lease Expires . . . . . . . . . . : Tuesday, May 31, 2016 2:34:50 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 192.168.1.5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, May 18, 2016 3:25:03 AM
Lease Expires . . . . . . . . . . : Tuesday, May 31, 2016 2:34:50 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.5
DNS Servers . . . . . . . . . . . : 192.168.1.5
Everything looks great. I still don't why 169.254.80.118 is showing up as the name of the DHCP server but it could be because the server wasn't registered with its own DNS because you weren't pointing it at itself when you added the DHCP server.
Now that the IP and DNS addresses on the server are correct you can try deleting and re-adding it if you want. Or if it ain't broke :)
Now that the IP and DNS addresses on the server are correct you can try deleting and re-adding it if you want. Or if it ain't broke :)
ASKER
As I restart each computer, now they all started getting new set of IP addresses from new DHCP server.
As to 169.254.80.118, as long as DHCP server continue to function correctly, I am going to leave it as it is.
Thanks for your help!
As to 169.254.80.118, as long as DHCP server continue to function correctly, I am going to leave it as it is.
Thanks for your help!
I agree. Not worth temping fate. Happy to help.
Usually you get an address like 169.254.80.118 if you have another adapter on the server that is enabled but not plugged in, next time just disable it before creating your scope.
ASKER