I found this in the release notes of the latest version (which is that I'm running):
https://github.com/inverse-inc/packetfence/releases/tag/v13.1.0 Cloud-ready NTLM authentication service PacketFence now provides its own NTLM authentication service - no longer relying on Samba nor requiring domain joins. EAP-PEAP authentications are now supported through the PacketFence Connector -- allowing Cloud-based deployments of PacketFence while maintaining support for this popular authentication mechanism. Is this why the ntlm-auth-api service won't start? (If so, why would the service still be included in the virtual appliance?) _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
