|
|
|
| Hello,
I am trying to set up a small network for my home lab as I am working towards the MCSE.
2 PC
1 xp
1 w2k server
I am trying to install active directory, but I am getting stuck in the dns bit...
I keep getting the error no connection reached or something similar..
so
how to install the dns server ?
how to install AD?
cheers | |
| cm2gj 2002-12-06, 12:55 am |
| AD is the directory services for a domain on windows 2000.
on your win2k server you need a NTFS partition in order to install AD.
for partition convertion use the following syntaxis:
convert c: /fs:ntfs
when c is your partition you want to convert.
to create a AD, you only need to run DCPROMO from the RUN box.....
the AD needs DNS, so the DNS is installed togheter and configured with AD.......
good luck and keep posted. | |
|
| first you need to install your AD and later testing it before add workstations to the domain..... | |
| hairy51 2002-12-06, 12:10 pm |
| When you run DCPROMO, it will ask you if you want to install DNS, select yes, and you should be away.. | |
|
| quote:
Originally posted by hairy51
When you run DCPROMO, it will ask you if you want to install DNS, select yes, and you should be away..
exactly.
ad can`t live without a dns.
on the ad wizard if the dns is not installed and configured, the ad wizard prompt for installation and on this way you can install and configure dns service togheter with ad.
ad needs dns... | |
| thecomeons 2002-12-06, 1:57 pm |
|  | |
|
| I have been trying to install ad and the dns but I must be doing something wrong, when i say yes to do you want to install the dns ... i keep getting the msg cannot reach network... or something similar.
thanks for your help. | |
|
| quote:
Originally posted by Perdu
I have been trying to install ad and the dns but I must be doing something wrong, when i say yes to do you want to install the dns ... i keep getting the msg cannot reach network... or something similar.
thanks for your help.
give us a step by step and say us where is the problemmmm | |
| anthonie 2002-12-10, 3:22 am |
| The server needs to be connected to a network. If you don't have a network cable plugged in, it won't let you install AD. | |
|
| quote:
Originally posted by anthonie
The server needs to be connected to a network. If you don't have a network cable plugged in, it won't let you install AD.
you donīt need to have a network for installation of a AD service.
Only a NIC with static information configured. no any other client or workstation is needed for AD installation. | |
| adam salam 2002-12-10, 5:01 am |
| quote:
Originally posted by cm2gj
Only a NIC with static information configured. no any other client or workstation is needed for AD installation.
Perdu, didn't mention any thing about assigning an IP adderess for the server, should be.
the other issue why you are using an XP client when your are studing MCSE w2k | |
| cm2gj 2002-12-10, 12:04 pm |
| quote:
Originally posted by adam salam
[B]
the other issue why you are using an XP client when your are studing MCSE w2k
actually you can use Xp clients to test win2k domain enviroments.
exam 70210 apply for mcse like the xp exam (70270)
and Xp pro is similar than 2k pro | |
|
|
| anthonie 2002-12-11, 3:06 am |
| quote:
Originally posted by cm2gj
you donīt need to have a network for installation of a AD service.
Only a NIC with static information configured. no any other client or workstation is needed for AD installation.
I've just tried to install AD again on a machine with a NIC with static IP assigned and network cable unplugged. As I expected, didn't work. Then I plugged the network cable to the hub and tried again. As I expected, successfully installed.
Well, maybe it's just me and my machines. Good luck to you! | |
|
| quote:
Originally posted by anthonie
I've just tried to install AD again on a machine with a NIC with static IP assigned and network cable unplugged. As I expected, didn't work. Then I plugged the network cable to the hub and tried again. As I expected, successfully installed.
Well, maybe it's just me and my machines. Good luck to you!
maybe you are right.
i never try to install a win2k Domain without cables connected to the network.
my next tested implementations must be tested first with cables unplugged.
thanks for the tip. | |
|
| quote:
Originally posted by anthonie
I've just tried to install AD again on a machine with a NIC with static IP assigned and network cable unplugged. As I expected, didn't work. Then I plugged the network cable to the hub and tried again. As I expected, successfully installed.
Well, maybe it's just me and my machines. Good luck to you!
i remember i install win2k on my vaio laptop without network connection..... mmmmmm ... i must test again........ | |
|
| quote:
Originally posted by adam salam
do you mean what you are saying, that's good news 
so I can hit two birds with one stone.
if it's the Q's why not getting XP pro certification also
you can make the mcse win2k and replace the 70210 pro exam with the 70270 xp exam. iīm pretty sure this is real. i ask microsoft directly and see a lot of articles about that. and add to this, the testing center CTEC MCTs confirm me this. and i have the complete list of exams requirements for mcse and all the path allowed and say very clearly: 210 or 270 is counted as only one exam. | |
| deltree 2002-12-11, 1:29 pm |
| I installed AD on my win2k server as a stand alone system. | |
|
| This was recently a project in our MOC class that I am taking. In the lab the first thing that you must do is install DNS then dcpromo. It worked well with us. | |
|
| Just a side note. If your server is connected to the internet via cable or DSL, and your ISP uses DHCP, DNS won't work very well (or not at all). DNS needs a static address to function properly. If you plan to truly use the server for DNS, with internet access for the client machines and the server, than I suggest the following:
Buy an inexpensive cable/DSL router, and through it's managment interface (http://"router's IP"), reconfigure it to use an IP structure that is secure from the internet for enhanced security (example 10.x.x.x). Now configure the router to assign a "Fixxed Mapping" (static IP) to your server (done through the servers MAC address). You can now configure the server to use the static address that you configured on the router, while still allowing the client devices to obtain their address through DHCP. Configure the client PC's to use DHCP, but point the DNS portion of the TCP/IP properties towards your newly created DNS server. Add the ISP's DNS server as a secondary. | |
| cm2gj 2002-12-17, 12:26 am |
| quote:
Originally posted by ccaya
This was recently a project in our MOC class that I am taking. In the lab the first thing that you must do is install DNS then dcpromo. It worked well with us.
this is good.
after dcpromo finish and restart, you must check event viewer and srv records!! this is super important!!!!!!.......
if you run dcpromo and donīt have dns installed or configured, the active directory wizard make all that for you! | |
| cm2gj 2002-12-17, 12:29 am |
| quote:
Originally posted by jayb1
Just a side note. If your server is connected to the internet via cable or DSL, and your ISP uses DHCP, DNS won't work very well (or not at all). DNS needs a static address to function properly. If you plan to truly use the server for DNS, with internet access for the client machines and the server, than I suggest the following:
Buy an inexpensive cable/DSL router, and through it's managment interface (http://"router's IP"), reconfigure it to use an IP structure that is secure from the internet for enhanced security (example 10.x.x.x). Now configure the router to assign a "Fixxed Mapping" (static IP) to your server (done through the servers MAC address). You can now configure the server to use the static address that you configured on the router, while still allowing the client devices to obtain their address through DHCP. Configure the client PC's to use DHCP, but point the DNS portion of the TCP/IP properties towards your newly created DNS server. Add the ISP's DNS server as a secondary.
actually if your isp provide dinamic ip configuration to your connection, this donīt affect your dns configuration locally.
this assignament is only for the modem interface.
the dns ip configuration required on your dns server is the nic interface, not the dial interface.
the best practice here is using a private subnet (i.e: 192.168.1.x), provide a static ip address to the dns server (i.e: 192.168.1.3) and configure the ISP dns as a forwarder on your local DNS.
actually is a BAD practice to use the DNS of your ISP as name resolution for your domain. your local clients needs in their tcp/ip configuration the local dns server address, donīt need the isp dns. |
|
|
|