¡Te damos la bienvenida al nuevo sysarmy --help! Para recuperar tu usuario pedí un password reset.
WSUS clientes no sincronizan
Instale un servidor de cero y sigue fallando. Probe todo los parches de MS.
No es un tema de proxy ni firewall, ya que el mismo servidor que contiene el WSUS tambien falla.
Parte del Log:
2016-06-09 11:21:25:289 784 fc8 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-09 11:21:25:289 784 fc8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.200.27/ClientWebService/client.asmx
2016-06-09 11:22:27:258 784 fc8 Misc WARNING: Send failed with hr = 80072ee2.
2016-06-09 11:22:27:258 784 fc8 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-06-09 11:22:27:258 784 fc8 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2016-06-09 11:22:27:258 784 fc8 PT + Caller provided credentials = No
2016-06-09 11:22:27:258 784 fc8 PT + Impersonate flags = 0
2016-06-09 11:22:27:258 784 fc8 PT + Possible authorization schemes used =
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2016-06-09 11:22:27:258 784 fc8 PT WARNING: PTError: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: Sync of Updates: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 Agent * WARNING: Failed to synchronize, error = 0x80072EE2
2016-06-09 11:22:27:258 784 fc8 Agent * WARNING: Exit code = 0x80072EE2
2016-06-09 11:22:27:258 784 fc8 Agent *********
2016-06-09 11:22:27:258 784 fc8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-09 11:22:27:258 784 fc8 Agent *************
Gracias! Saludos!
No es un tema de proxy ni firewall, ya que el mismo servidor que contiene el WSUS tambien falla.
Parte del Log:
2016-06-09 11:21:25:289 784 fc8 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-09 11:21:25:289 784 fc8 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://192.168.200.27/ClientWebService/client.asmx
2016-06-09 11:22:27:258 784 fc8 Misc WARNING: Send failed with hr = 80072ee2.
2016-06-09 11:22:27:258 784 fc8 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-06-09 11:22:27:258 784 fc8 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2016-06-09 11:22:27:258 784 fc8 PT + Caller provided credentials = No
2016-06-09 11:22:27:258 784 fc8 PT + Impersonate flags = 0
2016-06-09 11:22:27:258 784 fc8 PT + Possible authorization schemes used =
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2016-06-09 11:22:27:258 784 fc8 PT WARNING: PTError: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: Sync of Updates: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2016-06-09 11:22:27:258 784 fc8 Agent * WARNING: Failed to synchronize, error = 0x80072EE2
2016-06-09 11:22:27:258 784 fc8 Agent * WARNING: Exit code = 0x80072EE2
2016-06-09 11:22:27:258 784 fc8 Agent *********
2016-06-09 11:22:27:258 784 fc8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-09 11:22:27:258 784 fc8 Agent *************
Gracias! Saludos!
Este hilo ha sido cerrado.
Respuestas
Otra opcion ver logs en el server WSUS y ver si hay algo raro, Opcion 3 ver en las maquinas clientes el registro a ver si estan apuntando correctamente a WSUS.
Opcion 4 hay una herramienta de testeo de solarwinds para WSUS.
De ultima bajate batchpatch y trata de tirar parches a maquinas remotas, si te tira error vas a poder debuggear mejor.
Saludos