Hi David,
The 2 logs look very different; I would probably guess that the Palm is being
authenticated by different servers.
The logon script doesn't make a difference here. Logon scripts are typically
used by front-end servers to route PPP sessions to the appropriate PPP
server. Since you are directly connected to a PPP server there is no need for
a logon script.
The unsuccessful connection authenticates without using a username/password.
This is not necessarily a problem; MochaPPP (which works very well with Palm)
does authentication this way. The PPP log looks good. I can't tell why it's
failing.
Most Palm Ethernet cradles (from Palm and Symbol) request an IP address from a
DHCP server on the LAN, then the PPP authentication takes place between the
cradle and the Palm. This could explain the difference in the PPP logs.
I suggest you look at the WaveLAN manual. It probably needs further
configuration.
Regards,
Peter Easton
Palm Developer Support
David Tribble wrote:
> G'Day,
>
> I'm trying to use a wireless Ethernet connection as my serial connection
> between my Palm and a RAS server. The connection works with just a
> straight serial cable. It doesn't work when I use a wireless Ethernet
> connection (via serial converters) in place of the serial connection. The
> connection doesn't do the authentication that RAS requires, and I'm
> guessing I'm missing the appropriate script on my Palm. Anybody know
> anything to help?
>
> The unsuccessful connection (via wireless with the script of just "Send:
> CLIENT" and "End") results in the message "Connected, authenticating user"
> on the RAS server and the following log on the Palm:
>
> S: CLIENT
> LCP->CfgReq
> LCP<-CfgReq
> LCP->CfgAck
> LCP<-CfgAck
> LCP Up
> IPCP->CfgReq
> IPCP<-CfgReq
> IPCP->CfgRej
> IPCP<-CfgRej
> IPCP->CfgReq
> IPCP<-CfgReq
> IPCP->CfgAck
> IPCP<-CfgAck
> IPCP Up
>
> The successful connection (via the wire cable with the script of just
> "Send: CLIENT" and "End") results in a useable connection with the
> following long on the Palm:
>
> S: CLIENT
> LCP->CfgReq
> LCP<-CfgReq
> LCP->CfgRej
> LCP<-CfgAck
> LCP<-CfgReq
> LCP->CfgAck
> LCP Up
> CHAP<-Req
> CHAP->CfgAck
> CHAP<-Success
> CHAP Up
> IPCP->CfgReq
> LCP->ProRej
> IPCP<-CfgReq
> IPCP->CfgNak
> LCP->ProRej
> IPCP<-CfgNak
> IPCP->CfgReq
> IPCP<-CfgReq
> IPCP->CfgAck
> IPCP<-CfgAck
> IPCP Up
>
> This is all using direct serial on the Palm with appropriate speeds. I'm
> guessing I need more in my Palm script but don't know what to put in. the
> MS site isn't very helpful in providing the strings that a RAS server will
> take.
>
> I find it odd that the changing of the cables makes this difference, but
> since the WaveLAN is a packet system, it is repackaging the data, and that
> must make a difference.
>
> trib
> --------------------------------------------------
> David Tribble, Logicon INRI Hawaii
> (808) 625 2118 (v) (808) 625 6315 (f)
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
