<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.32.2">
</HEAD>
<BODY>
Agreed, we do the same for situations where the firewall is so poorly behaved there is nothing to be done, however by fiddling with the ports, we reduced those cases by an order of magnitude, giving many more customers the "It just works" experience. <BR>
<BR>
On Thu, 2011-06-09 at 09:42 -0700, Carlos Alvarez wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
anorexicpoodle wrote:
> Depending on your business model simply telling the customer how their
> firewall should be configured may work, but its not something that i
> suspect will take you too far since you are leaving the ability to break
> your service in the hands of your customer, which ultimately means they
> will break it, then be cross at you for something they did. Not an
> enviable situation at all.
We had our marketing and documentation company work up a one-page
explanation on this, and it's been very effective at explaining why this
is their problem and not ours. It not only saves the typing, but seems
to have some weight by looking "official" rather than some tech support
guy saying "it's not my problem."
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>