Subnetting

hello

managing network reached capacity on dhcp scope. network has 3 servers ( domain controller, telecommunications server , sql server) have reserved ip. understand option increase scope configure additional subnet , looking advice.

the network experiences high traffic result of voip and frequently performance of network drastically hindered . result of adding additional subnet additional router needed , if how should connected? correct me if wrong but configuring second subnet mask of 255.255.254.0 give me 254 addresses ranging 192.168.1.1 192.168.1.254 more substantial network. 

the client machines access servers whenever dialing (which time), need in primary subnet servers?

would else required subnet?

would subnet increase performance if there secondary router preventing bottleneck?

thank you

rob

hi rob,

in general, businesses invest in business-class switches , routers capable of adding subnet, in form of new vlan. so, i'd surprised if needed router - or hardware matter.

i'm not quite sure mean dialling, i'm going put aside moment. if can shed light on that, might better able comment on facet.

one point make that network has become saturated. know case, or end-user perception? reason ask time voip established, 2 things happen:

• a dedicated voip vlan configured, and/or
• quality of services (qos) rules established.

if neither of these has happened, can impact traffic when spikes occur nothing - not voice, server or client data, gets kind of guaranteed service levels. might wise take @ protocol traffic report see if there's inefficient broadcast-style protocols helping saturate the networking , if are, evaluating whether or not they're needed.

if network saturated , neither of these have been done, should network , telephony engineer's first port of call. if 1 or both exist you can in circumstances benefit breaking current subnet multiple smaller subnets (i.e. campus-wide lan broken per building arrangement), that's quite unusual see in practice unless original structure had been planned poorly , needs fixed. reality time happens practical thing invest in faster networking equipment (i.e. going 100mbps 1gbps equipment).

anyhow, moving along, you've got slight error example subnet mask of 255.255.254.0 insofar give you 510 addresses, not 254. class c subnet mask of 255.255.255.0 give 254 mentioned.

before make dhcp changes, relevant question ask whether or not current lan range boxed in other already-issued lan ranges.

for example, if current lan range 192.168.1.0/24, boxed un 192.168.0.0/24 on 1 side , 192.168.2.0/24 on other. if it's not, consider expanding dhcp range have, making sure adjust exclusion range(s) required. approach require network engineer adjust switch , routers configurations, along server engineer adjust subnet mask on servers , printers etc, going required degree no matter how situation handled.

as you've mentioned, other approach add class c range, in case, workload on network administrator little lighter they'll have create new vlan on each of switches (unless it's core stack), configure appropriate routing rules on switches , routers, , finally, configure new vlan relay dhcp requests ip address of existing dhcp server.

either approach fine - it's entirely crew figure out works.

once that's done, can create new dhcp scope, specify relevant options, activate , you'll , running. really, easiest part of whole process quite big margin, however, won't work @ if above isn't done correctly.

cheers,
lain

Windows Server  >  Windows Server General Forum