2003 and VLANs

Hi,

I am trying to implement a solution where one physical network is shared by
two distinct networks. This would not be too bad but for their wanting to
have one server and the internet access shared between the two networks.

I have a switch capable of understanding VLAN ID's etc and I can put each
port into one or more VLANs. The question I have is 2003 server capable of
understanding and using the VLAN ID's for the two networks? Will I need two
NIC's each set for one of the VLANs (see
http://msdn.microsoft.com/library/de...700db1.xml.asp)
or can I use the one NIC with two IP addresses as it is now.

I have a router that is routing from one network to the other.


The reason for all this is because the customer needs to run DHCP on both
networks and this is the only way I can think of that will allow us to use
one network and provide the correct IP info as needed without risk.


Any thoughts would be greatly appreciated.

Chris

VLANs require a LAN Router between them just as if they were two physical
networks,...there is no difference.

The Server has nothing to do with it and would simply stay on the segment
that it is already on with the Nic it already has with the address it
already has. The same is true of the "Internet Sharing Device". The only
extra thing that needs done on the Internet Sharing Device is to give it a
Static Route that tells it to use the LAN Router as the "gateway" for the
"other" VLAN segment.

All hosts (every single one) will use the LAN Router as the Default Gateway.
Then the LAN Router will use the Internet Device as *its* Default Gateway.
The Server is treated just like any other machine on the network and is
irrelavant to the structure of the VLANs.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------



"Chris Gradden" <(E-Mail Removed)> wrote in message
news:56CDF253-FD4B-4BC3-8A0B-(E-Mail Removed)...
> Hi,
>
> I am trying to implement a solution where one physical network is shared
by
> two distinct networks. This would not be too bad but for their wanting to
> have one server and the internet access shared between the two networks.
>
> I have a switch capable of understanding VLAN ID's etc and I can put each
> port into one or more VLANs. The question I have is 2003 server capable
of
> understanding and using the VLAN ID's for the two networks? Will I need
two
> NIC's each set for one of the VLANs (see
>
http://msdn.microsoft.com/library/de...700db1.xml.asp)
> or can I use the one NIC with two IP addresses as it is now.
>
> I have a router that is routing from one network to the other.
>
>
> The reason for all this is because the customer needs to run DHCP on both
> networks and this is the only way I can think of that will allow us to use
> one network and provide the correct IP info as needed without risk.
>
>
> Any thoughts would be greatly appreciated.
>
> Chris

You can use a NIC that supports 802.1q. The server can then be in multiple
networks with one physical NIC. Your switch will have to support it as well.
Google it for more info.


"Chris Gradden" <(E-Mail Removed)> wrote in message
news:56CDF253-FD4B-4BC3-8A0B-(E-Mail Removed)...
> Hi,
>
> I am trying to implement a solution where one physical network is shared
by
> two distinct networks. This would not be too bad but for their wanting to
> have one server and the internet access shared between the two networks.
>
> I have a switch capable of understanding VLAN ID's etc and I can put each
> port into one or more VLANs. The question I have is 2003 server capable
of
> understanding and using the VLAN ID's for the two networks? Will I need
two
> NIC's each set for one of the VLANs (see
>
http://msdn.microsoft.com/library/de...700db1.xml.asp)
> or can I use the one NIC with two IP addresses as it is now.
>
> I have a router that is routing from one network to the other.
>
>
> The reason for all this is because the customer needs to run DHCP on both
> networks and this is the only way I can think of that will allow us to use
> one network and provide the correct IP info as needed without risk.
>
>
> Any thoughts would be greatly appreciated.
>
> Chris