Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
hi all, i am attempting to build a win2k3 server standard edition. the server is for one of our remote sites.
i have got the operating system installed on the machine with any device drivers, but i am not sure what order to start the setup in.
i want to make the server a domain controller.
i wasnt sure if i am first meant to add the server to the domain using DHCP to obtain an ip address, or do i just have the server a member of workgroup and carry the setup that way and configure DNS, DHCP and active directoy.
i would really appreciate any advice provided.
thanks in advance
#1. No server should get its IP address via DHCP. That's just a bad idea in general.
#2. When it comes to domain controllers, that generally bad idea is 1000x worse. Can't say this any other way but, DON'T DO THAT! If you need to temporarily to patch the system, etc. that's ok. But it should have a static IP by the time you dcpromo the machine, or set it up as a DNS server, etc.
#3. Do you have Active Directory in place already?
"Milk was a bad choice!"
0 
hi thanks for the above. i havent got active direcory in place yet, thats where i am a bit confused really.
basically what i have done so far is setup the dhcp server, but have not tested as yet, and also have made a few settings to the routing and remote access section. i wasnt quite too sure when and how to get active direcotry comes into action.
where i am getting confused is that the new server will be on a zone where the ip range is 192.168.3.1 to q19.168.3.255. the lan with the primary domain controller is on 192.168.2.1 to 192.168.2.255.
every time i give the new win2k3 server a static ip address of 192.168.3.1, i am unable to access the main network.
0
Lots of good reading/help at MS technet site. Look up the subjects and read the docs. That's how everyone else does it.
Give a person a fish you feed them for a day.
Ask a person to internet search and they learn a skill for a lifetime.
0
hi, have the books and website open, just wanted to know which order to do things in, the rest of the nitty gritty stuff can probably work out.
0
Are you connected into a network that has that address scheme at the present time? Translation: is it plugged into the 192.168.2.X network, and you set the IP address to 192.168.3.X network, it doesn't work?
That's basic TCP/IP why it's not working.
"Milk was a bad choice!"
0
yep the server is plugged in to the 192.168.2.x. i joined the domain without a static ip address which i was able to do so. i want the new server to have the static ip address of 192.168.3.1 and for the dhcp scope to be 192.168.3.1 to 192.168.3.255.
so at what point do i configure the server with a static ip address?
0
LOL, dude, you can't promote it until it has a static IP address, and it's plugged into the network where it will work at the basic TCP/IP level.
"Milk was a bad choice!"
0
ok then, next dumb question (you can see this is the first time setting up a server) how do you get the domain to recognise that the static ip address assigned to the new server is part of the domain?
0
First, you assign it an IP in the range of your subnet. In this case something like 192.168.2.1 (assuming it's not in use). Once you've established that it's communicating on the network and with your present DC (DNS server) then you can begin the promotion. Remember, you can always change it's IP (statically) to the 192.168.3.x range AFTER it's been promoted.
There are considerations to keep in mind. Since the remote site is on a different subnet, in order for the new DC to be able to contact the existing DC, your routing had better be squared away and working before you attempt to deploy your new DC in the new location.
My turn for a dumb question.
You obviously don't have a clear understanding of what you're doing or the basic concepts involved.......so why are you doing it?
You should give serious consideration to hiring a qualified professional. It will save you grief, time, and money in the long run.
0
"Remember, you can always change it's IP (statically) to the 192.168.3.x range AFTER it's been promoted."
Dunno if I'd do that. If DNS doesn't update properly, that could get really messy for a newb to clean up.
"Milk was a bad choice!"
0
True enough.
What about using AD Sites and Services? Create the remote site and it's subnet. Join the server to that site/subnet at the main location, then perform the install and dcpromo. This way it would have the correct IP address and if all else is setup correctly between physical locations, you should be able to just plug it in at the remote site and fire it up.
0
If AD replication bandwidth consumption is a concern, there is a way to DCPromo and use a backup of AD, then sync only the changes since the time of the backup. Could look into that.
"Milk was a bad choice!"
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
