It is, as far as we can tell, the client. We are not admitting to any
problem in the PM-3 that causes this. And, as I said, I've heard reports
of this sporadically with MOTs before 3.7.2, and a few other clients. And
all indications are it is the client causing the stops.
If and when it is indentified as a problem on our end, it will be addressed.
At this time we do not feel it is our issue to resolve, and we believe the
K56flex code in the PM-3 is solid and compliant. And this does not happen
with all clients that we have seen, nor even 'reliably' with those it has
been reported with.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.