11 replies
by cg it
by cg it
by makeitso
by lordinfidel
FYI-
2K DC's with 2 nics can and will produce unwanted and strange results.
It is not reccomended that 2k DC's have 2 nic's installed. Otherwise known as Multihomed.
My reccomendation would be to remove the 2nd nic.
Make the DC's address available for the LAN only.
Create another server, do not make it a DC, it will be there simply for routing purposes. (unless the dlink has more then 1 port, then you can just cascade a hub/switch off of it)
The new server will have 2 nics in it. One conneceted directly to the dlink router, using a IP that can talk to it.
The other nic will be for the internal lan, connected to, what I hope you have, a hub/switch.
It's address will be that of the local lan, not of the rtr lan. They need to be 2 different ntwks.
Next, install RRAS with NAT and allow the RRAS server to give out dhcp address'.
You may also need to set DNS server address' also.
The clients will obviusly need to be set with dhcp.
by makeitso
by cg it
by lordinfidel
Like I said before...
A 2k Domain Controller with 2 nics in it *will* produce unwanted results.
Other small orgs who attempt to do the same thing encounter the same problem.
In this case, I would get a multi-port dsl router and a hub. Havethe multi-port router dial-up to your dsl provider, and attach a hub to it. Then attach the rest of your nodes to the hub.
Configure the dsl router to hand out dhcp OR statically assign IP address to the client systems.
I know it's not an answer that you want, But you can not get around this one if you have set up Active Directory on a 2k server.
AD DC's CAN NOT be multihomed!
by makeitso
by makeitso
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending