Buenos días, estamos tratando de tomar los eventos de nuestro servidor ISASERVER y nos dá este error. En el servidor ya abrimos el puerto y creamos las reglas de entrada y salida. También agregamos la máquina como estación autorizada para la administración del ISA y sin embargo nos sigue dando error.

   Agradecido de sus comentarios al respecto.

    Hector Carvajal
    Analista de seguridad de Infraestructura

Host Sort by host name (ascending)Sort by host name (descending)

Service Sort by service name (ascending)Sort by service name (descending)

Status Sort by service status (ascending)Sort by service status (descending)

Last Check Sort by last check time (ascending)Sort by last check time (descending)

Duration Sort by state duration (ascending)Sort by state duration time (descending)

Attempt Sort by current attempt (ascending)Sort by current attempt (descending)

Status Information

Servidor_ISASERVER



C:\ Drive Space



CRITICAL

01-21-2008 15:44:33

0d 16h 3m 44s

1/3

CRITICAL - Socket timeout after 10 seconds 


CPU Load



CRITICAL

01-21-2008 15:47:49

0d 16h 1m 29s

1/3

CRITICAL - Socket timeout after 10 seconds 


Memory Usage



CRITICAL

01-21-2008 15:50:04

0d 15h 59m 13s

1/3

CRITICAL - Socket timeout after 10 seconds 


NSClient++ Version



CRITICAL

01-21-2008 15:52:20

0d 16h 5m 57s

1/3

CRITICAL - Socket timeout after 10 seconds 


Uptime



CRITICAL

01-21-2008 15:44:36

0d 16h 3m 41s

1/3

CRITICAL - Socket timeout after 10 seconds 

 

El servidor esta agregado para ser monitoreado, pero no envía ningún traps de status por el bloqueo del puerto.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting 
any issue. 
::: Messages without supporting info will risk being sent to /dev/null

Reply via email to