I've used these for years now, and the only times I've ever had problems with them freezing up or generating lots of CRC errors were when we were using link compression. I assume since you've said every configuration was tried, you also have tried with no link compression whatsoever and suffered the same result? Joe On Tue, 11 Dec 2001, Mark L. Pieratt wrote: > Hi all, > > Anyone out there familiar with any problems which exist with Pipeline 50 > units which cause them to just start generating large amounts of CRC > errors, then losing connection (ISDN)? I'm using these units creating a > WAN between two offices. > > I've looked at everything! > > I've ordered several line quality tests on the ISDN lines, all the way to > my equipment. Should I trust the ISDN vendor (ma bell)?, I'm assuming I > do. I've looked at network traffic, nothing on either side is causing > CRC's, as I've isolated all hosts off each LAN. I've looked at ALL > configuration settings, and tried ALL different scenarios of bridging, and > routing. Almost always, when I reset both units (cycle power for > 20sec's+), they connect up fine for x-amount of time (varying between > 15min's and two weeks of error free uptime). Much more to tell, I'll spare > the details, I've spent a lot of time trying to solve this problem - > > Anyone with similar experiences, advice, clues??? > > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > ------------------------- Joseph Barnhart Florida Digital Turnpike Network Administrator http://www.fdt.net ------------------------- ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/