PRELIMINARY Well
going to work now with the installation of a small Windows 2003 network that will have a domain controller (DC) with its Active Directory service, a DNS server, a WINS server and a DHCP Server.
is important to note that the Domain Controller (DC) is a computer server that centralizes control of resources within a domain and to locate all the resources that are within that domain, the Domain Controller (DC) used turn a domain name service, or DNS server, this is how the resources located within its scope.
If within the domain are Windows versions older stations work, then you must also add the installation of a NETBIOS name service called WINS server. Both
DNS server as the WINS server have the sole mission only to locate the required resources that are within the domain. It is important to install this server because Windows 2003 uses both locators to locate resources.
And the infrastructure is complete, we will also install a DHCP server, which we know is a dynamic IP server that delivers all the resources they use TCP / IP. So liberate us from the tedious work of configuring and assigning static IP.
the DHCP server is responsible everything related to allocations and control of IP numbers is the best in a network.
Now the domain controller computer, manage a database where they are fully identified domain resources and also manage another database where are the policies that each resource has.
whole system is known as the Active Directory or Active Directory and these two databases are physically in the Domain Controller (DC).
But as we bounded in a previous blog a company can have multiple domains and each domain would imply that whenever a domain controller in front but his backup domain controller, which in summary would two domain controllers per domain.
is important to note that few teams to size precisare servers to be fully installed with my Active Directory
For this project we will consider installing all the servers on one machine or equipment.
This is for purposes of deployments and installations in this blog, but more appropriate is to have the domain controller on one machine only and other infrastructure servers such as WINS, DNS and DHCP on the other respectively.
also must weigh the risks to security, for which the domain controller must have other equipment and support equipment, thus increasing the percentage of high disponnibilidad while considerations regarding safety equipment such as firewalls, intrusion preventers, antivirus, etc. etc. for the moment not take into account.
In a real situation is important and if Dimesion theoretically possible to simulate in advance the burden of each server to know how many teams would be required, just suffice it to say that the domain controller by itself drives a heavy traffic within the internal network , as the number of resources in its domain increases.
traffic measurements of domain controller, they should consider their own internal traffics performing authentication workstations at all times when they need to enter their accounts, with this we must add, trafficking in updating the database that the domain controller performs the secondary domain controller, it is important this because in case of an incident in the main controller, we would only have to keep working the secondary controller, but useless if your database has not updated the resources of our network, which tuned every time it is carried out and at what times, is its own art of network management, well and all this must be added also the product itself traffic backups own maintenance required that should be done, all this would come has to be total internal traffic generated by the domain controller and this would have to add the traffic characteristic of the applications used in application servers (if present) and external traffic or is done outside the company network.
This is very important when designing the corporate internal communications networks, taking into account these parameters in order to have sufficient clearance on our internal network and for many decades considering future changes, is right because otherwise it would slow our only reality.
After these considerations we start with our:
PLAN WORK
Previous Work
Server (SRV)
1.-Set the computer name that will make DC + DNS + DHCP + WINS
2.-Check network connectivity and
3.-Set fixed IP network card driver domain
Workstations (WKS)
1.-Set the name of the workstation WKS
2.-Configure to support dynamic IP network card (NIC )
FACILITIES 1. -Install a DHCP server
2. -Install a DNS server
3 .- Install a WINS server
4 .-Instalar Controlador de Dominio (DC)
INSTALACION SERVIDOR DHCP
Nos dirigimos al asistente de Configuración de Servidor, entrando por el menú Inicio y ubicando luego Herramientas de Administración; una vez alli lo ejecutamos y este asistente de servidor realizará una comprobacion básica automática de verificación de si estamos conectados a una red y de si tenemos una tarjeta de red puesta y de si esta tarjeta de red tiene ya colocado una dirección IP fija.
Es importante acotar aqui que todos los servidores deben tener una IP fija asignada obligadamente pudiendo ser esta IP privada o IP pública pero que sea fija. Only workstations are the only ones to have dynamic IP.
Once you have verified that we meet these basic requirements, the system will give us access to a menu of server roles. This menu
server role that has Windows 2003 Server, we will select the DHCP Server role, which will give you a check for installation.
In the DHCP server, we have to enter the new field settings
Here is the name we have chosen to call this new field
We choose or select the range of addresses that will distribute this area
Here we set the total range of addresses, even considering that exclude after.
same to consider the network mask, which is very important defined.
Here we set the range of excluded addresses these excluded addresses are reserved addresses for routers equipment, safety equipment or any equipment owned by the Windows 2003 network infrastructure server
In this part we take the time to assign dynamic IP addresses can be days, hours or minutes. That depends on our security policy really.
gives us the option to set our gateways, if you had to define if we leave it blank.
Here we are setting the option of our DNS servers, if they already exist if you do not leave blank.
Then we went to set the addresses off of your WINS server if it already exists if not leave blank and we give below.
Finally we are turning the area to begin to deliver dynamic IP addresses to computers within the defined.
So far, we have configured the DHCP server, which will begin functioning immediately .
If a DHCP server will configure a domain controller and installed previously, then we should do an extra step, which would be the domain of activity within the respective domain controller.
This is for safety standards.
If
this activity will this view, DHCP Server administrator, and not actually work.
When activated, you have a view as in the picture below.
To turn, we are in this position where our mouse pointing to DHCP Server, your name, there we click the right mouse button and we'll be out a drop down menu.
in the pulldown menu select this option, which will allow us to execute and activate the DHCP server
like Vermeer when enabled the DHCP server, it turns green.
The final steps will be apparent in the workstations if DHCP server is working, for which one has to check if giving directions dynamic IP addresses.
A further step will check if this meeting time to the tickets assigned IP address.
In the next part we will make the configuration of a domain controller
0 comments:
Post a Comment