I am running a script which checks to see that the authentication process is going well - the script attempts an NTLM authentication and if it fails it restarts Winbind and tests again.

I started receiving The error Exec-Program output: Reading winbind reply failed! (0xc0000001) after WInbind restarts.

Chances are that it's reset the permissions of the pipe that ntlm_auth needs to use. Add the FR user (freerad or radiusd) to the same group that winbind runs as (winbindd probably). Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet Lumen House, Library Avenue, Harwell Oxford, Didcot, OX11 0SG jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. Jisc Collections and Janet Ltd. is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under Company No. number 2881024, VAT No. GB 197 0632 86. The registered office is: Lumen House, Library Avenue, Harwell, Didcot, Oxfordshire, OX11 0SG. T 01235 822200.

On Tue, Mar 10, 2015 at 10:41:51AM +0000, Clement Ogedengbe wrote:

I am seeing lots of " Exec-Program output: Reading winbind reply failed! (0xc0000001)" in the log and all users are being rejected.

Let me guess, this happens around every hour when students move between lectures?

I am running a script which checks to see that the authentication process is going well - the script attempts an NTLM authentication and if it fails it restarts Winbind and tests again.

OK

I started receiving The error Exec-Program output: Reading winbind reply failed! (0xc0000001) after WInbind restarts.

You'll see that while winbind restarts, as there is nothing to send the response. But it should only be transient, and should return to normal a few seconds later. But you could get lots in the log. If it keeps going you may have other problems, or e.g. permission set wrong on the winbind privileged socket. Does ntlm_auth --username=user --domain=domain --password=password return success when run as the same user that FreeRADIUS runs as? Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>