Link to home
Create AccountLog in
Avatar of Marc Chevalier
Marc ChevalierFlag for United States of America

asked on

Best way to wire our new network equipment, and what type of cables to use?

Hello, I am not trained in networking but I have to install our new network equipment.  

We currently have Comcast Business Class cable modem internet service.  We have purchased a Sonicwall NSA 220W device and 2 Cicso SG102-24-NA 24-port switches.  To add to this, we have a Synology DSW213+ NAS device used for centralized file storage.  I have planned to connect the Sonicwall NSA 220W WAN port to the Comcast modem LAN port with a straight ethernet patch cord.  Then connect one of the Sonicwall LAN ports to the first port of Cisco 24-port switch with a straight Ethernet patch cord.  Then connect the first Cisco switch from one of it's ports to the first port of the second Cisco switch with another straight Ethernet patch cord.  Then lastly I'm not sure where I should connect the Synology NAS?  To one of the switches or directly to the Sonicwall?  I am asking for the correct/best way to connect these devices and the correct type of Ethernet cable to use?  The Sonicwall or Comcast modem will be providing DHCP with a Sonicwall IP of 192.168.1.1 as the Gateway and providing a range of 192.168.1.2 thru 192.168.1.254.  Thanks for your help!
ASKER CERTIFIED SOLUTION
Avatar of tolinrome
tolinrome
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Marc Chevalier

ASKER

Thanks tolinrome, the Cisco switches we have are unmanaged and I don't think I can setup DHCP on them?  At least I don't know how to do that?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
thats right, I just checked. I would put it on the sonicwall then. Do you really need such a large range for the IP's though? Usually most network admins conserve the first 20 or so IP's for static devices such as other switches, printers, etc, things like this so they have a dedicated IP address. So you can make your scope from .30-.254 or something similar.
I do not need that large of a range. Will that help the speed of the network if I cut it in half, which I can easily do. We have a max of 40 devices connecting to the network.
I would agree with tolinrome and even say leave 50 available unless you plan to use a 192.168.2.--- option
It wont do anything to help with the speed of the network by cutting down your DHCP scope range. Keep in mind apart from laptops and desktops that if people are going to be using their smartphones to connect one day to a wireless device router you may setup in the future you'll need IP's from the DHCP scope to serve those as well.

But for now if you have a max of 40 devices and leave some room for growth, you can still have a range from .100 to .254 for DHCP and that gives you plenty of IP addresses. You can always rearrange the scope in the future.
Is this network a workgroup or a Windows domain? If it's the latter, common best practice (at least for a network of the size you describe) is to let the Windows server provide the network services.

If it's just a workgroup or you're using a flavour of Linux, then I'd use the Sonicwall to provide DHCP, DNS, etc. The Comcast could provide these services, but the router has a more spare grunt available for doing so, and its firewall is designed to keep external and internal networks apart except for permitted and controlled traffic.

I second (third?) tolinrome's recommendation to connect the NAS to a switch rather than the firewall; if external access is needed to the Synology unit it will ordinarily be more occasional and the firewall can easily be configured to permit such access, but as tolinrome says, it's pointless to have LAN traffic traversing more hops than necessary.