Help Me with my Small business network

[jamoor]

So I have my network that I am looking to configure very roughly as the picture.

In this instance should I have the router as the DHCP server or the Windows server? We have 5 users/terminals and 5 Voip phones.

The wireless devices only need internet access, no access to the server or other resources. Is it best to configure the second VLAN as a wireless network and then have signal boosters throughout the building or will it be better to have a second switch, and make a wired network and then plug 2-3 Unifi access points throughout the building?

Thanks for your help.

 

[Armageus]

Given the size of the network then see no issue with DHCP on the router.

With regards to your wireless, then run a second (probably PoE) switch direct from one of the Draytek's LAN ports, VLAN it off (if you definitely need the separation), and then use several access points wired back to the new switch.

 

[blueboy2001]

What are you doing for DNS? If it's the Windows server, do DHCP there for the LAN so it can update the DNS.

Don't use multiple signal boosters, they will cause all sorts of interference. Multiple Unifi AP's will work much better.

 

[jamoor]

What are you doing for DNS? If it's the Windows server, do DHCP there for the LAN so it can update the DNS.

Don't use multiple signal boosters, they will cause all sorts of interference. Multiple Unifi AP's will work much better.

I'm not too sure what to do for DNS as that was one of my questions. I think we are looking at around 20-25 devices that need IP addresses (IP phones, printers etc).

 

[Xez]

It entirely depends on what the Draytek can do really. I don't know Drayteks at all and what they are capable of doing.

If you are having a 'Internet' only wireless network then DHCP without getting overly complicated would be best on the router. A con to this may be that the Draytek may not support additional options for the DHCP scope. Some phones require this option so that they can detect the system and obtains an address. In which case Windows Server DHCP may be the only option for the private network.

I know on Cisco routers that these options are available along with VLAN's and ACL's to separate the traffic. I imagine the Draytek has VLAN capability and also ACL's to stop the routing of the VLAN from the Internet only to the private network. If everything is VLAN'd off though then there is no reason why you cannot have DHCP for the Internet VLAN on the router and DHCP on the Windows server for the private network.

 

[jamoor]

It entirely depends on what the Draytek can do really. I don't know Drayteks at all and what they are capable of doing.

If you are having a 'Internet' only wireless network then DHCP without getting overly complicated would be best on the router. A con to this may be that the Draytek may not support additional options for the DHCP scope. Some phones require this option so that they can detect the system and obtains an address. In which case Windows Server DHCP may be the only option for the private network.

I know on Cisco routers that these options are available along with VLAN's and ACL's to separate the traffic. I imagine the Draytek has VLAN capability and also ACL's to stop the routing of the VLAN from the Internet only to the private network. If everything is VLAN'd off though then there is no reason why you cannot have DHCP for the Internet VLAN on the router and DHCP on the Windows server for the private network.

From my understanding the Draytek can do all of that.

 

[Little_Crow]

You may need to check what licensing you're on for your Windows Server.

If it's currently Per User Cals then you should be fine. If it's Per Device, keep in mind that if your phones are using a windows box for DHCP/DNS they need to be licensed with a CAL too.

 

[Hellsmk2]

Draytek make decent lower class routers, but I would never consider using them for internal dns or DHCP if you have an active directory domain. Firstly, dns is installed by default on a domain controller, and is far more versatile. Secondly, DHCP from a windows server means you have options to easily migrate it, use split scopes, add secondary DHCP server for redundancy, etc etc.

No brainer really.