I see. Thank you very much.
-Original Message-
From: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] On
Behalf Of Heikki Vatiainen
Sent: Wednesday, August 19, 2015 3:42 PM
To: radiator@open.com.au
Subject: Re: [RADIATOR] davispolk.com: cannot login
On 08/19/2015 10:21
On 08/19/2015 10:21 PM, Qiu, Dennis wrote:
> TACACS+ users use port 49 on radiator server. But radiator server talks to
> Domain Controller to authenticate users.
>
> When radiator server talks to DC server, what protocol does it use?
Radiator calls the LSA API on the windows host it runs on.
Hekkie,
You did not answer my question.
TACACS+ users use port 49 on radiator server. But radiator server talks to
Domain Controller to authenticate users.
When radiator server talks to DC server, what protocol does it use?
Thank you.
-Original Message-
From: Heikki Vatiainen [mail
On 08/19/2015 07:45 PM, Qiu, Dennis wrote:
> We recently installed Windows updates on our domain controllers. Can you let
> me know what protocol Tacacs in radiator uses?
TACACS+ uses TCP between the TACACS+ client (switch, router, etc.) and
the TACACS+ server (Radiator). The default TCP port is
Heikki,
We recently installed Windows updates on our domain controllers. Can you let me
know what protocol Tacacs in radiator uses?
I see it uses RPC calls to domain controllers.
Thank you
Dennis Qiu
Information Systems
Davis Polk & Wardwell LLP
450 Lexington Avenue
New York, NY 10017
212 450
On 08/18/2015 10:16 PM, Qiu, Dennis wrote:
> Tue Aug 18 12:08:26 2015: DEBUG: New TacacsplusConnection created for
> 172.20.165.194:14854
> We see more than thousands of those lines in log. No one can login
> network device.
> After I restart Radius service, then it works again.
Hello Dennis,
