Set up network windows server 2003 tutorial

February 24, 2011 at 08:25:41
Specs: Windows server 2003 R2
Hello,

I'll start by introducing myself, my name is eques (on this site anyway) and i'm a webdev.
But my interest are lying more and more within Network security/setup/Active directory/ ... .
So in my spare time, i"ve decided i want too learn more and more about this.

I am looking for a book/tutorial/video that helps me setting up a network at home with windows server 2003. (i only have 2 laptops and one desktop (that will be running the server), and yes i know it's overkill, this is just to train/learn/excercise.

I've installed VMWare and on there i"ve installed a windows 2003 R2 standard version.
I've installed a DHCP and an Active directory. But i don't know how i connect computes (in my case the 2 laptops (both running W7)) on it. So that's what i'm looking for, something that will explain to me how that will work.

I hope my explanation ist't to elaborated, if it is i'm sorry.

Have a nice day and thanks in advance if you can help me


See More: Set up network windows server 2003 tutorial

Report •


#1
February 24, 2011 at 11:58:28
You have to prompt your server to a Domain Controller. Go to the command prompt and run DCPROMO. This will create a domain. Then you can join your laptops to the domain.

Report •

#2
February 25, 2011 at 13:42:38
hmm ok, i'll have a look at dcpromo then, but what i don't get is who to decide what IP you give your domain? can one choose it at random?

Report •

#3
February 25, 2011 at 14:46:49
Umm....before you go any further get some help because if you don't do this right you can mess things up and if you don't understand how simple TCP/IP works you will have problems.

Report •

Related Solutions

#4
February 25, 2011 at 15:04:41
well i don't realy have someone to ask so that's why i'm here :) to ask for some advice on a good book/video/tutorial whatever :) (thanks for the reply's btw)

Report •

#5
February 26, 2011 at 01:16:57
I would recommend this book as an excellent introduction to Windows 2003 server. As for IP addresses for your domain, just use one of the non-routable ranges (e.g. 192.168.1.x - whichever network your router is set up for).

Report •

#6
February 26, 2011 at 13:29:16
well i have the book and have read about 75 pages so far. Some parts are a bit too advanced but ok. It's my understanding that to be able to add computers to ur domain you need a DHCP to give away IP's to connect to. Further you can use AD to maintain them, if not you can use the "computer manager" for that (if the network is rather small). So only thing now is to get a grasp of the whole IP thing, that's kinda unclear for now. I have a desktop and in there i'm runnig VMware with the server on. The DNS is set on ip 192.168.0.1 but when i ping to it from without the VMware (so on the desktop) it times out. If i ping on 127.0.0.1 it sends something back.


Configurations for Your First Server
Static IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Preferred DNS server: 192.168.0.1
DHCP installed successfully.
This server has been successfully set up as a domain controller.
Install Active Directory and DNS
Full domain name: test.local
NetBIOS domain name: test
DNS installed successfully.
DNS-server: 127.0.0.1


So still got a lot of reading to do i suppose :) SO much to do and so little spare time :(


Report •

#7
February 26, 2011 at 23:59:36
If you haven't already done so, configure the network adapter in the VM to use Bridged mode. Running your server and DHCP in a VM is not really ideal, but will work if your clients are also VMs.

Your main computer (the one you are running the VMs on) can't be a client as the server needs to be running before the clients log on - a chicken and egg situation.


Report •

#8
February 27, 2011 at 05:49:57
So what you are saying is that if i want to add a client onto that domain, the client needs to be runned on a VMware machine aswel?

Report •

#9
February 27, 2011 at 07:08:50
No. You could use your laptops as a clients. But you will have to turn off DHCP on your router and assign a fixed IP address to the computer that the VMs are running on. You can only have one DHCP server on the network (that's not strictly true, but it simplifies things) and your main computer can't get it's address from the VM. Also you'll need to set a fixed IP address for the server in the VM (it can't assign an address to itself). Make sure that your router is on the same subnet as you assign for the server and your main computer.

Sorry if I gave the wrong impression previously. But you may wish to experiement with a VM client first. That way if you mess anything up it doesn't matter and, by taking snapshots before making any changes, you can easily restore server and/or client to a previous configuration.


Report •


Ask Question