Shulou(Shulou.com)06/02 Report--

Experimental requirements:

1. Set up a DNS server

Install DNS on server1

Create a forward lookup zone for DNS

Create the main area

Build a reverse lookup area first

Create a primary lookup area

Fill in the ip address of the host

Let's start creating a "host" for the forward lookup zone

two。 Install the first DC on server1

Fill in the DNS domain name 18

View AD's sites and services

Ping www.ms.com on server1

Users of the 3.Workgroup environment join to the domain environment

Start installing distributed file sharing (DFS) now

1. Create the DFS root directory

Build the root directory first

Root directory name

two。 Create a DFS link

3. Configure replication

Sharing on Server2

4. Modify replication topology and set replication schedule

5. Create a DFS root target

Now start building extra domain controllers on top of server4

6. Murray-revised-now starts to create the DFS root directory on Server1

7. Check DFS status

8. Access resources within the DFS

Lab Environment-DFS in Domain Environment

Preparation for building DFS:

The premise of the experiment is to build a domain controller, and then join all the servers in the workgroup group to the domain environment. Here I will demonstrate the construction process of the domain controller in detail.

1. Build a DNS server (this is a prerequisite for building a domain controller in a Windows server 2003 environment)

two。 Set up a domain controller

3 join member servers to the domain

1. Set up a DNS server

Before building, server1, server2 and server3 can communicate with each other on ping.

The DNS of server2 and server3 points to the ip address of server1, and the ip address of server1 points to itself.

All three servers are in the workgroup group environment

Server1 Network connection details

Server2 Network connection details

Server3 Network connection details

Enter "sysocmgr\ i:sysoc.inf" in the run

Start to enter the installation wizard

Skip back to the home page of the installation wizard and notice that the "network service" is automatically checked.

Insert a mirror of windows server2003 and suspend

Patch file when installing DNS

DNS service installation completed

Create a forward lookup zone for DNS

Enter "dnsmgmt.msc" in the run to open the DNS server management console page

Now create a new zone in the forward lookup area

Create the main area

Creation of forward lookup area completed

Next, create a reverse lookup zone

Build a reverse lookup area first

Create a primary lookup area

Fill in the ip address of the host

Reverse lookup area created

Let's start creating a "host" for the forward lookup zone

"www" is the host of DNS. The complete host name is: www.ms.com,DNS domain name: ms.com.

This is the server's own "host". "server1" is the host, "server1.ms.com" is the host name, and "ms.com" is the domain name.

Let's start to build the first root DC (the domain controller of the first active directory)

&. First of all, check whether your DNS points to yourself, this step is very important!

&. Be sure to fill in the suffix of the main DNS of this host!

two。 Install the first DC on server1

Type "dcpromo" in the run, and finally start to install the DC server.

Fill in the DNS domain name

Note: the restore password of the domain here is set to: ms@123, note that this password must be memorized, otherwise it will be very painful. Especially when restoring the AD database, remember not to divulge this password. I just filled in one for the demo.

Let's go to the AD installation wizard. You need to wait about 2-3 minutes here! Be patient and wait!

Installation of the first DC is complete

After the installation of the first DC is complete, you must restart the server before some configurations will take effect. You will have to wait about 4-5 minutes here. Be a little more patient.

View domain users and groups for AD

Enter "dsa.msc" in the run

View AD's sites and services

Ping www.ms.com on server1

Ping www.ms.com on server3

Users of the 3.Workgroup environment join to the domain environment

Server2 joins the domain environment

The user name and password of the DC account must be entered to allow joining to the domain environment, so the domain administrator of DC must be authorized here.

OK,workgroup users have finally successfully joined the domain environment.

Now you have to restart to take effect.

You need to wait a few minutes here, and you must log in in domain environment mode when logging in here.

This is the user desktop interface in the domain environment.

The procedure for joining Server3 to a domain environment is the same as that of server2, so I'll skip it here. Check the copmputers in DC

1. Create the DFS root directory

