(ASCEND) A Pipeline 50 that won't behave....

[hjong@triview.nl]

A client of mine has a small network which is connected to an ISP using a
Pipeline 50. Recently, something unknown happened which caused the Pipeline
to stop routing packets from the internal network to the ISDN line.
It still connects to the ISP. When I run a terminal session on the
Pipeline, I can ping/traceroute hosts on the Internet and on the local
network, the ISP has confirmed that all is right at their end, too.
When I try a traceroute from one of the computers on the network, it finds
the Pipeline, but no stations beyond it. When I do this (or attempt other
forms of Internet access), the Pipeline will dial out, send something
('current line utilisation' shows that data is sent), then go silent (CLU =
0 %, 1 packet per second is counted on the WAN link).

I tried using the Pipeline in our own network. After changing IP addresses
and authentication info as appropriate, it works. There are no filters that
could be blocking information (Connections > *ISP router* >Session options
>data filter and call filter are both =0).

The only difference between our network and our client's is that they have
2 IP ranges and 2 Pipelines (they share a fileserver, but wanted separate
ISP connections for accounting purposes). Range A/Pipeline A works,
Pipeline B doesn't.
The network is set up correctly as far as I can see, and it has worked for
a few weeks before Pipeline B decided to quit.

The Lucent Website is no help (at least not the knowledgebase, which
contains few things not covered in the manuals).


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