Re: Network Design

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

60 users?

It is very likely that the below setup is overkill, assuming the 60 users are not streaming video all the time, but are regular office users.

I would not split up the network in subnets if at all avoidable, there's no reason I can think of that is worth the extra hassle in this situation.

Without spending too much money I would do the following, keeping some level of scalability in mind.

1. two decent brand managable 48 port 100 Mbit switches for the users, you might want to consider vlanning depending on user activity.

2. A decent brand (juniper, cisco) router to the internet

3. Gigabit switch for the SAN backbone, assuming you are using iSCSI. Otherwise FC.

4. Internal IP scheme, something less obvious in the 172 or 10 range (for example 10.46.8.x) this will give you 254 ip addresses. (not 10.0.0.0 please... if you ever try to connect other LAN's you'll find that they will have done this; forcing you to renumber) You may want to consider using a B class to allow for scalability.

For a small setup like this the KISS principle applies.... Keep It Simple. The admins will thank you for it.

/ ) Regards,
/ /_________
_|__|__) Paul Weterings
/ (O_) http://www.servercare.nl
__/ (O_)
____(O_)


buf1 wrote:
Curious on best practice for network design of a relatively small network of 60 users, 5 printers, 3 servers, one storage arrray, one firewall to the internet...

I'm wondering if I split up into 2 subnets just to break it up a bit.

I'm thinking two switches for the SAN that connects to servers on the backend.

Then two switches (1 for each subnet) that would connect to all servers Then 2 user switches that would connect users in each sub net..

Is it over kill?? Or am I on the right track.. It's building a network from scratch..

What is best practice for private internal IP address scheme..

Thanks.


.

Relevant Pages

  • Re: NLB causing switch flooding
    ... Is there an easy setup guide for creating the vlan....my understanding is that these should be on their own dedicated switch?? ... If we put a NIC on each TS into a VLAN and enable NLB how do we get this to talk to the Session Directory Services on the PDC? ... Also how will this affect the data traffic to the other servers and the clients trying to connect to the TS Servers. ... The problems we are getting is that as soon as we initiate the NLB we start to get a HUGE amount of activity on the switches often leading to them locking up. ...
    (microsoft.public.windows.server.clustering)
  • Re: Problem with internal DNS
    ... Remember - you need an 'unsullied' private DNS for your AD to run ... Internet domains you want to ... Changing to my ISPs name servers, on the SBS box it is still adding ... What I have done is delete the DNS entry on SBS sever and setup the ...
    (microsoft.public.windows.server.sbs)
  • Re: network hangup
    ... servers which i had to fault find by other means so cannot rule out the ... some of the switches hang and not the same ones every time. ... ip's i need are reinstated i don't get network hangup (i need to be ... How to Configure OEx for Internet News ...
    (microsoft.public.windows.server.networking)
  • automated test query fails
    ... I have three servers on an internal network setup with DNS. ... is supposed to be setup as secondary DNS for the internet. ...
    (microsoft.public.windows.server.dns)
  • Re: automated test query fails
    ... > I have three servers on an internal network setup with DNS. ... > is supposed to be setup as secondary DNS for the internet. ...
    (microsoft.public.windows.server.dns)