12 Interactions with other PPP implementations

Contents of this section

12.1 I am using a Trumpet (for MSDOS) and the connection simply terminates. Why is this happening?

Trumpet does not like any VJ header compression. Use the pppd option "-vj" to turn it off.

12.2 I am using dp-3.1.2 (with SunOS) and the system will not allow me to use anything but ping, or nslookup. Why is this happening?

There is a bug in the 3.1.2 version of dp. Please get the 3.1.2a or later file from the dp ftp home site harbor.ecn.purdue.ecu. Until you can put the patch into dp, disable the vj header compression.

12.3 I can not connect to/with my Windows NT code (a.k.a. 'Daytona')

Microsoft has chosen to support a non-standard authentication protocol with Windows NT. That is their right to do so provided that they have registered the protocol number with the IANA. (They have.) If the `accept only Microsoft encrypted authentication' check box is set in the phone book entry, the connection will not complete. This setting mandates that the Daytona system only exchange PPP authentication with another Microsoft PPP implementation.

Linux does not support this authentication protocol.

If you have the option of changing the settings on the Daytona system then go to the Daytona Phone Book settings, advanced, security settings and choose either `Accept any authentication including clear text' to allow execution without authentication, or `Use clear text terminal login only' for PAP authentication, or `Accept only encrypted authentication' to allow CHAP authentication.

The Microsoft authentication sequence is a PAP style authentication with their encryption algorithm for the passwords. Normal PAP sends the passwords in clear text. This would violate their C2 security goals.

Next Chapter, Previous Chapter

Table of contents of this chapter, General table of contents

Top of the document, Beginning of this Chapter