On Sun, 30 Aug 1998, Brian C. Grayson wrote:

> Aug 30 12:40:09 k9 pppd[651]: sent [LCP ConfReq id=0x2 <asyncmap 0x0>
<magic 0xfb0cfdb9> <pcomp> <accomp>]
> Aug 30 12:40:09 k9 pppd[651]: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0xfb0cfdb9> <pcomp> <accomp>]
> Aug 30 12:40:09 k9 pppd[651]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <compress VJ 0f 01>]
> Aug 30 12:40:09 k9 pppd[651]: rcvd [IPCP ConfNak id=0x1 <addr 128.83.112.115>]
> Aug 30 12:40:09 k9 pppd[651]: sent [IPCP ConfReq id=0x2 <addr 128.83.112.115> <compress VJ 0f 01>]
> Aug 30 12:40:09 k9 pppd[651]: rcvd [IPCP ConfAck id=0x2 <addr 128.83.112.115> <compress VJ 0f 01>]
> Aug 30 12:40:12 k9 pppd[651]: rcvd [IPCP ConfReq id=0x12 <compress VJ 0f 00> <addr 0.0.0.0>]
> Aug 30 12:40:12 k9 pppd[651]: sent [IPCP ConfRej id=0x12 <addr 0.0.0.0>]
> Aug 30 12:40:12 k9 pppd[651]: rcvd [IPCP ConfReq id=0x13 <compress VJ 0f 00>]
> Aug 30 12:40:12 k9 pppd[651]: sent [IPCP ConfAck id=0x13 <compress VJ 0f 00>]
> Aug 30 12:40:12 k9 pppd[651]: Could not determine remote IP address
> Aug 30 12:40:12 k9 pppd[651]: sent [IPCP TermReq id=0x3 "Could not determine remote IP address"]
> Aug 30 12:40:12 k9 pppd[651]: rcvd [IPCP TermAck id=0x3]
> Aug 30 12:40:12 k9 pppd[651]: sent [LCP TermReq id=0x3 "No network protocols running"]
> Aug 30 12:40:12 k9 pppd[651]: rcvd [LCP TermAck id=0x3]
> Aug 30 12:40:12 k9 pppd[651]: Connection terminated.
> Aug 30 12:40:14 k9 pppd[651]: Exit.

It appears that the host expects you to tell it it's ip address! Is your
chat script providing a login name and password? Perhaps you're expected
to parse the remote address that it gives you after accepting you're
login. You could probably see if that's the case by running 'chat' with
the '-V' option.

You might also like to inquire of your university to see if they use pap.
Almost all modern terminal servers do. In that case, you end the chat with
"login:", and let pppd log you in using the information in the pap-secrets
files. That's a little more robust than chat scripts, which tend to break
on different terminal servers.

If not that, maybe they can tell you the address of the flakey
host/server/gateway. You can supply that, in the options file, preceded
with a colon. If you also add 'ipcp-accept-remote', you'll be covered in
case they use more than one terminal server (or change the number).