Step 1: select "start"-- > "Administrative tools"-> "distributed File system"-- > as shown in the figure, right-click "distributed File system"-> "New Root Directory"

Build the root directory first

Select "Domain Root" here

Here we choose server1.

Root directory name

The location and name of the shared folder

The picture after completion

two。 Create a DFS link

Browse

I found that there is no shared folder pictures in server2 and server3 here, so I have to create a shared folder pictures for server2 on disk C and a pictures on server3.

As shown in the figure: the shared folder of pictures created under server2 is also created like this in server3.

Files shared on the pictures shared folder on server2

You can browse it now.

The status is now found as follows:

The step now is to map the Link pictures to another target\ server3\ pictures, and select New destination as shown in the figure above

Now I will not configure replication for the time being, so I choose "No" here.

The current state is as follows

3. Configure replication

I choose "Ring" for the replication topology. If you want to change the replication topology in the future, you only need to use the "pictures property".

Sharing on Server2

4. Modify replication topology and set replication schedule

Next we can select the replicated topology by changing Custom.

As shown below, you can choose the replication topology you want.

With the following plan, we can determine when to replicate the topology

If we ask for replication to be allowed between 0: 00 a.m. and 4: 00 a.m., the time setting is as follows:

There were no shared resources on server3 just now, but there are now.

5. Create a DFS root target

Domain DFS can copy the DFS root to other servers by creating a new DFS root target to provide fault tolerance

As shown in the following figure, right-click DFS root directory-> "New Root Target"

Note: when you select the master server here, the server level here is at least the domain controller level, otherwise you will not be able to add it successfully. The following is a typical example of creation failure. I have also tried to use other members to join the domain to create a DFS, and then other members to create a DFS root directory, and found the failure, so this is not a problem with my operation, but a prerequisite restriction here. So you need to try more experiments like this. Since AD has five domain functional levels, why not try one by one?

Found that still can not solve the problem, the reason may be that I am a workstation mode computer, OK, I will now create a secondary domain controller to see if there is still a gap, to see if there will be an error.

Now add server4 to DC.

Now start building extra domain controllers on top of server4

Enter the DC administrator account

Enter the restore password-this password must be well managed by the DC administrator and should not be leaked casually, because it is very important to restore the restore mode in the future!

Let's go to the installation wizard for the extra domain controller, where you need to wait 2-3 minutes.

After the extra domain controller is installed, the server must be restarted

6. Murray-revised-now starts to create the DFS root directory on Server1

7. Check DFS status

If you want to check the status of DFS roots, links, and targets, just right-click them-> "check status" in the distributed file system window, and the screen will use colors and graphics to display the results of the check. If you check the DFS root directory or link, then:

& the green check box indicates that the root directory or link itself is fine, and the target it is mapped to is normal.

The exclamation point of & × × indicates that there is nothing wrong with the root directory or the link itself, but not all the targets it maps to are normal (for example, disabled or inaccessible)

& the red X symbol indicates that there is a problem with the root directory or the link itself

& if you check the DFS root directory or the target to which the link is mapped, then:

The green check box indicates that there is nothing wrong with the target itself, and "online" is displayed on the status bar.

You can enable or disable the mapping relationship by right-clicking the target-> enable reference or disable reference

& the red X symbol indicates that the target is abnormal, such as offline, and "offline" is displayed on the status bar.

8. Access resources within the DFS

Clients that support DFS can access files located in DFS

Method 1:

Let's use the Windows server 2003 computer to do the exercises. Click start, Windows Explorer, tools, Map Drive, and enter as shown in the following figure, where ms.com is the domain name, root123 is the name of the DFS root directory, and pictures is the link name of DFS

Method 2:

Click to add a network neighbor

After completion, it is shown in the figure:

Method 3:

You can also enter "\ ms.com\ root123\ pictures" in the run

You can also enter "\ server1\ root23" in the run

Method 4:

By command

Method 5:

Find through the network path

Enter:\ ms.com\ root123 in the address bar

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.