At 2:08 AM -0400 10/15/99, Steven Schafersman wrote:
>Jeff Wax at [log in to unmask] on 10/15/99 12:39 AM sent the following:
>
>>OK, I'm off campus this year.  Obviously, I have to dial into Miami's
>>server, and I use FreePPP 2.5.3.   Anyway, at the start of the year, it
>>would connect just fine about 95% of the time, and if it didn't connect
>>right, I would stop it and do it again, and it would work.  Lately though,
>>it's only been connecting right on the first try maybe 25% of the time. . . .
>>
>I had the same problem two years ago when I had to use dial-in. The Miami
>PPP server software doesn't work reliably in the auto mode with FreePPP
>(the Miami-provided "recommended" client). It often hangs up during the
>user identity authentification. There are two solutions:

I'm not sure whats meant by the 'Miami-provided "recommended"
client'.  For the last couple of years, we've been recommending and
providing OT/PPP.  We had too many problems with FreePPP that were
well documented.  One of the biggest problems, which probably plays a
part here, is that FreePPP tends to corrupt the user name and
password data that it saves for it's "Direct" connection method.
I've seen numerous times when the user name has garbage characters in
it just looking at the configuration.

>1. Configure FreePPP to interact manually with the PPP server rather than
>automatically. You will have to enter your username and password manually
>every time you log on, and click something like "Connect to PPP" at the
>appropriate time. I did this for a week, then moved to:

This avoids the corrupt data problem.

>2. Use the Mac Open Transport/PPP client. This works very reliably in
>auto mode with the PPP server.

This is definately the best answer.

--
Dirk S. Tepe
Knowledge Base Coordinator
Miami University
MCIS - Hoyt
302 Hoyt Hall
Oxford, OH  45056

mailto:[log in to unmask]
http://www.users.muohio.edu/tepeds/
http://kb.muohio.edu/

Voice:  513.529.1514
FAX:    513.529.1496
Pager:  513.856.4065
alpha: [log in to unmask]