<div>
Thanks, the first article you posted was particularly useful...
</div>


Thanks, the first article you posted was particularly useful...

<div>
<div class="content wysiwyg-content">
Hi there<br />
<br />
Currently, our network is flat and unmanaged. We have a bunch of Netgear switches across 4 floors.<br />
<br />
We're planning to upgrade to Cisco 2960's and a 3550 for L3 switching. 3 VLAN's will be created; VLAN1 (192.168.1.0/24) for desktops/laptops, VLAN2 for guests (192.168.2.0/24) which will be isolated from the rest of the network, and VLAN3 for the servers (192.168.3.0/24).<br />
<br />
The 3550 will provide routing between VLAN1 and VLAN3. My question is, how will DNS and DHCP work here? Will the DHCP server in VLAN3 be able to provide addresses that aren't local to its own subnet (i.e will it be able to lease addresses in the 192.168.1.0/24 range, when it itself is in the 192.168.3.0/24 subnet). Same with DNS...will it be able to register addresses in another subnet even though there is a route to it?<br />
<br />
Has anyone implemented this sort of system before? I'm worried that if we do segment the network to this, then even domain logon traffic can be affected.<br />
<br />
Thanks &nbsp;
</div>
</div>


Hi there

Currently, our network is flat and unmanaged. We have a bunch of Netgear switches across 4 floors.

We're planning to upgrade to Cisco 2960's and a 3550 for L3 switching. 3 VLAN's will be created; VLAN1 (192.168.1.0/24) for desktops/laptops, VLAN2 for guests (192.168.2.0/24) which will be isolated from the rest of the network, and VLAN3 for the servers (192.168.3.0/24).

The 3550 will provide routing between VLAN1 and VLAN3. My question is, how will DNS and DHCP work here? Will the DHCP server in VLAN3 be able to provide addresses that aren't local to its own subnet (i.e will it be able to lease addresses in the 192.168.1.0/24 range, when it itself is in the 192.168.3.0/24 subnet). Same with DNS...will it be able to register addresses in another subnet even though there is a route to it?

Has anyone implemented this sort of system before? I'm worried that if we do segment the network to this, then even domain logon traffic can be affected.

Thanks  

MS Server comms crossing VLAN's?

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.