PPP Autentication failed

[Werner Rips]

Hi Enrico,
I ran into similar problems with the connection to my provider when I want to connect to him with my WS715/100 box.

I edited the Auth-file with the following line:
tnt_e1 otelo\sonline
where otelo is my username and password is online.

hope this helps,
good luck
Werner

[Anthony deRito]

Enrico, the problem is with the authentication mechanism of PPP. It is either PAP or CHAP. PAP is a very simple authentication protocol but CHAP (Challenge Handshake Authentication Protocol) is preferred because of its two-way handshake. Your provider told you it was CHAP. When your interface has established its link the provider will send a challege message to your interface. On each side, the username and password to expect from the other side must be defined for the challenge to be successfull. I suspect that one or both of these parameters are not identified correctly on one or both sides. Your provider should give you this information. In any event, I beleive it is CHAP thats giving you the problem.

Tony

[Enrico Venegoni]

Hi,

thanks, but I haven't solved the problem yet and moreover, my provider is not able to give me any parameter about CHAP initial negotiation.

Thus, I have tried other tests.

I have another login/passwd (lent by a friend) on another provider. With this one there isn't any problem. The authentication phase has success, I set DNS, routing and netscape. Than I'm in internet.

The curious thing, if I connect to this provider with "cu -l cul0p0" and insert login and passwd when request, I'm connect since the outputs on terminal are a few rows like this:

^H}#@!}!e} }<}"}&} }*} } }%}&})}/}?K}$}(@%} } }#h}'}"}(}"f+
...................
...................
...................

Ok, after this, I'm forced to hungup.

Instead, with the other provider I have "Authentication failed" and login
request still appears. This is exact behaviour like pppd.

How can be this?

-Enrico

[Anthony deRito]

Enrico, I have done a little research on this and what I am reading is that there are
issues with connecting via PPP using CHAP (or PAP) from Unix/Linux boxes to MicroSoft servers. There are many threads out there that talk about Linux users who discovered that Microsoft uses a DES algorithm which until recently was incompatible with the pppd process. There were Linux patches which were provided require a patch to get this to work. I don't know if your provider used MS but I am wondering if this is the same type of thing with HP-UX.

Tony

[Enrico_3]

Hi Anthony,

I don't know if pppd support MS CHAP by default, so I've tested pppd adding "requiremschap" line command option. This option should set the CHAP to Microsoft CHAP. Does requiremschap option support DES algorithm?
Or, who can know this?
As long as my provider is not able to give me detailed information about CHAP negotiation, do you have suggestions to get these information by unix line command or how trace what across the line from WS to ISP?
Moreover, in the peer prompt I can't understand witch kind of Server is (Microsoft NT Server, Unix etc.) since I have the following prompt only:

User Access Verification

Username:

All the best
-Enrico

[Anthony deRito]

Enrico, I am sorry I cannot provide you with further insight to this problem. It sounds however that you need to press your provider for more information since they are the ones who need to debug on their end. I suppose some form of network tracing tool may be usefull. You can check out HP-UX nettl to see if you can capture CHAP challenges. The GUI form is /opt/nettladm/bin/nettladm.

Tony