Re: (ASCEND) Max40XX runing 6.1.3

To: Daniel <daniel@lynx.bc.ca>
Subject: Re: (ASCEND) Max40XX runing 6.1.3
From: "Oliver J. Albrecht" <oj@nexus.flensbone.net>
Date: Sat, 18 Jul 1998 23:30:17 +0200
Cc: ascend-users@bungi.com
In-Reply-To: <e30bf2823ac1@news.allcon.net>
Sender: owner-ascend-users@max.bungi.com
User-Agent: tin/pre-1.4-980202 (UNIX) (Linux/2.0.33 (i586))

In article <e30bf2823ac1@news.allcon.net> you wrote:

>After all the complaints calls that we received after we upgraded to 6.1.3,
>we find that all those users are using Trumpet Winsock to connect. It seems
>starting from 6.1.X and up, our trumpet winsock users can no longer stay
>connect. This happens on 6.1.0 and 6.1.3 that we have tested on our Max.

>Any way to get around this? 

Yes, this is related to LQM, turning it off will most likely fix the
problem. We were seeing the same thing with LQM.

>Also, I find the disconnect-cause-code is 240

240 is a disconnect caused by LQM.

-- 
Oliver J. Albrecht <oj@nexus.flensbone.net>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

Prev by Date: Re: (ASCEND) User counts....SNMP (fwd)
Next by Date: Re: (ASCEND) TNT warning
Prev by thread: RE: (ASCEND) Max40XX running 6.1.3
Next by thread: (ASCEND) Fixed 4030 & sync.serial port
Index(es):
- Main
- Thread