Re: Change DC from multi-homed to single homed segmented
- From: "Terry" <it@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Feb 2007 10:02:13 -0000
Thanks Bill,
I understand now. I will be replacing the current 100MB switches for 1GB
ones so will look into the VLAN option.
Regards
Terry
"Bill Grant" <not.available@online> wrote in message
news:urEV0MtWHHA.4832@xxxxxxxxxxxxxxxxxxxxxxx
You don't need to remove the subnets. What you are proposing would make
no difference to your browsing problems. You are just using different
numbers, but you still have multiple subnets and multiple NICs.
The solution is to use some other device as the router between the
subnets instead of using your DC. DHCP will still work OK if the router
can handle DHCP relay. If you move to a new switch you can probably do it
all with VLANs (ie the switch looks after the routing between subnets).
Once you have a routed network independent of the DC, browsing will
work if you configure all the machines to use WINS. WINS allows the
browser service to operate across a routed network (if the DMB isn't
multihomed). Each segment has its own browse master, and these can be
contacted by the DMB through WINS. The DMB then builds a network-wide
browse list so that all machines are in the browse list and all machines
can see the browse list.
"Terry" <new-grps@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23Z6cLdqWHHA.4188@xxxxxxxxxxxxxxxxxxxxxxx
Hi Bill,
Browser problems is the reason for removing the other subnets. Browsing
is not an issue on the main .1.1 subnet but as you correctly stated, can
be an issue between subnets on a multi-homed DC. However, I would still
like some advice on how to safely remove the other two subnets.
Regards
Terry
"Bill Grant" <not.available@online> wrote in message
news:%23UuSJZgWHHA.2284@xxxxxxxxxxxxxxxxxxxxxxx
If you want to improve browsing, the best thing to do is get the
routing off the DC. A multihomed DC is a major cause of browser
problems. If this is your only DC it automatically becomes the domain
master browser.
"Terry" <it@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23UyhV7ZWHHA.392@xxxxxxxxxxxxxxxxxxxxxxx
I have a Win2K3 DC (the only DC) with three NICS with subnets
192.168.1.1, .2.1 and .3.1.
DHCP enabled on all three.
WINS enabled on .1.1
Server is enabled as a Router.
I would like to segment the .1.1 range across at least two NICS, maybe
three.
Are there any 'gotchas' in reconfiguring the Server? DNS, DHCP, WINS,
Routing.
What could the subnet masks be on the Server and clients?
This is in preparation for moving away from 100MB switches to 1GB
switches and to provide better network browsing between the clients.
Regards
Terry
.
- References:
- Change DC from multi-homed to single homed segmented
- From: Terry
- Re: Change DC from multi-homed to single homed segmented
- From: Bill Grant
- Re: Change DC from multi-homed to single homed segmented
- From: Terry
- Re: Change DC from multi-homed to single homed segmented
- From: Bill Grant
- Change DC from multi-homed to single homed segmented
- Prev by Date: Re: VPN disconnect the internet on the server !!
- Next by Date: Re: unc/dc question.
- Previous by thread: Re: Change DC from multi-homed to single homed segmented
- Next by thread: VPN error 721 with Windows 2003 server
- Index(es):
Relevant Pages
|