> Apr 11 13:28:37 portmaster error: port S18 stopped too long - flushing packet
> queue
> Apr 11 13:28:42 portmaster error: port S18 stopped too long - flushing packet
> queue
> Apr 11 13:29:23 portmaster last message repeated 2 times
> Apr 11 13:29:47 portmaster error: port S18 stopped too long - flushing packet
> queue
> Apr 11 13:30:02 portmaster error: port S18 stopped too long - flushing packet
> queue
> Apr 11 13:30:03 portmaster dialnet: port S18 session disconnected dest pm03-w
> in.emporium.on.ca
>
>
> I rarely see this but it is happening to one user rather frequently. The
> problem is that this is the account for a computer store that acts as an
> agent for our company. They also sell access for another provider and have
> no such disconnect problems with that provider. This will really hurt us if
> I cannot resolve it.
Are they dialing in to the same port? If so, try changing the modem on
that port, moving them to another modem, changing their modem, reduce the
possibilities of failure, by doing one change at a time. Most times at a
site I worked at it was a modem failing on our end, basically getting hung
in an indeterminate state. Check it out.. 8)
> I was relieved to see an error message associated with the disconnect; maybe
> there is an answer to the problem.
Never a problem, always an opportunity! This will show them your
trouble-shooting ability and response to a problem, whether percieved or
real.
BTW, MZ is out on the road according to sources...he'll return to the lair
on Monday..
-- Aloha,Sherwood