You can enable more detailed error messages by enabling cifs debug messages (before the mount) by "echo 7 > /proc/fs/cifs/cifsFYI" posix error 13 is the same as "access denied" One possible reason is that the domain of the server is not specified and that the default domain for that user differs from what you think (add something like "domain=yourserversdomain") On Sun, Aug 29, 2010 at 4:14 PM, Steve French <smfrench@xxxxxxxxx> wrote: > On Sun, Aug 29, 2010 at 3:52 PM, Rolf G. Økland <Rolf@xxxxxxxxxxx> wrote: >> Hi >> >> I got an annoying problem, when I'm trying to mount my Dreambox DM800 (Linux client) to a windows server 2008 R2 share I get access denied for some reason. >> This have been working like a charm on my old Windows 2003 Server, but not a chance in h. to my new 2008R2 server. >> I'm using this script on my DM800: "mount -t cifs //192.168.0.5/xdb.tv-serier -o udp,rw,nolock,wsize=8192,rsize=8192,user=myuser,pass=mypass /media/net/tv/" >> >> I also got a QNAP NMP-1000 that does mount to the same share on the windows 2008R2 without any issues what so ever. > > Various reasons reasons for access denied are possible. Looking at > the log (dmesg) might give you more information. > > Note that your mount options are a little strange (udp is meaningless > for cifs - cifs uses reliable connections via tcp only, and shrinking > rsize and wsize to 8192 (they default to 16K and 56K respectively for > Linux cifs.ko) usually degrades performance. In addition the mount > target (/media/net/tv) is harder to read when the mount options are > put in the middle between //server/share and the mount target. > > It is possible that your Windows 2008R2 share defaulted to ntlmv2, and > required packed signing (while your Windows 2003 was not configured > that way) - and that you have hit an old bug (it is hard to tell what > cifs version and kernel version you are running on the two systems). > > -- > Thanks, > > Steve > -- 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
