> Sorry if I missed the response to this. I have had 3.8b17 installed since
> it came out, then wham in the last two days have gotten calls from about 6-8
> people with connection problems. When looking at the sessions, I find the
> User of @!]. With the first two people I walked through their DUN setup
> with them and found that turning software compression back on allowed them
> to get a connect. Must have just been a fluke though because it wasn't the
> case with the rest. After rebooting the PM3, every one is now able to get
> on again. Do I have another week, or is there a permanent solution? Any
> info summary would be appreciated.
At this point in time, this is currently a bug in 3.8b17 that we are
working to crush for the next beta release that affects users on PRI
lines.
I would recommend that you log it with support then downgrade to either an
earlier beta or to 3.7.2c3 to avoid your users any further pain.
-jr
----
Josh Richards - <jrichard@livingston.com> - <josh@lucent.com>
[Beta Engineer] - LUCENT Technologies - Remote Access Business Unit
<URL:http://www.livingston.com/> * <URL:http://www.lucent.com/dns/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>