[EAS] CARRIER OUTAGE!??

[Ed Czarnecki]

Ray - 

The ports required for Email functionality in the DASDEC are port 25, when
not using authentication, and port 587 when using authentication. These port
numbers are fixed based on which method you are using. If you have blocked
these, that may explain the issue.  Maybe someone in IT changed which ports
were blocked/allowed.

Please feel free to drop and e-mail or call to our customer service - we're
finding that many (most) issues of this nature are traced back to local
network configuration.

Ed

Edward Czarnecki, Ph.D.
  Senior Director -  Strategy, Development & Regulatory Affairs
100 Housel Ave. | Lyndonville | NY | 14098
www.monroe-electronics.com
www.digitalalertsystems.com

This email message (including attachments) contains information which may be
confidential and/or legally privileged. Unless you are the intended
recipient, you may not use, copy, forward, or disclose to anyone the message
or any information c ontained in the message or from any attachments that
were sent with this email.   If you have received this email message in
error, please advise the sender by email, and delete the message. Caution
should be observed in placing any reliance upon any information contained in
this e-mail, which is not intended to be a legal representation or legal
advice.  Any decision taken based on the information provided in this e-mail
should only be made after consultation with appropriate legal, regulatory,
tax, technical, business, investment, financial, and accounting advisors.

-----Original Message-----
From: eas-bounces at radiolists.net [mailto:eas-bounces at radiolists.net] On
Behalf Of ray at electronicstheory.com

@Eric Adler -

Thanks for the heads-up concerning the known outages.

I understand backhoe fade, (as well as fat-finger fade), but since I can
ping, nmap, and access get the box's internal web server, I threw that
possibility out. Ports 80 and 443 work (so it does do CAP and its internal
web server is functional), but it no longer sends email (logs), and they
can't be accessed via SSH for troubleshooting/maintenance any more.

The problem "seems" more software than hardware based. All our boxes (both
working and non-working) are using the same version of software, were tested
to be fully functional before they left Dallas to parts unknown, and have
since been working fine but recently (last week or so) failed.

As for their locations, some are east coast (Boston for instance), and some
are as far west as Arizona. Our network is based out of Dallas, but we have
stations nationwide exhibiting similar problems.  About 1/10th of our boxes
across the country are presently showing the same issue.

Firewalls vary from site to site, depending on what the particular carrier
provides at time of hook-up.

Ray

_______________________________________________
This is the EAS Forum Discussion List

Please invite your friends to join our Forum!
http://lists.radiolists.net/mailman/listinfo/eas

And, remember the main page: http://eas.radiolists.net