I'm assuming that these are transitory failures?
One of the more obscure causes of this msg is a delay
in validating the pap request from Win95. Could your
Radius server be getting more loaded?
You might be able to get a clue from the info that Win95
will record in \windows\ppplog.txt if you enable it on the
client under NetHood/Properites/Dialup/Adv/Record.
The debug 0x51 output is very useful it you can catch it
in the act.
Hope this helps,
Bill
On Thu, 14 Nov 1996 16:48:48 -0500 (EST), you wrote:
>Hello folks..
>
>Have a problem which started occuring lately..people who log in using
>win95 get the above message and their connection is never established.
>It happens with other OS's and dialers as well but the other dialers
>usually don't give much of an error message (not that MS does but
>that's the most common OS these days). Anyway..I was wondering if
>anyone has had it beofer or could shed some light on things..here's
>some base info...
>
>our dynamic IPs are from one class C (207.32.94.0), our pm's ether
>addresses are on another (204.157.123.0 or 207.32.89.0) and the
>reported addresses on the PMs are 207.32.93.10 (static IPs on
>207.32.93.0 among others). It happens on both dynamic and non-dynamic
>IP customers and it doesn't always happen. I've seen some debug 0x51
>logs and it seems that the remote machine isnt' replying to the PM's
>configure reqeusts in time. Any ideas?=20
>
>Thanks for the help,=20
>please reply to mickey@intr.net
>
>thanks again
>
>mickeY
>