<div>
Not exactly sure what your question is. A firewall or even a simple network router can be used to segment the third network from the others with no issues, yet still provide Internet access. Just be sure to use a different network address range.
</div>


<div>
Ok, in the mean time I did figure the following out.<br />
1. yes, no access to the switches therefore must use LAN port on SonicWALL.<br />
2. Configured LAN2 on SonicWALL to have a network address of 192.168.150.1 and bridged same to LAN1, 192.168.148.1.<br />
Used a switch (netGEAR 8 port Gig switch) in the closet to connect a pc to the NetGEAR then to LAN2 on the SonicWALL. &nbsp;<br />
then took the patch panel port (e.g. 21) in the same closet and instead of going thru the existing VoIP switches patched patch panel port 21 into an open port on the NetGEAR. &nbsp;<br />
3. &nbsp;Yes at this point I have a Server (Windows 2012) and a workstation Win 8.1 Pro) on a their own network. <br />
<br />
here is the problem. &nbsp; I am trying to install configure Hyper V on the server I set up in it's own domain and forest. &nbsp;I need the PC to get DHCP from the server. &nbsp;the server IP is 192.168.150.3 the PC is static 192.168.150.2 and the GW is 192.168.150.1. &nbsp;I am thinking that if I turn on the DHCP server on Win 2012R2 that it will be throwing out IP's on the same physical lan that all the pc's are on and if they come up for an IP lease renewal, &nbsp;the 192.168.150.1 network could throw out an IP and they could catch it. &nbsp; <br />
THIS plus I can't at the moment join the newly created domain. &nbsp; <br />
e.g. &nbsp;aone.local is the domain, in it's own forest. &nbsp; While I can ping the server e.g. &nbsp;fatalbert and get a reply 192.168.150.3 &nbsp;I still can't join my existing test pc to it. &nbsp;It' says it can't be reached.
</div>


<div>
Ok, that's what I have done now. &nbsp;So the final part is this. &nbsp;The Server 2012R2 will be a DHCP server, the other two networks get their DHCP from their respective SonicWALL. &nbsp;Can I have the DHCP server on the Servr 2012R2 give out DHCP without the possibility of other two networks catching a lease?
</div>


<div>
Hi there,<br />
<br />
Extremely sorry but a bit jumbled in understanding your requirement.<br />
LAN 1: 192.168.148.0/24<br />
<br />
i)<br />
<i>Used a switch (netGEAR 8 port Gig switch) in the closet to connect a pc to the NetGEAR then to LAN2 on the SonicWALL. &nbsp;<br />
then took the patch panel port (e.g. 21) in the same closet and instead of going thru the existing VoIP switches patched patch panel port 21 into an open port on the NetGEAR. &nbsp;<br />
</i><br />
<br />
Could you please post a basic connectivity diagram?<br />
Also kindly confirm the reason behind having LAN1 and LAN2 in BRIDGED MODE.<br />
<br />
ii)<br />
<b><i> I need the PC to get DHCP from the server</i></b>. &nbsp;the server IP is 192.168.150.3 <i><b>the PC is static 192.168.150.2 </b></i>and the GW is 192.168.150.1. &lt;Contradictory ideas&gt;<br />
<br />
iii)<br />
&nbsp;I am thinking that if I turn on the DHCP server on Win 2012R2 that it will be throwing out IP's on the same physical lan that all the pc's are on and if they come up for an IP lease renewal, &nbsp;the 192.168.150.1 network could throw out an IP and they could catch it. &nbsp;&lt;Not sure what this means&gt;<br />
<br />
**************************<wbr />**********<wbr />**********<wbr />**********<wbr />*
</div>


<div>
Abandoned question, selected best answers
</div>


<div>
<div class="content wysiwyg-content">
We have two networks in one physical location.<br />
Each of them has their own firewall, own cable modem (ISP), but they share a phone system.<br />
There are two managed Netgear switches that we do not have access to.<br />
What we'd like to do is create a 3rd network for testing. &nbsp; There will be 1 Windows 2012 Svr R2, and 2 or 3 workstations.<br />
Each of the other two networks has available Public Static IP's with one each being assigned to their respective firewalls. &nbsp;<br />
I know that I can't bring on an Active Directory Server in the same forest, but what if i make it, it's own forest?<br />
Any suggestions on how to accomplish this would be helpful.<br />
We could potentially install a 3rd firewall and have it route traffic out one of the two cable modem in the building.
</div>
</div>


We have two networks in one physical location.
Each of them has their own firewall, own cable modem (ISP), but they share a phone system.
There are two managed Netgear switches that we do not have access to.
What we'd like to do is create a 3rd network for testing.   There will be 1 Windows 2012 Svr R2, and 2 or 3 workstations.
Each of the other two networks has available Public Static IP's with one each being assigned to their respective firewalls.  
I know that I can't bring on an Active Directory Server in the same forest, but what if i make it, it's own forest?
Any suggestions on how to accomplish this would be helpful.
We could potentially install a 3rd firewall and have it route traffic out one of the two cable modem in the building.

Configuring Multiple Networks

Network design and methodology, also known as network architecture, is the design of a communication network. It is a framework for the specification of a network's physical components and their functional organization and configuration, its operational principles and procedures, as well as data formats used in its operation. In telecommunication, the specification of a network architecture may also include a detailed description of products and services delivered via a communications network, as well as detailed rate and billing structures under which services are compensated.

Network Architecture

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.

Network Operations

Network Management involves issues that are independent of specific hardware or software, including email policies, upgrade planning, backup scheduling and working with managed service providers for Desktop-As-A-Service (DaaS), Software-As-A-Service (SaaS) and the like through the use of tools, coupled with manufacturer standards, best practice guidelines, policies and procedures plus all other relevant documentation. Network management also includes monitoring, alerting and reporting, management reporting, planning for device or service updates, the backup of configurations, the setting of key performance indicators and measures (KPIs/KPMs), associated service level agreements and problem records as part of the IT Service Management (ITSM) framework.

Network Management

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.