I have a fairly standard install of Wildfire and use:
Port: 5222
SSL Mode: Explicit or None
Auth. Mech.: PLAIN
Gary
-Original Message-
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Steve Davis
Sent: Thursday, March 15, 2007 12:36
To: Servers Alive Discussio
I've setup XMPP using Wildfire and it seems to be working OK. I've
installed Wildfire on the same server as Servers Alive and have to
following settings in Servers Alive:
XMPP Host:
Port: 5233:
SSL mode: Automatic
Auth. Mech.: PLAIN
Username: serversalive
password: *
Default recipient: {insta
Hi,
Is anyone using this at all, particularly with the Wildfire server?
I cannot work out which combination of settings to use, it seems more
complex than it needs to be as the clients just ask for server name,
port, logon name.
Steve
To unsubscribe send a message with UNSUBSCRIBE as subject to
1) We use an api on the system running Servers Alive and that one gives us that
timeout.
2) don't think that there is currently a possible work around - once the windows
agents is released then that could be a solution/workaround
Dirk Bulinckx.
-Original Message-
From: Servers Alive Disc
Yes.
Chris>>
-Original Message-
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Gary Dodd
Sent: Thursday, March 15, 2007 7:55 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Windows NT Process Error
Do you "Second Knock" enabled?
Gary
-Orig
Two more questions:
1) Is that the API on the Servers Alive server reporting the timeout,
or the API on the server being checked?
2) Is there a workaround? I ask, because I have two servers where I
can't check any processes, because I can never see a list of processes,
and another that will oc
Do you "Second Knock" enabled?
Gary
-Original Message-
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Dirk Bulinckx
Sent: Wednesday, March 14, 2007 17:51
To: Servers Alive Discussion List
Subject: RE: [SA-list] Windows NT Process Error
In some cases the api
