OMG OMG OMG OMG OMG OMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMGGGGGGGGGGGGGGGGGG! IT FRIGGIN WORKS! 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. THIS is what ultimately worked: *sudo mount.cifs -o sec=ntlm,username=xxxx,password=xxxx ///SHARE /mnt/other* If omit sudo, it needs to be in the fstab I went back to the NAS and set it to "public". Now I do not need the USER/PASS so it is now: *sudo mount.cifs -o sec=ntlm ///SHARE /mnt/other* These things must use NT Lanmangler security protocols? It wound up being SO simple and I knew it was... Being CLUELESS SUCKS. 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.... otherwise, its milk & cookies for you my friend, TOLL HOUSE, not some cheap store-bought crap. ;-) WOW, I,m am SOOOOOoooooooooooooooo happy right now. :-) :-) ;-) :-P :-D ....8-) On 08/22/2013 03:13 PM, Matt Graham wrote: >> On 08/21/2013 07:37 PM, James Dugger wrote: >>> Sorry for the confusion. Based on your description, the WD >>> N750 router is acting as a NAS (Network Sttached Storage) > > Is this true? If the router/whatever is serving stuff over SMB, then > you don't need Samba, you need mount.cifs . > > On 2013-08-22 14:45, ChasM Marshall wrote: >> If the NAS box is requesting a password, something is weird. You said >> it has no Win restrictions. >> Your NAS device must have a Linux device name. >> Because it is a router, I think it is connected on the Linux device >> named "/dev/eth0". > > This is ... flawed. First off, ethernet interfaces have not had > device nodes in Linux for a long time unless you're doing TUN/TAP or > something like that. Second, a SMB server has a name associated with > it, but it doesn't have an associated device node. DNS, NetBIOS, or > IP addresses are what the mount.cifs things use to talk to the remote > server. > > If you know this device's IP address, you could try something like this: > > smbclient -L 192.168.X.Y > (should give you a list of all the services that are on 192.168.X.Y) > > mkdir /mnt/other > mount -t cifs //192.168.X.Y/SHARE /mnt/other > > SHARE needs to be a filesystem share that the device is making > available. In many environments, you usually need to add "-o > user=USER,domain=DOMAIN" to the above mount command so that the server > knows you're using the correct username and domain. If guest access > is available, you may not need "user=guest", but that's something to > try if the first try doesn't work. >