On Mon, 24 Apr 2006 17:01 -0400, William W. Fisher wrote:
On Apr 24, 2006, at 12:35 PM, Chip Old wrote:
We recently upgraded our Barracuda 400 to firmware v3.4.01.003, then to
v3.4.01.004. Both seem to break InterMapper's Barracuda HTTP probe.
InterMapper shows the Barracuda as down and shows "Gave up connecting
to port 8000 after 0 seconds" as the reason. I'm not sure where the "0
seconds" comes from. The timeout in InterMapper for the device was the
3 second default, but I've tried bumping it up to very high values.
That doesn't help.
The message "Gave up connecting to port 8000 after 0 seconds" indicates
that InterMapper immediately failed when connecting to port 8000,
perhaps because there isn't anything listening on that port. This isn't
a timeout issue.
TCP port 8000 is the default for the unencrypted Barracuda probe. Have
you tried using the SSL/HTTPS version of the probe? It connects to port
443 by default.
Our Barracuda is listening on port 8000. If it weren't, we wouldn't be
able to access its Web interface. We don't have it configured for
SSL/HTTPS, so it isn't listening on port 443.
The problem began when we upgraded the Barracuda from firmware v3.3 to
v3.4. I'm guessing the problem is related to the fact that v3.4
introduces a large number of changes. We have a case open on the problem
(#47197), so I'm sure it will get figured out.
--
Chip Old (Francis E. Old) E-Mail: [EMAIL PROTECTED]
BCPL Network Administrator Phone: 410-887-6180
BCPL.NET Internet Services Manager FAX: 410-887-2091
Baltimore County Public Library
320 York Road
Towson, MD 21204-5179 US
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
