the available messages which can be returned on mount are quite limited so sometimes the mapping of network errors on to the very limited set of available mount error messages can get confusing. Do you see mount generating any messages in dmesg? Alternatively, you might turn on cifs debugging (echo 7 > /proc/fs/cifs/cifsFYI) and try mount again and see if the warning message for the mount failure is listed (in dmesg) On Thu, Aug 18, 2011 at 11:31 AM, <bruce@xxxxxxxxxxxxxxx> wrote: > > Dear List, > I am running a 2.6.28 kernel that I have compiled with cifs filesystem > support. I am trying to mount a share from a windows 2008 server requiring > ntlmv2. when I try to pass the option sec=ntlmv2 or ntlmv2i I receive an > invalid argument message. If I omit the sec option I receive a permission > denied. > I have also tried to use a stock Debian kernel (2.6.32) that I have > checked to have cifs compiled in and I get the same results. If I perform > a 'modinfo cifs' it shows the module to be loaded and that I am running > ver 1.61 of cifs. > Is there any other components I need to check (do I need a library package > to support ntlmv2??) > I can mount shares of servers that allow NTLMv1. > > Any help gratefully received. > > Thanks Bruce > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-cifs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
