2
Probleme beim NTP einrichten, zweiter W2K3 Server in Domain
Guten Tag !
Habe in einer Domain 2 W2K3 Server.
1. Server: 15.10.1.1, Domain-Controller. Hier einen extrenen NTP-Server eingetragen, synchronisation funktioniert.
2. Server: 15.10.1.2. Dieser Server soll sich jetzt seine Zeit vom 10.15.1.1 holen.
NTP mit diesem Befehl eingestellt:
NET TIME \\localhost /setsntp:10.15.1.1
Hab jetzt hier im Ereignis-Protokoll Fehlermelungen, daß der NTP-Server nicht erreichbar wäre.
Der Befehl w32tm /resync gibt eine Erfolgsmeldung zurück, leider wird die Uhrzeit nicht richtig gesetzt.
Wo liegt mein Fehler ?
Vielen Dank für die Hilfe.
Gruß
Martin
Habe in einer Domain 2 W2K3 Server.
1. Server: 15.10.1.1, Domain-Controller. Hier einen extrenen NTP-Server eingetragen, synchronisation funktioniert.
2. Server: 15.10.1.2. Dieser Server soll sich jetzt seine Zeit vom 10.15.1.1 holen.
NTP mit diesem Befehl eingestellt:
NET TIME \\localhost /setsntp:10.15.1.1
Hab jetzt hier im Ereignis-Protokoll Fehlermelungen, daß der NTP-Server nicht erreichbar wäre.
Der Befehl w32tm /resync gibt eine Erfolgsmeldung zurück, leider wird die Uhrzeit nicht richtig gesetzt.
Wo liegt mein Fehler ?
Vielen Dank für die Hilfe.
Gruß
Martin
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 73059
Url: https://administrator.de/contentid/73059
Ausgedruckt am: 25.11.2024 um 15:11 Uhr
2 Kommentare
Neuester Kommentar
net time /setsntp:name_erster_server
net time /set
geTuemII
net time /set
geTuemII
How to configure an authoritative time server in Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;816042
Ausszüge:
INTRODUCTION
Windows includes W32Time, the Time Service tool that is required by the Kerberos authentication protocol. The purpose of the Windows Time service is to make sure that all computers that are running Microsoft Windows 2000 or later versions in an organization use a common time.
To guarantee appropriate common time usage, the Windows Time service uses a hierarchical relationship that controls authority, and the Windows Time service does not permit loops. By default, Windows-based computers use the following hierarchy:
• All client desktop computers nominate the authenticating domain controller as their in-bound time partner.
• All member servers follow the same process that client desktop computers follow.
• All domain controllers in a domain nominate the primary domain controller (PDC) operations master as their in-bound time partner.
• All PDC operations masters follow the hierarchy of domains in the selection of their in-bound time partner.
In this hierarchy, the PDC operations master at the root of the forest becomes authoritative for the organization. We highly recommend that you configure the authoritative time server to gather the time from a hardware source. When you configure the authoritative time server to sync with an Internet time source, there is no authentication. We also recommend that you reduce your time correction settings for your servers and stand-alone clients. These recommendations provide more accuracy and security to your domain.
http://support.microsoft.com/default.aspx?scid=kb;en-us;816042
Ausszüge:
INTRODUCTION
Windows includes W32Time, the Time Service tool that is required by the Kerberos authentication protocol. The purpose of the Windows Time service is to make sure that all computers that are running Microsoft Windows 2000 or later versions in an organization use a common time.
To guarantee appropriate common time usage, the Windows Time service uses a hierarchical relationship that controls authority, and the Windows Time service does not permit loops. By default, Windows-based computers use the following hierarchy:
• All client desktop computers nominate the authenticating domain controller as their in-bound time partner.
• All member servers follow the same process that client desktop computers follow.
• All domain controllers in a domain nominate the primary domain controller (PDC) operations master as their in-bound time partner.
• All PDC operations masters follow the hierarchy of domains in the selection of their in-bound time partner.
In this hierarchy, the PDC operations master at the root of the forest becomes authoritative for the organization. We highly recommend that you configure the authoritative time server to gather the time from a hardware source. When you configure the authoritative time server to sync with an Internet time source, there is no authentication. We also recommend that you reduce your time correction settings for your servers and stand-alone clients. These recommendations provide more accuracy and security to your domain.
