I know I am chiming in her rather late, but I have had problems in the past mounting my Buffalo NAS from Linux. This is what I have in my fstab -

//192.168.25.3/USB_Storage /mnt/readyshare cifs rw,nounix,dom=PMI,user=xxxxxxx,password=xxxxxxxxx,uid=mark,gid=mark,file_mode=0644,dir_mode=0755  0  0

Check your syslog and/or dmesg when you mount. I had errors in the logs even though I could read and write the NAS drive. I found that I needed the nounix command to get rid of some of the errors.

This error:
[2480664.321842]  CIFS VFS: Send error in SETFSUnixInfo = -5
[2480664.321870]  CIFS VFS: Negotiating Unix capabilities with the server failed.  Consider mounting with the Unix Extensions
[2480664.321873] disabled, if problems are found, by specifying the nounix mount option.

needed nounix to stop this error.

I still get lots of these after using nounix (note the time stamps)
[Fri Aug 23 08:42:20 2013] CIFS VFS: Received no data, expecting 4
[Fri Aug 23 08:44:20 2013] CIFS VFS: Received no data, expecting 4
[Fri Aug 23 08:46:20 2013] CIFS VFS: Received no data, expecting 4

From what I have read on Google searches for this error, I have to wait for Linux 3.2 to remove these errors. I am using Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (ben@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) on one machine and Linux version 2.6.32-5-686 (Debian 2.6.32-48squeeze3) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) on another machine and both exhibit this error. But transferring files works.

Mark

On Fri, Aug 23, 2013 at 9:18 AM, Matt Graham <mhgraham@crow202.org> wrote:

On 08/22/2013 10:55 PM, Wayne Davis wrote:

IT FRIGGIN WORKS!

Yay!

I had to do a bit more investigating, BUT at least you gave the foundation
Matt!   I thank EVERYONE involved.  It was a road to get here, but HERE I AM.

sudo mount.cifs -o sec=ntlm,username=XXXX,password=XXXX  //<IPADDRESS>/SHARE /mnt/other

This is actually a bit odd.  sec=ntlm is the default setting here on this older CentOS box.  I wonder if they've changed the default setting to sec=ntlm2 on the most recent Samba packages or something.  (NTLM2 is only available on recent 'Doze machines IIRC, while NTLM has been available for a very long time.)

I went back to the NAS and set it to "public".  Now I do not need
the USER/PASS

This is less secure, but if this is only available to your home network, convenience may be more important than security.

It wound up being SO simple and I knew it was...

Many things are when you know all the stuff that's happening.  "The password for this automated job is 'password509'."  Fat-finger this as 'password508'.  Spend a long time wondering why the automated job isn't working, because the error messages from the job failing are being sent to someone who isn't me who's wondering why they're getting fail mail.

Matt, if you're ever up here in North Phoenix, let me buy you
a beer or 3  (Cave Creek Rd /Union Hills area)   IF your old
enough to do so of course....

That's a bit of a ways to go for me (Tempe, south of ASU) but I'll keep it in mind if I'm ever out there.  I remember using Logo on an Apple //c without a color monitor in the 1980s, so I'm probably old enough :-) .

--
Crow202 Blog: http://crow202.org/wordpress
There is no Darkness in Eternity
But only Light too dim for us to see.

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss