Jump to content
RESET Forums (homeservershow.com)
doliveira

Network Setup – Router LAN – DHCP Settings

Recommended Posts

doliveira

Hi,
 
I’m setting up my small office network and on my server I will use the “Windows Server 2012 R2 Essentials”.
 
As router I use the TP-Link TL-ER5120 and im in the phase of setting up the router and I don’t know if I must fill the fields “Default Gateway” and “Default Domain” as you can see on the image I have attached to this thread.
 
On my network it will be the server to handle the DNS, but it will be the Router to handle the DHCP.
 
So can someone please look at the image and tell me if I should leave that 2 fields in blank or should o fill them.
 
I was thinking on putting my domain name in the “Default Domain” as: mydomain.local. Should I do that?
 
Feel free to share you advice.
 
Thanks

router-settings-2.jpg

Edited by doliveira

Share this post


Link to post
Share on other sites
ShadowPeo

Any paticular reason you are not going to dish DHCP out from the server??

 

By default the gateway should be the router address (I am assuming that is the internet connection) unless you are utilising a transparent proxy but given your question I would think not.

 

Domain name is dependent on how your setting up the rest of the network, are you setting it up on a domain controller or not?

 

honestly I would utilise the DHCP service on the server, it is will give you more flexibility long term

Share this post


Link to post
Share on other sites
doliveira

Any paticular reason you are not going to dish DHCP out from the server??

 

By default the gateway should be the router address (I am assuming that is the internet connection) unless you are utilising a transparent proxy but given your question I would think not.

 

Domain name is dependent on how your setting up the rest of the network, are you setting it up on a domain controller or not?

 

honestly I would utilise the DHCP service on the server, it is will give you more flexibility long term

 

Hi @ShadoePeo,

 

The only reason DHCP is being managed by the router instead of the server is because i have a small office and the server is nor turned on 24x7. To save electric bill i only turn on the server when i need. So this was why i have put DHCP to be managed by the router.

 

I was afraid that with the server turn off, i could not connect clients and friends compyters when they come on to my office with the server turned off. Or its possible and i should have DHCP managed and working on the server instead of having it on the router?

 

Please advise me.

 

Thanks

Share this post


Link to post
Share on other sites
jmwills

Leave DHCP on the router for the exact reason you explained.

Share this post


Link to post
Share on other sites
doliveira

Leave DHCP on the router for the exact reason you explained.

 

Hi jmwills,

 

Just to clarify: 

 

If my server was turned on always 24x7, the best thing is to have the DHCP running on the server. But because my server is not turned on 24x7, i'm firced to have thye DHCP running on the router, correct?

 

Thanks

Share this post


Link to post
Share on other sites
jmwills

Either way, I'd run DHCP on the router.

Share this post


Link to post
Share on other sites
doliveira

Either way, I'd run DHCP on the router.

 

Hi Can you tell me the pros vs cons of having the DHCP running on the router instead of in the server?

 

Thanks

Share this post


Link to post
Share on other sites
jmwills

The only reason DHCP is being managed by the router instead of the server is because i have a small office and the server is nor turned on 24x7. To save electric bill i only turn on the server when i need. So this was why i have put DHCP to be managed by the router.

 

There's your reason for leaving it on the router.  Besides, if you have clients over, the only way for them to connect, if you leave it on the server, would be through a wired connection as the server would have no wireless capabilities.

Share this post


Link to post
Share on other sites
ShadowPeo

The DHCP service on the server is eminantly more configurable than the one on the DHCP server depending on what you are going to do long term, more than 2 DNS servers, Boot options, automatic proxy configuration (WPAD, although this is almost exclusively I.E., WebKit based browsers and Firefox tend to use DNS based AutoProxy) Time Server assignment, multiple search domains, all these are possible with the DHCP service in Windows and it is most likely not able to be done on the router.

 

But if you are going to turn the server off the router is the best option. However you stated above that you were going to run DNS on the server and DHCP on the router, this will cause issues DNS resolution issues unless the server is on, if you are going to do this do it as a secondary at least then you will have an external primary. However if you are utilising internal DNS names through a secondary zone assignment then you may return the wrong DNS resolution if there is an equivalent name somewhere in the wild on the primary (i.e. help.me.com external exists and points to 222.222.222.222 but internally you want it to go to 172.16.1.12 then if you do not use your server as primary the external resolution is likely to be sent through not the internal as the external is primary, using the internal on the server as primary you are going to get delay on DNS resolution when the server is off as the machine will try the primary first, and then falls back to the secondary, yes I know this is a gross simplification)

 

In your case I would be putting the router in as Default gateway (192.168.0.1 in your case) and whatever domain you are utilising for internal resolution in the Default Domain box (as I am assuming this is going to be the "search domain" option in DHCP), or blank if you are not utilising one.

Share this post


Link to post
Share on other sites
doliveira

But if you are going to turn the server off the router is the best option. However you stated above that you were going to run DNS on the server and DHCP on the router, this will cause issues DNS resolution issues unless the server is on, if you are going to do this do it as a secondary at least then you will have an external primary. However if you are utilising internal DNS names through a secondary zone assignment then you may return the wrong DNS resolution if there is an equivalent name somewhere in the wild on the primary (i.e. help.me.com external exists and points to 222.222.222.222 but internally you want it to go to 172.16.1.12 then if you do not use your server as primary the external resolution is likely to be sent through not the internal as the external is primary, using the internal on the server as primary you are going to get delay on DNS resolution when the server is off as the machine will try the primary first, and then falls back to the secondary, yes I know this is a gross simplification)

 

