Servidor de Hora

En el DC:
Event Error 29:
The time provider NtpClient is configured to acquire time from one or more
time sources, however none of the sources are currently accessible. No
attempt to contact a source will be made for 240 minutes. NtpClient has no
source of accurate time.
Event Warning 47:
Time Provider NtpClient: No valid response has been received from
manually
configured peer slug.ctv.es after 8 attempts to contact it. This peer will
be
discarded as a time source and NtpClient will attempt to discover a new
peer
with this DNS name.
Lo mismo en un servidor de:
- 1 Servidor TrendMicro

- 1 Servidor SQL

- 1 Servidor Righfax

- 1 Servidor Mailsweeper & Fsecure

- 1 Servidor ISA Server y Websense

- 1 Servidor Blackberry

- 1 Servidor Altiris

- 1 Controlador Dominio

- 1 Global Catalog

- 1 Servidor MS Exchange & OWA

- Servidor ISS Server Protect


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

"Javier Inglés [MS MVP]" wrote:

a ver, qué mensaje te da??

Salu2!!
Javier Inglés
MS MVP, Windows Server-Directory Services





"[[ecdl]]" escribió en el mensaje
news:
> Eso es lo que llevo haciendo mas de un mes..., por eso he venido aqui.
> :(
>
> "Javier Inglés [MS MVP]" wrote:
>
>> mira el error en www.eventid.net
>>
>>
>> Salu2!!
>> Javier Inglés
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>>
>>
>> "[[ecdl]]" escribió en el mensaje
>> news:
>> > Ya, pero no tiene que estar bien ya que generan errores en log de
>> > eventos.
>> >
>> > "Javier Inglés [MS MVP]" wrote:
>> >
>> >> Entonces simplemente no hagas nada.
>> >>
>> >> Por defecto, los servidores y estaciones de trabajo se sincronizan
>> >> entre
>> >> ellos automáticamente con los DCs.
>> >>
>> >>
>> >> Salu2!!
>> >> Javier Inglés
>> >> MS MVP, Windows Server-Directory Services
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "[[ecdl]]" escribió en el mensaje
>> >> news:
>> >> > No quiero que se sincronicen con una hora exterior, creo que se
>> >> > sincronicen
>> >> > con un servidor que tenga poca carga, pero todo en LAN.
>> >> >
>> >> > Salu2
>> >> >
>> >> > "Javier Inglés [MS MVP]" wrote:
>> >> >
>> >> >> Cortesía de Fernando Reyes [MS MVP],
>> >> >>
>> >> >> Tienes que sincronizar tu PDC con una fuente externa de tiempo
>> >> >> (si
>> >> >> tienes
>> >> >> más de un DC, puedes identificar cuál es el que tiene el roll
>> >> >> FSMO
>> >> >> PDC
>> >> >> en
>> >> >> "Usuarios y Equipos de Active Directory" haciendo click derecho
>> >> >> sobre
>> >> >> el
>> >> >> nombre de tu dominio y ejecutando "Maestro de operaciones" en el
>> >> >> menú
>> >> >> emergente). Mira en www.eventid.net el resto de eventos. Te pego
>> >> >> a
>> >> >> continuación una respuesta al respecto de la sincronización de
>> >> >> tiempos
>> >> >> que
>> >> >> posteé en su día:
>> >> >>
>> >> >>
>> >> >>
>> >> >> <auto-pego>
>> >> >>
>> >> >> Los clientes deben sincronizar con los DC's, los DC's con el DC
>> >> >> Raíz y
>> >> >> éste
>> >> >> a su vez con una fuente de tiempo externa.
>> >> >>
>> >> >> Para sincronizar los clientes W2000/XP se ejecuta la instrucción
>> >> >> (puedes
>> >> >> hacer que se ejecute en un script de logon). Si es necesario
>> >> >> hacer
>> >> >> esto
>> >> >> es
>> >> >> porque algo raro hay, pues deberían sincronizar automáticamente
>> >> >> (generlamente es porque se les ha configurado un servidor de
>> >> >> tiempo
>> >> >> externo):
>> >> >>
>> >> >> net time /set /y
>> >> >>
>> >> >> Para sincronizar los clientes w9x:
>> >> >>
>> >> >> net time \ombre_de_DC /set /y
>> >> >>
>> >> >> Para que un equipo sincronice con un servidor de tiempos externo
>> >> >> se
>> >> >> ejecuta
>> >> >> la instrucción:
>> >> >>
>> >> >> net time /setsntp:"Lista de servidores NTP separados por
>> >> >> espacio"
>> >> >>
>> >> >> Para saber con qué servidores externos sincroniza un equipo se
>> >> >> mira
>> >> >> con:
>> >> >>
>> >> >> net time /querysntp
>> >> >>
>> >> >> que nos devuelve la lista de servidores NTP con los que está
>> >> >> configurado
>> >> >> o
>> >> >> nos advierte de que no está configurado para sincronizar con
>> >> >> ningún
>> >> >> servidor
>> >> >> de tiempo.
>> >> >>
>> >> >> Te recomiendo mires este W32Time linkpack. Te comento para qué
>> >> >> es
>> >> >> cada
>> >> >> enlace:
>> >> >>
>> >> >> Su propio nombre lo dice:
>> >> >>
>> >> >> 216734 - Cómo configurar un servidor horario autorizado en
>> >> >> Windows
>> >> >> 2000
>> >> >>
>> >> >> http://support.microsoft.com/defaul...;es;216734
>> >> >>
>> >> >> Esta es una lista de los diferentes servidores de tiempo que hay
>> >> >> por
>> >> >> la
>> >> >> red.
>> >> >> Tambien te explica lo que es un servidor primario, lo que es uno
>> >> >> secundario
>> >> >> y te recomienda la utilización de estos últimos:
>> >> >>
>> >> >> 262680 - A List of the Simple Network Time Protocol Time Servers
>> >> >> That
>> >> >> Are
>> >> >> Available on the Internet
>> >> >> http://support.microsoft.com/defaul...s%3B262680
>> >> >>
>> >> >> Conviene que al menos la primera vez (y tambien de vez en
>> >> >> cuando)
>> >> >> configures
>> >> >> el servicio para que no sólo registre los fracasos de
>> >> >> sicronización
>> >> >> si
>> >> >> no
>> >> >> que tambien registre los aciertos. Es normal que se produzcan
>> >> >> errores
>> >> >> (reiniciando el DC, con una caída de la conexión a Internet,
>> >> >> caída
>> >> >> del
>> >> >> servidor, etc.). Si ves que lo más normal es que sean aciertos
>> >> >> no
>> >> >> te
>> >> >> precupes por ver errores:
>> >> >>
>> >> >> 307937 - Configuring the Time Service to Log When the Time Is
>> >> >> Changed&
>> >> >> http://support.microsoft.com/defaul...07937&
>> >> >>
>> >> >>
>> >> >> Este te dice las diferentes entradas que hay en el registro para
>> >> >> configurar
>> >> >> el servicio W32Time:
>> >> >>
>> >> >> 223184 - Entradas del Registro para el servicio W32Time
>> >> >> http://support.microsoft.com/defaul...;es;223184
>> >> >>
>> >> >> Y ya, como fin de fiesta y por el mismo precio, copio un
>> >> >> linkpack
>> >> >> de
>> >> >> Ignacio
>> >> >> Adasme sobre el servicio W32Time:
>> >> >>
>> >> >>
>> >> >>
>> >> >> <pego>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Comienzo.
>> >> >>
>> >> >> Advancing Time on Production Computers and the Effect on Active
>> >> >> Directory
>> >> >> and FRS
>> >> >> http://support.microsoft.com/?kbid(9668
>> >> >> Basic Operation of the Windows Time Service
>> >> >> http://support.microsoft.com/?kbid"4799
>> >> >> Description of Date and Time Format Standards
>> >> >> http://support.microsoft.com/?kbid$7873
>> >> >> Registry Entries for the W32Time Service
>> >> >> http://support.microsoft.com/?kbid"3184
>> >> >> Using NET TIME for all Workstations and Servers
>> >> >> http://support.microsoft.com/?kbid0944
>> >> >> Using TIMESERV to Set and Synchronize Time
>> >> >> http://support.microsoft.com/?kbid#2255
>> >> >> Windows 2000 vs. Windows NT Time Synchronization
>> >> >> http://www.winnetmag.com/Articles/I...?ArticleID„56
>> >> >> Windows Time Synchronization Service
>> >> >> http://www.winnetmag.com/Articles/I...?ArticleIDƒ83
>> >> >> Un Documento muy bueno.
>> >> >> http://www.microsoft.com/windows200...meserv.asp
>> >> >>
>> >> >> Artículos.
>> >> >>
>> >> >> How Machines Determine the Time Source Server Using NET TIME
>> >> >> http://support.microsoft.com/?kbid6460
>> >> >> How to Configure an Authoritative Time Server in Windows 2000
>> >> >> http://support.microsoft.com/?kbid!6734
>> >> >> How to Configure the Short Date Format in Windows and Windows NT
>> >> >> http://support.microsoft.com/?kbid$1671
>> >> >> How to Synchronize the Time on a Windows 2000-Based Computer in
>> >> >> a
>> >> >> Windows
>> >> >> NT
>> >> >> 4.0 Domain
>> >> >> http://support.microsoft.com/?kbid%8059
>> >> >> How Windows Keeps Track of the Date and Time
>> >> >> http://support.microsoft.com/?kbid#2488
>> >> >> Installing the Time Service Resource for Windows Clustering in a
>> >> >> Windows
>> >> >> NT
>> >> >> Domain
>> >> >> http://support.microsoft.com/?kbid'9005
>> >> >> Keeping Time on your Windows NT Network
>> >> >> http://www.microsoft.com/technet/tr...ntp-nt.asp
>> >> >> Mexico City Time Zone Update for Daylight Saving Time
>> >> >> http://support.microsoft.com/?kbid(9502
>> >> >> Obtaining Universal Coordinated Time (UTC) from NTFS Files
>> >> >> http://support.microsoft.com/?kbid8588
>> >> >> Time Synchronization in an NT Network
>> >> >> http://www.winnetmag.com/Articles/I...rticleIDR2
>> >> >> Win32 Time Service Informational, Warning, and Error Messages
>> >> >> http://support.microsoft.com/?kbid#2209
>> >> >> Using NET TIME for all Workstations and Servers
>> >> >> http://support.microsoft.com/?kbid0944
>> >> >>
>> >> >> Troubleshooting.
>> >> >>
>> >> >> Access Violation May Occur in Termsrv.exe When You Are Using
>> >> >> Time-Outs
>> >> >> http://support.microsoft.com/?kbid%6843
>> >> >> Cannot Log On If Time and Date Are Not Synchronized
>> >> >> http://support.microsoft.com/?kbid#2386
>> >> >> Clients May Not Synchronize the System Time Accurately in
>> >> >> Windows
>> >> >> 2000
>> >> >> http://support.microsoft.com/?kbid21290
>> >> >> "Could Not Locate a Time Server" After Setting SNTP Time Server
>> >> >> Using
>> >> >> NET
>> >> >> TIME Command
>> >> >> http://support.microsoft.com/?kbid$3574
>> >> >> Daylight Saving Time Option Is Not Retained While Installing
>> >> >> Windows
>> >> >> 2000
>> >> >> http://support.microsoft.com/?kbid#5417
>> >> >> Internet Time Feature Is Not Available When a Computer Is a
>> >> >> Domain
>> >> >> Member
>> >> >> http://support.microsoft.com/?kbid(9689
>> >> >> Logon Time Restrictions Prevent Users on Windows NT 4.0 from
>> >> >> Remotely
>> >> >> Accessing Windows 2000 Resources
>> >> >> http://support.microsoft.com/?kbid&3006
>> >> >> RPC Error Messages Returned for Active Directory Replication
>> >> >> When
>> >> >> Time
>> >> >> Is
>> >> >> Out of Synchronization
>> >> >> http://support.microsoft.com/?kbid%7187
>> >> >> SetLocalTime/GetLocalTime Not the Same if Adjusting for Daylight
>> >> >> Savings
>> >> >> Time
>> >> >> http://support.microsoft.com/?kbid#4735
>> >> >> Time Stamp Changes with Daylight Savings
>> >> >> http://support.microsoft.com/?kbid9574
>> >> >> W32Time Client Does Not Fail Over to Secondary NTP Servers by
>> >> >> FQDN
>> >> >> http://support.microsoft.com/?kbid(5641
>> >> >> W32tm Command Generates Error Messages When Run on a Windows
>> >> >> 2000
>> >> >> Domain
>> >> >> Controller
>> >> >> http://support.microsoft.com/?kbid$7321
>> >> >> Win32 Time Service Informational, Warning, and Error Messages
>> >> >> http://support.microsoft.com/?kbid#2209
>> >> >> Windows 2000 Adjusts Time of Files on CD-ROMs for Local Time
>> >> >> Zones
>> >> >> http://support.microsoft.com/?kbid$2059
>> >> >> Windows 2000 Loses Date and Time on Every Boot
>> >> >> http://support.microsoft.com/?kbid$3883
>> >> >> Windows Time Service Continues to Monitor Secondary Client
>> >> >> Broadcasts
>> >> >> http://support.microsoft.com/?kbid$3993
>> >> >>
>> >> >>
>> >> >> Salu2!!
>> >> >> Javier Inglés
>> >> >> MS MVP, Windows Server-Directory Services
>> >> >>
>> >> >>

Salu2!!
Javier Inglés
MS MVP, Windows Server-Directory Services





"[[ecdl]]" escribió en el mensaje
news:
> En el DC:
> Event Error 29:
> The time provider NtpClient is configured to acquire time from one or more
> time sources, however none of the sources are currently accessible. No
> attempt to contact a source will be made for 240 minutes. NtpClient has no
> source of accurate time.
> Event Warning 47:
> Time Provider NtpClient: No valid response has been received from
> manually
> configured peer slug.ctv.es after 8 attempts to contact it. This peer will
> be
> discarded as a time source and NtpClient will attempt to discover a new
> peer
> with this DNS name.
> Lo mismo en un servidor de:
> - 1 Servidor TrendMicro
>
> - 1 Servidor SQL
>
> - 1 Servidor Righfax
>
> - 1 Servidor Mailsweeper & Fsecure
>
> - 1 Servidor ISA Server y Websense
>
> - 1 Servidor Blackberry
>
> - 1 Servidor Altiris
>
> - 1 Controlador Dominio
>
> - 1 Global Catalog
>
> - 1 Servidor MS Exchange & OWA
>
> - Servidor ISS Server Protect
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Javier Inglés [MS MVP]" wrote:
>
>> a ver, qué mensaje te da??
>>
>> Salu2!!
>> Javier Inglés
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>>
>>
>> "[[ecdl]]" escribió en el mensaje
>> news:
>> > Eso es lo que llevo haciendo mas de un mes..., por eso he venido aqui.
>> > :(
>> >
>> > "Javier Inglés [MS MVP]" wrote:
>> >
>> >> mira el error en www.eventid.net
>> >>
>> >>
>> >> Salu2!!
>> >> Javier Inglés
>> >> MS MVP, Windows Server-Directory Services
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "[[ecdl]]" escribió en el mensaje
>> >> news:
>> >> > Ya, pero no tiene que estar bien ya que generan errores en log de
>> >> > eventos.
>> >> >
>> >> > "Javier Inglés [MS MVP]" wrote:
>> >> >
>> >> >> Entonces simplemente no hagas nada.
>> >> >>
>> >> >> Por defecto, los servidores y estaciones de trabajo se sincronizan
>> >> >> entre
>> >> >> ellos automáticamente con los DCs.
>> >> >>
>> >> >>
>> >> >> Salu2!!
>> >> >> Javier Inglés
>> >> >> MS MVP, Windows Server-Directory Services
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> "[[ecdl]]" escribió en el mensaje
>> >> >> news:
>> >> >> > No quiero que se sincronicen con una hora exterior, creo que se
>> >> >> > sincronicen
>> >> >> > con un servidor que tenga poca carga, pero todo en LAN.
>> >> >> >
>> >> >> > Salu2
>> >> >> >
>> >> >> > "Javier Inglés [MS MVP]" wrote:
>> >> >> >
>> >> >> >> Cortesía de Fernando Reyes [MS MVP],
>> >> >> >>
>> >> >> >> Tienes que sincronizar tu PDC con una fuente externa de tiempo
>> >> >> >> (si
>> >> >> >> tienes
>> >> >> >> más de un DC, puedes identificar cuál es el que tiene el roll
>> >> >> >> FSMO
>> >> >> >> PDC
>> >> >> >> en
>> >> >> >> "Usuarios y Equipos de Active Directory" haciendo click derecho
>> >> >> >> sobre
>> >> >> >> el
>> >> >> >> nombre de tu dominio y ejecutando "Maestro de operaciones" en el
>> >> >> >> menú
>> >> >> >> emergente). Mira en www.eventid.net el resto de eventos. Te pego
>> >> >> >> a
>> >> >> >> continuación una respuesta al respecto de la sincronización de
>> >> >> >> tiempos
>> >> >> >> que
>> >> >> >> posteé en su día:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> <auto-pego>
>> >> >> >>
>> >> >> >> Los clientes deben sincronizar con los DC's, los DC's con el DC
>> >> >> >> Raíz y
>> >> >> >> éste
>> >> >> >> a su vez con una fuente de tiempo externa.
>> >> >> >>
>> >> >> >> Para sincronizar los clientes W2000/XP se ejecuta la instrucción
>> >> >> >> (puedes
>> >> >> >> hacer que se ejecute en un script de logon). Si es necesario
>> >> >> >> hacer
>> >> >> >> esto
>> >> >> >> es
>> >> >> >> porque algo raro hay, pues deberían sincronizar automáticamente
>> >> >> >> (generlamente es porque se les ha configurado un servidor de
>> >> >> >> tiempo
>> >> >> >> externo):
>> >> >> >>
>> >> >> >> net time /set /y
>> >> >> >>
>> >> >> >> Para sincronizar los clientes w9x:
>> >> >> >>
>> >> >> >> net time \ombre_de_DC /set /y
>> >> >> >>
>> >> >> >> Para que un equipo sincronice con un servidor de tiempos externo
>> >> >> >> se
>> >> >> >> ejecuta
>> >> >> >> la instrucción:
>> >> >> >>
>> >> >> >> net time /setsntp:"Lista de servidores NTP separados por
>> >> >> >> espacio"
>> >> >> >>
>> >> >> >> Para saber con qué servidores externos sincroniza un equipo se
>> >> >> >> mira
>> >> >> >> con:
>> >> >> >>
>> >> >> >> net time /querysntp
>> >> >> >>
>> >> >> >> que nos devuelve la lista de servidores NTP con los que está
>> >> >> >> configurado
>> >> >> >> o
>> >> >> >> nos advierte de que no está configurado para sincronizar con
>> >> >> >> ningún
>> >> >> >> servidor
>> >> >> >> de tiempo.
>> >> >> >>
>> >> >> >> Te recomiendo mires este W32Time linkpack. Te comento para qué
>> >> >> >> es
>> >> >> >> cada
>> >> >> >> enlace:
>> >> >> >>
>> >> >> >> Su propio nombre lo dice:
>> >> >> >>
>> >> >> >> 216734 - Cómo configurar un servidor horario autorizado en
>> >> >> >> Windows
>> >> >> >> 2000
>> >> >> >>
>> >> >> >> http://support.microsoft.com/defaul...;es;216734
>> >> >> >>
>> >> >> >> Esta es una lista de los diferentes servidores de tiempo que hay
>> >> >> >> por
>> >> >> >> la
>> >> >> >> red.
>> >> >> >> Tambien te explica lo que es un servidor primario, lo que es uno
>> >> >> >> secundario
>> >> >> >> y te recomienda la utilización de estos últimos:
>> >> >> >>
>> >> >> >> 262680 - A List of the Simple Network Time Protocol Time Servers
>> >> >> >> That
>> >> >> >> Are
>> >> >> >> Available on the Internet
>> >> >> >> http://support.microsoft.com/defaul...s%3B262680
>> >> >> >>
>> >> >> >> Conviene que al menos la primera vez (y tambien de vez en
>> >> >> >> cuando)
>> >> >> >> configures
>> >> >> >> el servicio para que no sólo registre los fracasos de
>> >> >> >> sicronización
>> >> >> >> si
>> >> >> >> no
>> >> >> >> que tambien registre los aciertos. Es normal que se produzcan
>> >> >> >> errores
>> >> >> >> (reiniciando el DC, con una caída de la conexión a Internet,
>> >> >> >> caída
>> >> >> >> del
>> >> >> >> servidor, etc.). Si ves que lo más normal es que sean aciertos
>> >> >> >> no
>> >> >> >> te
>> >> >> >> precupes por ver errores:
>> >> >> >>
>> >> >> >> 307937 - Configuring the Time Service to Log When the Time Is
>> >> >> >> Changed&
>> >> >> >> http://support.microsoft.com/defaul...07937&
>> >> >> >>
>> >> >> >>
>> >> >> >> Este te dice las diferentes entradas que hay en el registro para
>> >> >> >> configurar
>> >> >> >> el servicio W32Time:
>> >> >> >>
>> >> >> >> 223184 - Entradas del Registro para el servicio W32Time
>> >> >> >> http://support.microsoft.com/defaul...;es;223184
>> >> >> >>
>> >> >> >> Y ya, como fin de fiesta y por el mismo precio, copio un
>> >> >> >> linkpack
>> >> >> >> de
>> >> >> >> Ignacio
>> >> >> >> Adasme sobre el servicio W32Time:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> <pego>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Comienzo.
>> >> >> >>
>> >> >> >> Advancing Time on Production Computers and the Effect on Active
>> >> >> >> Directory
>> >> >> >> and FRS
>> >> >> >> http://support.microsoft.com/?kbid(9668
>> >> >> >> Basic Operation of the Windows Time Service
>> >> >> >> http://support.microsoft.com/?kbid"4799
>> >> >> >> Description of Date and Time Format Standards
>> >> >> >> http://support.microsoft.com/?kbid$7873
>> >> >> >> Registry Entries for the W32Time Service
>> >> >> >> http://support.microsoft.com/?kbid"3184
>> >> >> >> Using NET TIME for all Workstations and Servers
>> >> >> >> http://support.microsoft.com/?kbid0944
>> >> >> >> Using TIMESERV to Set and Synchronize Time
>> >> >> >> http://support.microsoft.com/?kbid#2255
>> >> >> >> Windows 2000 vs. Windows NT Time Synchronization
>> >> >> >> http://www.winnetmag.com/Articles/I...?ArticleID„56
>> >> >> >> Windows Time Synchronization Service
>> >> >> >> http://www.winnetmag.com/Articles/I...?ArticleIDƒ83
>> >> >> >> Un Documento muy bueno.
>> >> >> >> http://www.microsoft.com/windows200...meserv.asp
>> >> >> >>
>> >> >> >> Artículos.
>> >> >> >>
>> >> >> >> How Machines Determine the Time Source Server Using NET TIME
>> >> >> >> http://support.microsoft.com/?kbid6460
>> >> >> >> How to Configure an Authoritative Time Server in Windows 2000
>> >> >> >> http://support.microsoft.com/?kbid!6734
>> >> >> >> How to Configure the Short Date Format in Windows and Windows NT
>> >> >> >> http://support.microsoft.com/?kbid$1671
>> >> >> >> How to Synchronize the Time on a Windows 2000-Based Computer in
>> >> >> >> a
>> >> >> >> Windows
>> >> >> >> NT
>> >> >> >> 4.0 Domain
>> >> >> >> http://support.microsoft.com/?kbid%8059

Entonces ahora a cada uno le pongo su ip???


Reincia el servicio W32Time y listo.

Salu2!!
Javier Inglés
MS MVP, Windows Server-Directory Services





"[[ecdl]]" escribió en el mensaje
news:
> En el DC:
> Event Error 29:
> The time provider NtpClient is configured to acquire time from one or
> more
> time sources, however none of the sources are currently accessible. No
> attempt to contact a source will be made for 240 minutes. NtpClient has
> no
> source of accurate time.
> Event Warning 47:
> Time Provider NtpClient: No valid response has been received from
> manually
> configured peer slug.ctv.es after 8 attempts to contact it. This peer
> will
> be
> discarded as a time source and NtpClient will attempt to discover a new
> peer
> with this DNS name.
> Lo mismo en un servidor de:
> - 1 Servidor TrendMicro
>
> - 1 Servidor SQL
>
> - 1 Servidor Righfax
>
> - 1 Servidor Mailsweeper & Fsecure
>
> - 1 Servidor ISA Server y Websense
>
> - 1 Servidor Blackberry
>
> - 1 Servidor Altiris
>
> - 1 Controlador Dominio
>
> - 1 Global Catalog
>
> - 1 Servidor MS Exchange & OWA
>
> - Servidor ISS Server Protect
>
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> "Javier Inglés [MS MVP]" wrote:
>
>> a ver, qué mensaje te da??
>>
>> Salu2!!
>> Javier Inglés
>> MS MVP, Windows Server-Directory Services
>>
>>
>>
>>
>>
>> "[[ecdl]]" escribió en el mensaje
>> news:
>> > Eso es lo que llevo haciendo mas de un mes..., por eso he venido
>> > aqui.
>> > :(
>> >
>> > "Javier Inglés [MS MVP]" wrote:
>> >
>> >> mira el error en www.eventid.net
>> >>
>> >>
>> >> Salu2!!
>> >> Javier Inglés
>> >> MS MVP, Windows Server-Directory Services
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "[[ecdl]]" escribió en el mensaje
>> >> news:
>> >> > Ya, pero no tiene que estar bien ya que generan errores en log de
>> >> > eventos.
>> >> >
>> >> > "Javier Inglés [MS MVP]" wrote:
>> >> >
>> >> >> Entonces simplemente no hagas nada.
>> >> >>
>> >> >> Por defecto, los servidores y estaciones de trabajo se
>> >> >> sincronizan
>> >> >> entre
>> >> >> ellos automáticamente con los DCs.
>> >> >>
>> >> >>
>> >> >> Salu2!!
>> >> >> Javier Inglés
>> >> >> MS MVP, Windows Server-Directory Services
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> "[[ecdl]]" escribió en el
>> >> >> mensaje
>> >> >> news:
>> >> >> > No quiero que se sincronicen con una hora exterior, creo que
>> >> >> > se
>> >> >> > sincronicen
>> >> >> > con un servidor que tenga poca carga, pero todo en LAN.
>> >> >> >
>> >> >> > Salu2
>> >> >> >
>> >> >> > "Javier Inglés [MS MVP]" wrote:
>> >> >> >
>> >> >> >> Cortesía de Fernando Reyes [MS MVP],
>> >> >> >>
>> >> >> >> Tienes que sincronizar tu PDC con una fuente externa de
>> >> >> >> tiempo
>> >> >> >> (si
>> >> >> >> tienes
>> >> >> >> más de un DC, puedes identificar cuál es el que tiene el roll
>> >> >> >> FSMO
>> >> >> >> PDC
>> >> >> >> en
>> >> >> >> "Usuarios y Equipos de Active Directory" haciendo click
>> >> >> >> derecho
>> >> >> >> sobre
>> >> >> >> el
>> >> >> >> nombre de tu dominio y ejecutando "Maestro de operaciones" en
>> >> >> >> el
>> >> >> >> menú
>> >> >> >> emergente). Mira en www.eventid.net el resto de eventos. Te
>> >> >> >> pego
>> >> >> >> a
>> >> >> >> continuación una respuesta al respecto de la sincronización
>> >> >> >> de
>> >> >> >> tiempos
>> >> >> >> que
>> >> >> >> posteé en su día:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> <auto-pego>
>> >> >> >>
>> >> >> >> Los clientes deben sincronizar con los DC's, los DC's con el
>> >> >> >> DC
>> >> >> >> Raíz y
>> >> >> >> éste
>> >> >> >> a su vez con una fuente de tiempo externa.
>> >> >> >>
>> >> >> >> Para sincronizar los clientes W2000/XP se ejecuta la
>> >> >> >> instrucción
>> >> >> >> (puedes
>> >> >> >> hacer que se ejecute en un script de logon). Si es necesario
>> >> >> >> hacer
>> >> >> >> esto
>> >> >> >> es
>> >> >> >> porque algo raro hay, pues deberían sincronizar
>> >> >> >> automáticamente
>> >> >> >> (generlamente es porque se les ha configurado un servidor de
>> >> >> >> tiempo
>> >> >> >> externo):
>> >> >> >>
>> >> >> >> net time /set /y
>> >> >> >>
>> >> >> >> Para sincronizar los clientes w9x:
>> >> >> >>
>> >> >> >> net time \ombre_de_DC /set /y
>> >> >> >>
>> >> >> >> Para que un equipo sincronice con un servidor de tiempos
>> >> >> >> externo
>> >> >> >> se
>> >> >> >> ejecuta
>> >> >> >> la instrucción:
>> >> >> >>
>> >> >> >> net time /setsntp:"Lista de servidores NTP separados por
>> >> >> >> espacio"
>> >> >> >>
>> >> >> >> Para saber con qué servidores externos sincroniza un equipo
>> >> >> >> se
>> >> >> >> mira
>> >> >> >> con:
>> >> >> >>
>> >> >> >> net time /querysntp
>> >> >> >>
>> >> >> >> que nos devuelve la lista de servidores NTP con los que está
>> >> >> >> configurado
>> >> >> >> o
>> >> >> >> nos advierte de que no está configurado para sincronizar con
>> >> >> >> ningún
>> >> >> >> servidor
>> >> >> >> de tiempo.
>> >> >> >>
>> >> >> >> Te recomiendo mires este W32Time linkpack. Te comento para
>> >> >> >> qué
>> >> >> >> es
>> >> >> >> cada
>> >> >> >> enlace:
>> >> >> >>
>> >> >> >> Su propio nombre lo dice:
>> >> >> >>
>> >> >> >> 216734 - Cómo configurar un servidor horario autorizado en
>> >> >> >> Windows
>> >> >> >> 2000
>> >> >> >>
>> >> >> >> http://support.microsoft.com/defaul...;es;216734
>> >> >> >>
>> >> >> >> Esta es una lista de los diferentes servidores de tiempo que
>> >> >> >> hay
>> >> >> >> por
>> >> >> >> la
>> >> >> >> red.
>> >> >> >> Tambien te explica lo que es un servidor primario, lo que es
>> >> >> >> uno
>> >> >> >> secundario
>> >> >> >> y te recomienda la utilización de estos últimos:
>> >> >> >>
>> >> >> >> 262680 - A List of the Simple Network Time Protocol Time
>> >> >> >> Servers
>> >> >> >> That
>> >> >> >> Are
>> >> >> >> Available on the Internet
>> >> >> >> http://support.microsoft.com/defaul...s%3B262680
>> >> >> >>
>> >> >> >> Conviene que al menos la primera vez (y tambien de vez en
>> >> >> >> cuando)
>> >> >> >> configures
>> >> >> >> el servicio para que no sólo registre los fracasos de
>> >> >> >> sicronización
>> >> >> >> si
>> >> >> >> no
>> >> >> >> que tambien registre los aciertos. Es normal que se produzcan
>> >> >> >> errores
>> >> >> >> (reiniciando el DC, con una caída de la conexión a Internet,
>> >> >> >> caída
>> >> >> >> del
>> >> >> >> servidor, etc.). Si ves que lo más normal es que sean
>> >> >> >> aciertos
>> >> >> >> no
>> >> >> >> te
>> >> >> >> precupes por ver errores:
>> >> >> >>
>> >> >> >> 307937 - Configuring the Time Service to Log When the Time Is
>> >> >> >> Changed&
>> >> >> >> http://support.microsoft.com/defaul...07937&
>> >> >> >>
>> >> >> >>
>> >> >> >> Este te dice las diferentes entradas que hay en el registro
>> >> >> >> para
>> >> >> >> configurar
>> >> >> >> el servicio W32Time:
>> >> >> >>
>> >> >> >> 223184 - Entradas del Registro para el servicio W32Time
>> >> >> >> http://support.microsoft.com/defaul...;es;223184
>> >> >> >>
>> >> >> >> Y ya, como fin de fiesta y por el mismo precio, copio un
>> >> >> >> linkpack
>> >> >> >> de
>> >> >> >> Ignacio
>> >> >> >> Adasme sobre el servicio W32Time:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> <pego>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Comienzo.
>> >> >> >>
>> >> >> >> Advancing Time on Production Computers and the Effect on
>> >> >> >> Active
>> >> >> >> Directory
>> >> >> >> and FRS
>> >> >> >> http://support.microsoft.com/?kbid(9668
>> >> >> >> Basic Operation of the Windows Time Service
>> >> >> >> http://support.microsoft.com/?kbid"4799
>> >> >> >> Description of Date and Time Format Standards
>> >> >> >> http://support.microsoft.com/?kbid$7873
>> >> >> >> Registry Entries for the W32Time Service
>> >> >> >> http://support.microsoft.com/?kbid"3184
>> >> >> >> Using NET TIME for all Workstations and Servers
>> >> >> >> http://support.microsoft.com/?kbid0944
>> >> >> >> Using TIMESERV to Set and Synchronize Time
>> >> >> >> http://support.microsoft.com/?kbid#2255
>> >> >> >> Windows 2000 vs. Windows NT Time Synchronization
>> >> >> >> http://www.winnetmag.com/Articles/I...?ArticleID„56
>> >> >> >> Windows Time Synchronization Service
>> >> >> >> http://www.winnetmag.com/Articles/I...?ArticleIDƒ83
>> >> >> >> Un Documento muy bueno.
>> >> >> >> http://www.microsoft.com/windows200...meserv.asp
>> >> >> >>
>> >> >> >> Artículos.
>> >> >> >>
>> >> >> >> How Machines Determine the Time Source Server Using NET TIME
>> >> >> >> http://support.microsoft.com/?kbid6460
>> >> >> >> How to Configure an Authoritative Time Server in Windows 2000
>> >> >> >> http://support.microsoft.com/?kbid!6734
>> >> >> >> How to Configure the Short Date Format in Windows and Windows
>> >> >> >> NT
>> >> >> >> http://support.microsoft.com/?kbid$1671
>> >> >> >> How to Synchronize the Time on a Windows 2000-Based Computer
>> >> >> >> in
>> >> >> >> a
>> >> >> >> Windows
>> >> >> >> NT
>> >> >> >> 4.0 Domain
>> >> >> >> http://support.microsoft.com/?kbid%8059