Fluid_Imagery
asked on
How to seperate a server from rest of network
So my setup is as follows:
Cable Modem goes to a Freedom9 Freeguard100 UTM Firewall
Lan Port 1 on Firewall goes to Dell Managed 24 Port switch (switch1) and is a 192.168.1.x network
DMZ port of firewall goes to another Dell Managed 24 port (switch2) and is a 192.168.2.x network
192.168.1.x can see the 192.168.2.x network but 192.168.2.x cant see the 192.168.1.x, and the 192.168.1.x is work servers and work machines, where 192.168.2.x is the client machines and client nas server
192.168.1.x has its own DHCP server (Domain Controller)
192.168.2.x has its DHCP through the NAS Server (win2k3 box).
What I have now is a ESX Server just running so that I can mess around with different OS and not have to build and take down a machine. What I want to do is have this ESX server be able to be accessed from the 192.168.1.x side but not interfere with the current networking.
When I loaded ESX and loaded the first guest O/S (SBS2003), it through a warning during setup about having a current DHCP server loaded. So I want to find a way to separate the ESX server from the rest of the 192.168.1.x network so that if i load another DHCP server it wont affect the current servers.
How can I go about doing this? Both switches are managed but currently aren't in managed mode.
I want the ESX server to be able to browse the internet but stay separate from the other equipment while still being able to be accessed from my work desktop and stuff.
Thanks,
Fluid Imagery
Cable Modem goes to a Freedom9 Freeguard100 UTM Firewall
Lan Port 1 on Firewall goes to Dell Managed 24 Port switch (switch1) and is a 192.168.1.x network
DMZ port of firewall goes to another Dell Managed 24 port (switch2) and is a 192.168.2.x network
192.168.1.x can see the 192.168.2.x network but 192.168.2.x cant see the 192.168.1.x, and the 192.168.1.x is work servers and work machines, where 192.168.2.x is the client machines and client nas server
192.168.1.x has its own DHCP server (Domain Controller)
192.168.2.x has its DHCP through the NAS Server (win2k3 box).
What I have now is a ESX Server just running so that I can mess around with different OS and not have to build and take down a machine. What I want to do is have this ESX server be able to be accessed from the 192.168.1.x side but not interfere with the current networking.
When I loaded ESX and loaded the first guest O/S (SBS2003), it through a warning during setup about having a current DHCP server loaded. So I want to find a way to separate the ESX server from the rest of the 192.168.1.x network so that if i load another DHCP server it wont affect the current servers.
How can I go about doing this? Both switches are managed but currently aren't in managed mode.
I want the ESX server to be able to browse the internet but stay separate from the other equipment while still being able to be accessed from my work desktop and stuff.
Thanks,
Fluid Imagery
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Those switches may be able to do VLANs sounds like what you're after, but "Dell Managed 24 Port switch" is a bit vague to be sure as Dell sell lots of different switches. If you can look it up from the part number and see if it supports VLANS you should look into that.