In your case I would be putting the router in as Default gateway (192.168.0.1 in your case) and whatever domain you are utilising for internal resolution in the Default Domain box (as I am assuming this is going to be the "search domain" option in DHCP), or blank if you are not utilising one.

 

Hi ShadowPeo,

 

Thanks for your help and advices. As said before i will have DHCP running on the Router and DNS running on the Server, only because my server is not turned on 24x7.

 

So i will try to use the following settings on my router LAN > DHCP settings:

 

Default Gateway: 192.168.0.1  (this is my router IP)

Default Domain: myoffice.local (this is my windows network domain name)

Primary DNS: 192.168.0.10 (this is my server IP)

Secondary DNS: 192.168.0.1 (this is my router IP)

 

I think that settings up this way, when my server in turned ON all my office computers will use the server as DNS and when the server is turned OFF all the my office computers will use the router as DNS.

 

So what do you guy's think of the settings i listed above?

 

Thanks

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • JROrtiz
      By JROrtiz
      I've been banging my head for a few days now trying to figure this out and I've run out of ideas. Hoping the very intelligent crew here can help me out.
       
      I have a Drobo 5N and a Synology RS816 on my network, both of which have been working without issue for quite some time now. I've always connected to both via Windows Explorer by simply going to the network address i.e., \\N5 and \\SYN (sample names). 
       
      I recently got a new desktop which is where the issues are coming up. When I try to go to \\N5, it results in a message saying it cannot find that location. However, \\SYN works just fine. What's strange is that I can see and manage the Drobo through the Drobo Dashboard software. What could be preventing Windows from seeing the Drobo on the network? 
       
      I've already enabled the SMB 1.x protocol, ensured the workgroup names are the same, rebooted both the machine and the Drobo, made sure network sharing is enabled, and even did a fresh install to ensure that some program I installed didn't cause the issue. Every other machine I have can access the Drobo without issue. It's just this new desktop, and everything is running Windows 10.
       
      Another strange phenomenon that I discovered is that if I go to "\\DROBO" (verbatim, not a sample name) it leads me to the Synology. Where is Windows getting the mapping from that it is directing that address to the Synology?
       
      This is driving me nuts so any advice would be greatly appreciated.
    • Jason
      By Jason
      Have been running a Windows DHCP server on home WSE12R2 box for quite some time behind my Sophos UTM firewall. Also allowed me to seamlessly run Windows Deployment Services at home. WDS just worked.
       
      But if I needed to make a particular LAN IP address exception on the firewall, I had to 1.) create a Windows DHCP server reservations AND 2.) create a network definition for that IP on the Sophos UTM box. 2 steps. Not very efficient; was sure I was doing something incorrectly...
       
      Tried to migrate to Sophos UTM running the DHCP Server, but now WDS doesn't work. LAN devices can no longer PXE boot. Seems possible. Many guides. None have proven especially successful.
       
      Is it possible to run a Windows DHCP server and have Sophos UTM import DHCP reservations instead of maintaining 2 unique entries for each IP reservation (one in Windows DHCP, another on Sophos UTM box)?
       
      What is best practice?
       
       
      Sent from my iPhone using Tapatalk
    • donschmidt
      By donschmidt
      Good morning.  I've just  purchased a home still under construction and plan to have CAT6 installed throughout the living areas. I'm hoping that someone can advise me as to the specific quality/specs of cable that I should use.
      Thanks and Happy New Year.
    • Joe_Miner
      By Joe_Miner
      I've been looking at the Intel Compute Stick BOXSTK1AW32SC and was wondering if anyone here has experience with that and if the Intel AC 7265 built into it is backwardly compatible with older N and A,B wifi?
    • heavy21
      By heavy21
      I want to optimize the performance and security of my home network of servers, PCs, laptops printers, smartphones, TVs, etc.  Current network appliances include layer 2 and 3 switches (Cisco small business) and Linksys router.  I’m looking to replace the Linksys with a security (pfSense) router appliance (w/OpenVPN).  I will also be adding security cameras and a NVR to the network.
       
      The gigabit network is straightforward in structure with all Ethernet connections hanging off the24 port switch connected to the cable modem and router except a cascaded 8 port switch in a room to provide 4 Ethernet connections in a room with only one data port.  Wireless connections presently come off the Linksys but will eventually come off the to-be-purchased security/router appliance with a wireless card.  I don’t see more than 100 devices in total for the whole network.  No VLANS and no sub-netting.  All hardware supports IPv6.
       
      Hardware line up is:
      Dual Zeon server w/RAID 10 of 24 TB of storage, 64GB memory
      Cisco managed switches layer 2 and 3
      HPEX495 server
      Workstations, Desktops, Laptops, Tablets, iPads
      Printers
       
      Software line up is:
      Windows Server Essentials 2012 R2, single domain controller, storage and file server duties
      Windows 10 Pro all non-server Intel computing devices
      PLEX server for streaming audio and video to display units
      Office 365
       
      From what I’ve read so far, it appears that I need to incorporate an IP addressing scheme for clients and servers on the network.  It would also appear that I need to implement VLANS and/or sub-netting to protect access to certain files and security footage, provide guest networking with future consideration for electronic door locks and some sort of server based media distribution to various display devices,
      What are best practices on assigning client and server devices to IP ranges, fixed or dynamic IP addresses?  Do I need to assign clients or servers to IP ranges?  What are the considerations in establishing sub-nets over VLANS or vice versa?  I’m pretty sure I want to restrict access to cameras and their security footage and personal files on my workstation.
       
      Thanks for any resources and advice provided.
       


×
×
  • Create New...