Hello John,
On Sep 9, 8:28pm, John Gray wrote:
> Subject: (RADIATOR) Radiator ignoring authentication request
> Hi,
>
> I am still having problems getting Radiator to authenticate VOP Mail Email
> Server. I have triple checked the secret and am comvinced that they are
> the same. I have also checked that I am trying to log in with a correct
> login and password. I have had the email server working other than using
> Radiator to authenicate. It must be something simple that I am over
> looking. The Radiator server and the Email Server are in different
> domains, I do not know if that makes a difference.
Probably not.
> I am now getting this
> message.
>
> Thu Sep 9 08:22:50 1999: INFO: Access rejected for atest: NT CheckPassword
> failed: 86: The specified network password is not correct.
Looks like the password is failing to authenticate to me.
Have you confirmed that you can authenticate that user using radpwtst?
If you can authenticate the user with radpwtst, but not with VOP, then I still
suspect some sort of problem with the secret.
It might be best if you posted some Radiator log files at trace level 4. You
could show what happens when you authenticate the user with radpwts, and with
VOP. You should also include your Radiator configuration file (no secrets,
please).
>
> Appreciate some help,
With the above information, we should be able to shed some light onit.
Cheers.
>
> John
>
>
>
>
> >>From [EMAIL PROTECTED] Thu Sep 9 02:19:06 1999
> >From: "Mike McCauley" <[EMAIL PROTECTED]>
> >Date: Thu, 9 Sep 1999 17:22:05 -0500
> >X-Mailer: Z-Mail (4.0.1 13Jan97)
> >To: John Gray <[EMAIL PROTECTED]>
> >Subject: Re: (RADIATOR) Radiator ignoring authentication request
> >
> >Hello John,
> >
> >On Sep 8, 8:35pm, John Gray wrote:
> >> Subject: (RADIATOR) Radiator ignoring authentication request
> >> Hi,
> >>
> >> Thanks for the help on trace for folks.
> >>
> >> To continue my problem solving strategies I have now found that my VOPMail
> >> Email Server is sending an authenication request to Radiator, but Radiator
> >> is ignoring it.
> >OK, thats good progress.
> >
> >> I get the following message but I know I am using the
> >> correct password. What else could it be?
> >>
> >> Wed Sep 8 20:11:16 1999: INFO: Duplicate request id 37 received from
> >> 216.61.219.7: ignored
> >> Wed Sep 8 20:11:16 1999: INFO: Duplicate request id 37 received from
> >> 216.61.219.7: ignored
> >> Wed Sep 8 20:11:31 1999: INFO: Access rejected for atest: NT CheckPassword
> >> failed: 86: The specified network password is not correct.
> >
> >First, its probably a good idea to set DupInterval to 0 for the client where
> >the VOP requests are coming from. That will prevent the Duplicate request
> id 37
> >messages.
> >
> >Second, my best guess is that the shared secret between VOP and Radiator
> is not
> >entered correctly into your Client clause. That will cause the password to
> >decrypt incorrectly, and the result is indistinguishable from a bad
password.
> >
> >Hope that helps.
> >
> >Cheers.
> >
> >>
> >> Appreciate some help,
> >>
> >> John
> >>
> >>
> >> Hi John,
> >> On Sep 7, 5:57pm, John Gray wrote:
> >> > Subject: (RADIATOR) radius config script
> >> > Hi,
> >> >
> >> > I am using radiator to authenicate using my NT user data base. I got a
> >> > copy of VOPMail an email server and it will authenicate using a radius
> >> > server. I can not get it to find the radius server. The VOP people
> >> > obviously sent me back to Radius for answers. What do I need to do for
> >> > Radiator to recognize the email server's requests?
> >> >
> >> > Appreciate some ideas.
> >> Probably the first thing is to see whether the requests sent by VOP are
> >> getting
> >> to your Radiator.
> >> Its easist to do this if you run your radiator at trace level 4 in the
> >> foreground. Then you will see some debug printed every time a request is
> >> received, and you weill be able to see if the requests are actuually
> reaching
> >> Radiator.
> >> If the requests are not even reaching the radius server, then you probably
> >> have
> >> a configuration issue with VOP. If they are reaching the radius server,
then
> >> the debug output should help you figure out whats happening to each
request.
> >> Hope that helps.
> >> Cheers.
> >>
> >>
> >>
> >>
> >>
> >> ===
> >> Archive at http://www.thesite.com.au/~radiator/
> >> To unsubscribe, email '[EMAIL PROTECTED]' with
> >> 'unsubscribe radiator' in the body of the message.
> >>-- End of excerpt from John Gray
> >
> >
> >
> >--
> >Mike McCauley [EMAIL PROTECTED]
> >Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
> >24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
> >Phone +61 3 9598-0985 Fax +61 3 9598-0955
> >
> >Radiator: the most portable, flexible and configurable RADIUS server
> >anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> >Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
> >NT, Rhapsody
>
>
> ===
> Archive at http://www.thesite.com.au/~radiator/
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>-- End of excerpt from John Gray
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
