Can anybody tell me how to insert the Realm of a failed access, into de
Logfile name, just to differentiate diverse users in diverse logfiles?

Inserting this clause in the cfg file isn�t working:

<Log FILE>
       Filename %L/%u_logfile%f%g%i
       Trace 3
</Log>

as it nevers catches the user name, and, whoever fails in accessing, I only
get a _logfile20010104 file....

Thanks in avance

Javier Benita

-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]En nombre
de Hugh Irvine
Enviado el: jueves, 04 de enero de 2001 9:32
Para: [EMAIL PROTECTED]
Asunto: (RADIATOR) Fwd: RE: Fwd: Problem Radiator & W2000 Server


Hello everyone -

I thought this would be useful for anyone with W2K server.

regards

Hugh

----------  Forwarded Message  ----------
Subject: RE: Fwd: Problem Radiator & W2000 Server
Date: Thu, 04 Jan 2001 08:36:04 +0100
From: "Boer, A.P. de (Alexander)" <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>


Hello Hugh,

Many thanks for your swift response. It helped me to discover that Microsoft
IAS service was using the well-known port numbers 1645/1646. Radiator is
doing fine again.

With best regards,

Alexander

-----Original Message-----
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: donderdag 4 januari 2001 6:21
To: Boer, A.P. de (Alexander)
Cc: [EMAIL PROTECTED]
Subject: Re: Fwd: Problem Radiator & W2000 Server



Hello Alexander -

> >Dear Sir,
> >
> >After migrating the Radiator software to a 'clean' installed W2000 Server
> >platform I am encountering serious problems. 'Radiusd' responds with the
> >following error message:
> >
> >Could not bind authentication socket: Unknown error at radiusd line 339
> >
> >I running ActivePerl 5.6.0 build 613. Previously Radiator (2.17.1) was
> > doing fine under W2000 Professional. Unfortunately I'm now forced to

move

> > to W2000 Server, raising this compatibility issue.
> >
> >I would be grateful if you can provide me with some hints how to solve
> > this problem.

This is usually caused by another service already running on the radius port

number that you have set in your configuration file. Microsoft now includes
a
radius server in the Win2k server. Otherwise, the port has not been freed up

by the system after a service has been shutdown - it seems to take a longish

time - up to 15 minutes or so.

hth

Hugh


--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

-------------------------------------------------------

--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.

===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.


===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to