I've been running the RedHat "version" of FreeRADIUS Version 2.1.3 for a few years. Each morning I update the users authorization file and run "service radius reload" for the changes to take affect. I recently patched the system, which updated FreeRADIUS to version 2.1.12. I find now that after reloading, using the same script, it appears to reload successfully but my authentications (through ntlm_auth to an MS AD) begin failing. If I instead use "service radiusd restart", it's fine. Did anything change between versions that would explain this? Oct 5 07:30:02 radserv radiusd[3825]: Login OK: [xxxx] (from client wlc-7 port 0 via TLS tunnel) Oct 5 07:30:02 radserv radiusd[3825]: Login OK: [xxxxx] (from client wlc-7 port 13 cli 6c-c2-6b-98-06-52) Oct 5 07:30:02 radserv radiusd[15741]: Loaded virtual server <default> Oct 5 07:30:02 radserv radiusd[15741]: Loaded virtual server inner-tunnel Oct 5 07:30:02 radserv radiusd[15741]: ... adding new socket proxy address * port 0 Oct 5 07:30:02 radserv radiusd[3825]: Received HUP signal. Oct 5 07:30:02 radserv radiusd[3825]: HUP - Re-reading configuration files Oct 5 07:30:02 radserv radiusd[3825]: HUP - loading modules Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "radutmp" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "suffix" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "attr_filter.access_reject" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "attr_filter.accounting_response" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "detail" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "mschap" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "pap" Oct 5 07:30:02 radserv radiusd[3825]: Module: Reloaded module "files" Oct 5 07:30:02 radserv radiusd[3825]: Loaded virtual server <default> Oct 5 07:30:02 radserv radiusd[3825]: Loaded virtual server inner-tunnel Oct 5 07:30:04 radserv radiusd[3825]: Login incorrect (mschap: External script says ): [xxxxx] (from client wlc-6 port 0 via TLS tunnel) Oct 5 07:30:04 radserv radiusd[3825]: Login incorrect: [xxxxx] (from client wlc-6 port 13 cli 00-26-08-e6-13-90) Oct 5 07:30:04 radserv radiusd[3825]: Login incorrect (mschap: External script says ): [xxxxx] (from client wlc-7 port 0 via TLS tunnel) Oct 5 07:30:04 radserv radiusd[3825]: Login incorrect: [xxxx] (from client wlc-7 port 13 cli 7c-11-be-c3-20-72) Oct 5 07:30:05 radserv radiusd[3825]: Login incorrect (mschap: External script says ): [xxxxx] (from client wlc-6 port 0 via TLS tunnel) Oct 5 07:30:05 radserv radiusd[3825]: Login incorrect: [xxxxx] (from client wlc-6 port 13 cli 48-60-bc-f4-1d-31) Oct 5 07:30:07 radserv radiusd[3825]: Login incorrect (mschap: External script says ): [xxxxx] (from client wlc-7 port 0 via TLS tunnel) Oct 5 07:30:07 radserv radiusd[3825]: Login incorrect (mschap: External script says ): [xxxxxx] (from client wlc-6 port 0 via TLS tunnel) Oct 5 07:30:07 radserv radiusd[3825]: Login incorrect: [xxxx] (from client wlc-6 port 13 cli 48-60-bc-f4-1d-31) -Mike