On Sat, Nov 17, 2001 at 05:11:14PM +0100, Manuel Bouyer wrote:
> On Sat, Nov 17, 2001 at 10:02:57AM -0600, David Kanter wrote:
> > This is the logging that was done. Perhaps it's helpful:
> > Nov 17 09:37:00 localhost pppd[271]: Serial connection established.
> > Nov 17 09:37:00 localhost pppd[271]: Using interface ppp0
> > Nov 17 09:37:00 localhost pppd[271]: Connect: ppp0 <--> /dev/tty03
> > Nov 17 09:37:02 localhost pppd[271]: local  IP address 144.74.60.71
> > Nov 17 09:37:02 localhost pppd[271]: remote IP address 144.74.60.19
> > Nov 17 09:43:21 localhost pppd[271]: Hangup (SIGHUP)

David, 

Any luck on this?

After you're connected, check the log again to determine your remote
ip address.  You should have a default route to it and be able to ping
it.  

'route show' should show something like:
Internet:
Destination      Gateway            Flags 
default          144.74.60.19       UG     
[...]

If it's there -- which it should be, based on what you said -- you
should be able to ping it, taking care not to involve name services:

$ ping -n -c 3 144.74.60.19
PING 192.168.1.5 (192.168.1.5): 56 data bytes
64 bytes from 144.74.60.19: icmp_seq=0 ttl=255 time=0.362 ms
64 bytes from 144.74.60.19: icmp_seq=1 ttl=255 time=0.352 ms
64 bytes from 144.74.60.19: icmp_seq=2 ttl=255 time=0.358 ms
[...]

If you can ping your default gateway, then I'd try to ping the DNS,
that is, the DNS address provided by your ISP.  If you can ping your
default gateway and not their DNS, that's an easy thing (relatively)
to explain to your ISP.

HTH.

--jkl