That has been my nightmare for about a week now. I now know that the
problem is ComOS 3.7.2 and maybe any flavor of 3.7.x. Livingston or
Lucent, PLEASE solve this SERIOUS BUG IN YOUR COMOS 3.7.2.
For the past few weeks, customer complaints about that DUN error has
increased tremendously and I just couldn't understand why. I checked
*everything* I could think of. I followed suggestions on this list. I
checked phone lines, I checked a slowdown on the PM2, I checked radius, I
checked our internal wiring, I had PacBell check their lines, I guessed
that weather was causing the problem, I checked if maybe the new PRI I
ordered somehow affected our analog lines, I checked for a commonality
amoung OS. I checked for overheating equipment, I checked for RF problems,
I conditioned some test lines, I attenuated loop current. I checked the
modem banks. I rebooted PMs. I walked customer through reinstall of DUN,
checked port settings on Win95, checked protocols.
I was getting a major headache. It was so bad, Win 3.1 was getting same
errors, Mac was getting errors, NT getting errors.
One thing was clear, everybody was getting the error and they were upset.
I made it my *Mission* to solve this problem.
I did notice, recently that the problem only occurred during peak times
when our lines became full. I also noted that we have 6 PM2E-30s, the
first 3 had ComOS 3.5 and those were the first to fill with dialin
customers. I also noted that the last 3 PM2E-30s have ComOS 3.7.2. One
was shipped with 3.7.2, I upgraded the other 2 with 3.7.2 about the same
time these errors increased. In fact, these errors began to increase when
the PM with 3.7.2 arrived!
I just downgraded from 3.7.2 to 3.5 and I now have the blessed sound of NO
PHONES RINGING OFF THE HOOK for TECH SUPPPORT.
The blessed sound of silence!
There is the occasional DUN error but easily solved. Customers who
couldn't connect because of the problem all of sudden connect and even
congratulate me because now they connect faster than ever. I even
downgraded the PM2E that came with ComOS 3.7.2 to 3.5 and now I have nearly
totally eliminated connection problems. The only connection problems now
are the new customers installing for the first time. I can handle those.
In closing, it is my sincere opinion based on experience that ComOS 3.7.x
is seriously flawed.
Thanks to all who responded to my plea for help during my "Avalanche of
Tech Support Calls"
Jose de Leon
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.