Hi Joe, Everywhere on the net it's told do turn off SElinux in case of problems... so i was making sure nobody was going to ask that. I actually used 'setenforce 0' to confirm it was not the cause.
Nalin's hint on allow_weak_crypto solved this issue, thaks a lot. []s, Fernando Lozano >---- Original Message ---- >From: Joe Zeff <[email protected]> >To: "Community support for Fedora users" <[email protected]> >Sent: Qui, Abr 7, 2011, 13:40 PM >Subject: Re: nsfs4 client with kerberos > >On 04/07/2011 09:24 AM, [email protected] wrote: >> and tried disabling SELinux and flusing iptables rules to no effect. > >What made you think SELinux was at fault? Did it report problems? Try >turning it back on and making sure it's set to notify you of any issues, >then try again. If you don't get any SELinux alerts, it's not involved. >-- >users mailing list >[email protected] >To unsubscribe or change subscription options: >https://admin.fedoraproject.org/mailman/listinfo/users >Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- users mailing list [email protected] To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
