VLANs and W2K3

Hello!

In my network more than 10 vlans. Can one server under windows server
2003 be a domain controller, wins and dns server for each vlan?

Will be able server to service more than 10 virtual network adapters?

Qwinto Henrik.

Hi ther
Yes and N

One DC cant be "cover" several domains. There could exist one DNS and one WINS server though in a trusted enviroment(Child domain etc), but I would not recommend it. What happens on a single point of failure(Server with DNS server goes down)?? AD NEED DNS to work!! So spread it out, it does not use any significant bandwidth anyway

I am not sure why you mix DOMAINS and VLAN's anyway
VLAN's are great if u want a spesific port to belong a spesific net (physical), but it have nothing to do with Domains really

U use VLAN to decrease the broadcast traffic, or for any other security issue (Corp A belongs to VLAN 1 and Corp B belongs to VLAN 2 etc...) and you want t
increase the security

If your really, really, really :-) want one server (physical) to hold several domains, install a server OS (I.e 2000/2003) and install VMware GSX server to make 10 virtual machines, each with its own OS, and own Domain

Sincerel
Svein-Petter Johnsen

----- Original Message -----
From: "Svein-P" <(E-Mail Removed)>
Newsgroups: microsoft.public.windows.server.networking
Sent: Wednesday, May 19, 2004 6:36 PM
Subject: RE: VLANs and W2K3


> One DC cant be "cover" several domains. There could exist one DNS and one
WINS server though in a trusted >enviroment(Child domain etc), but I would
not recommend it. What happens on a single point of failure(Server with >DNS
server goes down)?? AD NEED DNS to work!! So spread it out, it does not use
any significant bandwidth >anyway.

I have only one domain "company.domain.com"... This domain are placed in
each VLAN.

> I am not sure why you mix DOMAINS and VLAN's anyway?
> VLAN's are great if u want a spesific port to belong a spesific net
(physical), but it have nothing to do with Domains >really.

> If your really, really, really :-) want one server (physical) to hold
several domains, install a server OS (I.e 2000/2003) >and install VMware GSX
server to make 10 virtual machines, each with its own OS, and own Domain.


I have more than 10 VLANs. I can not put a physical server (DELL/COMPAQ
etc.) in each VLAN . So I use one server, but it's in all VLANs. Thus, each
VLAN has it's "own" AD, DNS, WINS.

Qwinto Henrik.

Can Windows Server 2003 hold more then 10 VLANs? Is this good?

"Qwinto Henrik" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Can Windows Server 2003 hold more then 10 VLANs? Is this good?

1. Servers don't "hold" VLANs. Nothing "holds" VLANs. VLANs are not "held".

2. Domains have nothing to do with VLANs and VLANs have nothing to do with
Domains.

3. VLANs are just LANs (or subnets). Can a server be multihomed and live in
10 subnets?,...yes. Is it a poor design?....probably.

4. The server should only be in one subnet. Use a Router or Routers to
manage the subnets.

5. Repeating #2,....Domains have nothing to do with VLANs and VLANs have
nothing to do with Domains.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

> 1. Servers don't "hold" VLANs. Nothing "holds" VLANs. VLANs are not
"held".

I had in view of that server has an interfaces in each VLAN...

> 2. Domains have nothing to do with VLANs and VLANs have nothing to do with
> Domains.

I am understand this...

> 3. VLANs are just LANs (or subnets). Can a server be multihomed and live
in
> 10 subnets?,...yes. Is it a poor design?....probably.

10 VLANs == 10 Virtual Network Adapters...

10 IP subnets on 1 Network Adapter != 10 Virtual Network Adapters...

Different server resources are required in each case...

> 4. The server should only be in one subnet. Use a Router or Routers to
> manage the subnets.

There are Windows 9X clients at the network... They are not support
Active Directory (ex. SRV records at the DNS)... So, they are never find
PDC... I am right?

> 5. Repeating #2,....Domains have nothing to do with VLANs and VLANs have
> nothing to do with Domains.

Repeating... I am understand this...

"Qwinto Henrik" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> > 3. VLANs are just LANs (or subnets). Can a server be multihomed and
live
> > in 10 subnets?,...yes. Is it a poor design?....probably.

> 10 VLANs == 10 Virtual Network Adapters...
> 10 IP subnets on 1 Network Adapter != 10 Virtual Network Adapters...
> Different server resources are required in each case...

I know what you did. It is a bad design. Here is a summary of a good design:

10 subnets (or VLANs, it doesn't matter). A Router (or many routers) link
the subnets together. The Server lives in only one subnet. Server
communicates accross the router(s) to the clients on the other side of the
routers.

> > 4. The server should only be in one subnet. Use a Router or Routers to
> > manage the subnets.
>
> There are Windows 9X clients at the network... They are not support
> Active Directory (ex. SRV records at the DNS)... So, they are never find
> PDC... I am right?

No, not right. Win9x machines find the domain controllers via WINS. Also
"Netbios Over TCP/IP" needs to be enabled on the server. It has nothing to
do with Subnets, VLANs, or Active Directory.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

> 10 subnets (or VLANs, it doesn't matter). A Router (or many routers) link
> the subnets together. The Server lives in only one subnet. Server
> communicates accross the router(s) to the clients on the other side of the
> routers.

And how about DNS/WINS/DHCP? Also in one VLAN? Or, possible, do the
DNS/WINS/DHCP to be visible in all VLANs?

> No, not right. Win9x machines find the domain controllers via WINS. Also
> "Netbios Over TCP/IP" needs to be enabled on the server. It has nothing
to
> do with Subnets, VLANs, or Active Directory.

I don't know about this...

Thank You a lot!!!

"Qwinto Henrik" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> > 10 subnets (or VLANs, it doesn't matter). A Router (or many routers)
link
> > the subnets together. The Server lives in only one subnet. Server
> > communicates accross the router(s) to the clients on the other side of
the
> > routers.
>
> And how about DNS/WINS/DHCP? Also in one VLAN? Or, possible, do the
> DNS/WINS/DHCP to be visible in all VLANs?

All of our "main servers" exist in the primary (first) subnet (VLAN). The
only servers that are in the same VLAN with the client machines are
specialized department servers that only those people in those VLAN require.
Our "main servers" consist of 2 DNS, 2 WINS, 2 Domain Contollers, 1 Exchange
Server, 1 Norton Antivirus Server, 1 Spam Filter/SMTP Relay, 1 ISA Server, 1
Proxy2. The DNS/WINS/DC combination is all on one box, so those are simply
2 identical machines running the DNS/WINS/DC combination.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

> All of our "main servers" exist in the primary (first) subnet (VLAN). The
> only servers that are in the same VLAN with the client machines are
> specialized department servers that only those people in those VLAN
require.
> Our "main servers" consist of 2 DNS, 2 WINS, 2 Domain Contollers, 1
Exchange
> Server, 1 Norton Antivirus Server, 1 Spam Filter/SMTP Relay, 1 ISA Server,
1
> Proxy2. The DNS/WINS/DC combination is all on one box, so those are
simply
> 2 identical machines running the DNS/WINS/DC combination.

Thank You...

And two last questions...

1. Did You recommend setup file service on DC/DNS/WINS server or I must
do it on the separate server?

2. How about stability? Any crashes, bugs, problems with Your servers
and OSes?