New VLAN on Network

Hello all,
Okay this is from a newbie on VLANs.
We currently have a client that has this situation going on.
There are two seperate entities to their network and it is all under a class C subnet (let's say they are using 192.168.241.x).  It is one flat network and we are completely running out of IP addresses.  Our master DC is
We were going to set this up as a class B network but one monkey wrench was thrown into the mix.  They have a PACS system and in order to change the IP address on it the PACS technician was going to charge about $5,000 to do this (that includes flying up here to fix this, motel, etc.) and they would not give us the steps to do it.
So our next idea is to have one entity on its own VLAN.
Both entities are on the same Active Diirectory domain and both entities access files on the same servers.  
We have switches in place that can handle VLANs and are looking at doing 192.168.242.x for the separate entity.  Our question is how do we get the servers to recognize the new VLAN and have the PCs hook into the domain?
Any step-by-step answers or pointing in the right direction would be great.
We will not be able to start this until Tuesday, April 5th.
Who is Participating?
This is not at all a very complex scenario. What you need to do is, keep your existing infrastructure intact.  All the changes need to be done in your switches/routers.

1) In your switches there will already be vlan1 under which 192.168.241.x falls.
2) create vlan2 whose ip address would be 192.168.242.x or anything you chose.
3) You have to configure the ports in the switches to respective vlans.
4) All existing live ports should be under vlan1.
5) Any new user/server should be under vlan2 (192.168.242.x)
6) Configure routing in your switches/routers to route the vlans.

So zest is, you don't touch 192.168.241.x Ip range, only configure vlan2 in the switches for now and see if you can ping 192.168.242.x ip from a desktop. Once it's done, just keep adding the ports and allocate new ip's to all new requirements.

First of all you need to find out if the switch you have is a Layer 3 switch that is whether it will support routing. If you only have a Layer 2 switch then you will have to purchase a router to route traffic between the two networks. Depending on the what kind of router you use (Cisco, Adtran etc) there are several articles you can find by gooling router-on-stick configuration or even call the vendor for support for a nomial fee and they can help you with the configuration.
Just wanted to add a comment. If the current switch you have is Layer 3 Capabale, then you do not need a router and do the routing in the switch itself. Please provide details of your switch.
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

chillepodAuthor Commented:
Okay, I think I understand.
Yes the switches are all layer 3 switches.
The separate entity has its own switch in its own closet.  IT connects to the main switch via fiber into a fiber transceiver in the main switch.  Hopefully we can configure the fiber transceiver as a VLAN.
Again about the servers and PCs.  Since the servers are being used by 192.168.241.x, when we make one of the PCs on the separate entity 192.168.242.x, how will it see the servers?  Is there something I have to do on the server side or a route statement that I have to do on the PC side or does the VLAN part of the switch take care of it?
Do I put in the IP address of the VLAN switch in as the gateway?
Thank you all.
if any of your PC is, the gateway would be vlan2 Ip in the switch-

The gateway Ip for your PC using the .242.10 Ip address would be

So when request comes from .242.10 PC towards 241.100 server, the request goes to default gateway of 242.1 and then the L3 switch does routing and it reaches 241.1.

Similar is the case when your server 241.100 wants to reach 242.10. Request comes to default gateway Ip of 241.1 (vlan1 Ip) and then gets routed to 242.X IP.

So as you can see, all you need to do is vlan config and routing config in the swicthes. No need to touch any PC or any server or tochange any IP.

Makes sense?

chillepodAuthor Commented:
This is what I was looking for.  Hopefully all will work correctly.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.