On Wed, 16 Feb 2000, Frederick Bruckman wrote:

> On Wed, 16 Feb 2000, Chan Yiu Wah wrote:
> 
> > > > Feb 16 22:43:21 lts159 pppd[1797]: Remote IP address changed to
> > > > 202.66.33.78
> > > > Feb 16 22:43:21 lts159 pppd[1797]: IPCP terminated by peer (Unauthorized
> > > > remote IP address)
> 
> > Feb 16 17:02:34 pc77 pppd[1013]: Peer is not authorized to use remote
> > address 202.66.33.159
> > Feb 16 17:02:34 pc77 pppd[1013]: Connection terminated.
> 
> > 202.66.33.77:202.36.50.159
> 
> You have four different ip addresses here, where there should only be two.
> 
> Are either of 202.66.33.159 or 202.36.50.159 valid ips? Neither one
> looks up for me. In any case, I would set up the ppp link as a private
> network. The server gets
> 
> 192.168.200.1:192.168.200:11
> nodefaultroute
> 
> and not much else, and the client gets only...
> 
> ipcp-accept-local
> ipcp-accept-remote
> noipdefault
> noauth
> 
> so you can make any required changes on the server. You don't even
> need to specify a tty and baud rate--the getty does that for you.
> "silent persist" is also wrong if you're using a getty with a "ppp"
> user.
> 
> With that arrangement, you'll be able to telnet/ftp/rsh from the
> server to the Mac client and vice-versa. Once you get ppp working, you
> can complete the set-up by supplying legal addresses in the server
> options and setting up routes, or by setting up ipnat on the server.

The valid IPs are 202.66.33.77 (server) and 202.66.50.159 (client).
202.66.33.77 acts as the router for LAN-A and 202.66.50.139 is the router
for LAN-B.  Users in LAN-B will ask for services on one of the machines
(application for users in LAN-A and LAN-B) in LAN-A.  While LAN-A and
LAN-B are in two different location. The connection is the dialup ppp.
That is the only purpose of our porject.  

Clarence 


> 
> 
> 
>