The method you mentioned didn't solve the problem.  Here is the content of
all the config files and log messages of the srever and client.  I can who
the client before the line disconnected.  Any idea to fix my problem?
Thanks.

Clarence

======= options.tty00 (Server) =======
202.66.33.77:202.66.50.159
nodefaultroute
======= options.tty00 (Server) =======

======= Error (Server) =======
Feb 17 14:21:43 pc77 pppd[774]: pppd 2.3.9 started by root, uid 0
Feb 17 14:21:43 pc77 pppd[774]: Using interface ppp0
Feb 17 14:21:43 pc77 pppd[774]: Connect: ppp0 <--> /dev/tty00
Feb 17 14:21:47 pc77 pppd[774]: Deflate (15) compression enabled
Feb 17 14:21:47 pc77 pppd[774]: Peer is not authorized to use remote address 202
.66.50.159
Feb 17 14:21:47 pc77 pppd[774]: Connection terminated.
Feb 17 14:21:47 pc77 pppd[774]: Connect time 0.1 minutes.
Feb 17 14:21:47 pc77 pppd[774]: Sent 216 bytes, received 227 bytes.
Feb 17 14:21:47 pc77 pppd[774]: Exit.
======= Error (Server) =======

------------------------------------------------------------------------

======= peers (Client) =======
/dev/modem 115200		# modem port and speed
connect '/etc/ppp/chat-script "12345678"' # connect script

crtscts				# use hardware flow control
lock				# lock the modem port on connect
modem				# use full modem control

ipcp-accept-local		# allow remote to specify our IP address
ipcp-accept-remote		# allow remote to specify his IP address
noipdefault			# no local defaults for IP addresses
noauth

netmask 255.255.255.0		# netmask for our assigned IP address
user ppp			# account name to use to log onto remote
mtu 1500			# maximum transmission size for link
======= peers (Client) =======

======= Error (Client) =======
Feb 17 22:32:31 lts159 pppd[1062]: pppd 2.3.9 started by root, uid 0
Feb 17 22:32:56 lts159 pppd[1062]: Serial connection established.
Feb 17 22:32:56 lts159 pppd[1062]: Using interface ppp0
Feb 17 22:32:56 lts159 pppd[1062]: Connect: ppp0 <--> /dev/modem
Feb 17 22:33:00 lts159 pppd[1062]: Remote message: Login ok
Feb 17 22:33:00 lts159 pppd[1062]: Deflate (15) compression enabled
Feb 17 22:33:00 lts159 pppd[1062]: local  IP address 202.66.50.159
Feb 17 22:33:00 lts159 pppd[1062]: remote IP address 202.66.33.77
Feb 17 22:33:00 lts159 pppd[1062]: IPCP terminated by peer (Unauthorized remote IP address)
Feb 17 22:33:00 lts159 pppd[1062]: LCP terminated by peer (No network protocols running)
Feb 17 22:33:03 lts159 pppd[1062]: Connection terminated.
Feb 17 22:33:03 lts159 pppd[1062]: Connect time 0.1 minutes.
Feb 17 22:33:03 lts159 pppd[1062]: Sent 272 bytes, received 279 bytes.
Feb 17 22:33:05 lts159 pppd[1062]: Exit.
======= Error (Client) =======


On Wed, 16 Feb 2000, Frederick Bruckman wrote:

> On Wed, 16 Feb 2000, Chan Yiu Wah wrote:
> 
> > 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.  
> 
> You should still set distinct numbers for the ends of the ppp link.
> There's no need to use any of either LAN's ip numbers for that. Say
> the router for LAN-A gets 192.168.200.77, and for LAN-B
> 192.168.200.159. Then on the "server", it's
> 192.168.200.77:192.168.200.159, and on the client, as suggested (let
> the server set the address).
> 
> So on the LAN-A router (server), you could do "route add 202.66.50
> 192.168.200.159", and on LAN-B (client); "route add 202.66.33
> 192.168.200.77".
> 
> It's even clearer if you set names for the interfaces. Then it would
> be like routerA-ppp:routerB-ppp on one, and routerB-ppp:routerA-ppp on
> the other. Likewise, "route add 202.66.50 routerB-ppp" on routerA, and
> "route add 202.66.33 routerA-ppp" on routerB.
> 
> 
>