And today's poser is ....

Q57. When you are viewing the status of Active Directory replication between two domain controllers, the following messages may be displayed for the result of the last replication attempt:

The RPC server is unavailable.

or

The RPC server is too busy to complete this operation.

These error messages may be reported in the Event log through Active Directory Replication Monitor (Replmon.exe) from the Windows 2000 Support Tools, or Repadmin.exe from the Windows 2000 Support Tools.

How can you resolve this error message? (Choose all that apply)

A. Use the net time command to synchronize the time with the computer that holds the Primary Domain Controller (PDC) Operations Master role.

B. Apply Service Pack 2 or later for Windows 2000.

C. Change the Real Properties Clock to the correct time.

D. Use the W32tm.exe tool that is included with Windows 2000 to determine if a time server is explicitly configured for the local computer and if synchronizations against that host are not working.

Good Luck .... see you tomorrow for the answer!!

__________________
One Exam leads to another! Where will it ever end?

Report this post to a moderator

I'm guessing on this one: A & D

Report this post to a moderator

I'm going with A,B,D

__________________
A+, Net+, MCP 70-210

Report this post to a moderator

quote:

---

Originally posted by wbafrank
And today's poser is ....

Q57. When you are viewing the status of Active Directory replication between two domain controllers, the following messages may be displayed for the result of the last replication attempt:

The RPC server is unavailable.

or

The RPC server is too busy to complete this operation.

These error messages may be reported in the Event log through Active Directory Replication Monitor (Replmon.exe) from the Windows 2000 Support Tools, or Repadmin.exe from the Windows 2000 Support Tools.

How can you resolve this error message? (Choose all that apply)

A. Use the net time command to synchronize the time with the computer that holds the Primary Domain Controller (PDC) Operations Master role.
B. Apply Service Pack 2 or later for Windows 2000.
C. Change the Real Properties Clock to the correct time.
D. Use the W32tm.exe tool that is included with Windows 2000 to determine if a time server is explicitly configured for the local computer and if synchronizations against that host are not working.

Good Luck .... see you tomorrow for the answer!!

---

And the Answer is ....

Correct Answers: A, B and D

CAUSE
By default, Windows 2000-based computers synchronize time as described in the following Microsoft Knowledge Base article:

Q216734 How to Configure an Authoritative Time Server in Windows 2000

However, this behavior can be overridden by specifying a time server as described in the article.

If the time server is not available and the time difference between domain controllers drifts beyond the skew allowed by Kerberos, authentication between the two domain controllers may not succeed and the RPC error messages can result.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, please see the following article in the Microsoft Knowledge Base:

Q260910 How to Obtain the Latest Windows 2000 Service Pack

One method of synchronizing time amongst domain controllers is to use the net time command to synchronize the time with the computer that holds the Primary Domain Controller (PDC) Operatons Master role. To do this, use the following command:

net time \\ mypdc /set /y

This command instructs the local computer to synchronize its time with the server named Mypdc . The /set option specifies that the time not only be queried, but synchronized with the specified server. The /y switch skips the confirmation for changing the time on the local computer.

Another method is to use the W32tm.exe tool that is included with Windows 2000 to determine if a time server is explicitly configured for the local computer and if synchronizations against that host are not working. At a command prompt on the server displaying the error messages, type the following command:

w32tm.exe -v

In the following sample output, a time server named MYTIMESERVER has been configured, but it is unreachable by the local computer:

W32Time: BEGIN:GetSocketForSynch
W32Time: NTP: ntpptrs[0] - MYTIMESERVER
W32Time: rgbNTPServer MYTIMESERVER
W32Time: NTP: gethostbyname failed
W32Time: Port Pinging to - 123
W32Time: NTP: connect failed
W32Time: END:Line 1147

This article also fixes an incorrect calculation in the round trip which under certain conditions causes W32TIME and W32TM to potentially set the system time about 65 seconds ahead of real time.

STATUS

The time service does not record an event in the Event log when the Windows Time service is configured to synchronize time against a specific host and that host is not available. This problem was first corrected in Windows 2000 Service Pack 2.

__________________
One Exam leads to another! Where will it ever end?

Report this post to a moderator

__________________
A+, Net+, MCP 70-210

Report this post to a moderator