Re: Mounting a Windows Share
On Sunday 17 January 2016 21:48:48 Bob Holtzman wrote: > On Sun, Jan 17, 2016 at 03:59:57PM +0200, Moreanu Robert - Nicolae wrote: > > hi > > i'm looking to resolve this problem when I want to install debian 8.2 or > > 8.1. I receive this message after it's take to Grub install > > > > " the 'grub-pc' package failed to install into /target/ " > > after the operation of clean up on installing, i have a failed > > operations. > > > > i make the install of debian 8.2.0 or 8.1.0 from a dvd boot > > > > robert, waiting for your response > > Just how the hell many threads do you plan on hijacking!? Robert - You posted the same basic message three times in an hour to three different threads, two of them hijacked. Do please give people time to answer before posting again. And you will get more help if you start a thread initially, as you did, then stick to it. But don't re-post at 12:53:19, then 13:33:05 then 13:59:07 (times as recorded in GMT by my email client), if you want to get people to help rather than just annoy them. Lisi
Re: Mounting a Windows Share
On Sun, Jan 17, 2016 at 03:59:57PM +0200, Moreanu Robert - Nicolae wrote: > hi > i'm looking to resolve this problem when I want to install debian 8.2 or > 8.1. I receive this message after it's take to Grub install > > " the 'grub-pc' package failed to install into /target/ " > after the operation of clean up on installing, i have a failed operations. > > i make the install of debian 8.2.0 or 8.1.0 from a dvd boot > > robert, waiting for your response Just how the hell many threads do you plan on hijacking!?
Re: Mounting a Windows Share
hi i'm looking to resolve this problem when I want to install debian 8.2 or 8.1. I receive this message after it's take to Grub install " the 'grub-pc' package failed to install into /target/ " after the operation of clean up on installing, i have a failed operations. i make the install of debian 8.2.0 or 8.1.0 from a dvd boot robert, waiting for your response On Sun, Jan 17, 2016 at 3:49 PM, emmanuel segura wrote: > Sorry, > > The problem was solved using sec=ntlm > > 2016-01-17 11:26 GMT+01:00 Nemeth Gyorgy : > > 2016-01-17 00:48 keltezéssel, Steve Matzura írta: > >>> modprobe cifs maybe can help you. > >> > >> What is supposed to happen when I enter that command? All I got was > >> another shell prompt. > > > > After modprobe try mount again > > > > > > -- > > --- Friczy --- > > 'Death is not a bug, it's a feature' > > > > > > -- > .~. > /V\ > // \\ > /( )\ > ^`~'^ > > -- *o zi frumoasa !Robert - Nicolae MOREANU*
Re: Mounting a Windows Share
Sorry, The problem was solved using sec=ntlm 2016-01-17 11:26 GMT+01:00 Nemeth Gyorgy : > 2016-01-17 00:48 keltezéssel, Steve Matzura írta: >>> modprobe cifs maybe can help you. >> >> What is supposed to happen when I enter that command? All I got was >> another shell prompt. > > After modprobe try mount again > > > -- > --- Friczy --- > 'Death is not a bug, it's a feature' > -- .~. /V\ // \\ /( )\ ^`~'^
Re: Mounting a Windows Share
2016-01-17 00:48 keltezéssel, Steve Matzura írta: >> modprobe cifs maybe can help you. > > What is supposed to happen when I enter that command? All I got was > another shell prompt. After modprobe try mount again -- --- Friczy --- 'Death is not a bug, it's a feature'
Re: Mounting a Windows Share
Emanuel, On Sun, 17 Jan 2016 00:41:11 +0100, you wrote: >modprobe cifs maybe can help you. What is supposed to happen when I enter that command? All I got was another shell prompt.
Re: Mounting a Windows Share
modprobe cifs maybe can help you.
2016-01-16 22:02 GMT+01:00 Steve Matzura :
> After a reboot, one of my shares will no longer mount. And of course,
> it's the big one, the NAS box. Here is output from `strace mount.cifs
> //DISKSTATION1/BigVol1 /mnt/bigvol1 -o
> vers=2.1,username=***,password=*** (*** is real username and password
> covered up):
>
>
> execve("/sbin/mount.cifs", ["mount.cifs", "//DISKSTATION1/BigVol1",
> "/mnt/bigvol1", "-o", "vers=2.1,username=***,password"...], [/* 15
> vars */]) = 0
> brk(0) = 0x7f98fbf17000
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> directory)
> mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x7f98fa212000
> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=27175, ...}) = 0
> mmap(NULL, 27175, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f98fa20b000
> close(3)= 0
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> directory)
> open("/usr/lib/x86_64-linux-gnu/libcap-ng.so.0", O_RDONLY|O_CLOEXEC) =
> 3
> read(3,
> "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\25\0\0\0\0\0\0"...,
> 832) = 832
> fstat(3, {st_mode=S_IFREG|0644, st_size=22312, ...}) = 0
> mmap(NULL, 2117648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> 0) = 0x7f98f9be3000
> mprotect(0x7f98f9be7000, 2097152, PROT_NONE) = 0
> mmap(0x7f98f9de7000, 8192, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7f98f9de7000
> close(3)= 0
> access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
> directory)
> open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
> read(3,
> "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"...,
> 832) = 832
> fstat(3, {st_mode=S_IFREG|0755, st_size=1729984, ...}) = 0
> mmap(NULL, 3836448, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
> 0) = 0x7f98f983a000
> mprotect(0x7f98f99d9000, 2097152, PROT_NONE) = 0
> mmap(0x7f98f9bd9000, 24576, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19f000) = 0x7f98f9bd9000
> mmap(0x7f98f9bdf000, 14880, PROT_READ|PROT_WRITE,
> MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f98f9bdf000
> close(3)= 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x7f98fa20a000
> mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x7f98fa208000
> arch_prctl(ARCH_SET_FS, 0x7f98fa208740) = 0
> mprotect(0x7f98f9bd9000, 16384, PROT_READ) = 0
> mprotect(0x7f98f9de7000, 4096, PROT_READ) = 0
> mprotect(0x7f98fa214000, 4096, PROT_READ) = 0
> mprotect(0x7f98fa009000, 4096, PROT_READ) = 0
> munmap(0x7f98fa20b000, 27175) = 0
> geteuid() = 0
> getpid()= 1580
> capget({0 /* _LINUX_CAPABILITY_VERSION_??? */, 0}, NULL) = 0
> gettid()= 1580
> open("/proc/sys/kernel/cap_last_cap", O_RDONLY) = 3
> read(3, "37\n", 7) = 3
> brk(0) = 0x7f98fbf17000
> brk(0x7f98fbf38000) = 0x7f98fbf38000
> capget({_LINUX_CAPABILITY_VERSION_3, 1580},
> {CAP_CHOWN|CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|CAP_SETUID|CAP_SETPCAP|CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|CAP_NET_BROADCAST|CAP_NET_admin|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|CAP_SYS_MODULE|CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|CAP_SYS_PACCT|CAP_SYS_ADMIN|CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|CAP_SYS_TIME|CAP_SYS_TTY_CONFIG|CAP_MKNOD|CAP_LEASE|CAP_AUDIT_WRITE|CAP_AUDIT_CONTROL|CAP_SETFCAP,
> CAP_CHOWN|CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|CAP_SETUID|CAP_SETPCAP|CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|CAP_NET_BROADCAST|CAP_NET_ADMIN|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|CAP_SYS_MODULE|CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|CAP_SYS_PACCT|CAP_SYS_ADMIN|CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|CAP_SYS_TIME|CAP_SYS_TTY_CONFIG|CAP_MKNOD|CAP_LEASE|CAP_AUDIT_WRITE|CAP_AUDIT_CONTROL|CAP_SETFCAP,
> 0}) = 0
> open("/proc/1580/status", O_RDONLY|O_CLOEXEC) = 4
> fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0x7f98fa211000
> read(4, "Name:\tmount.cifs\nState:\tR (runni"..., 1024) = 783
> close(4)= 0
> munmap(0x7f98fa211000, 4096)= 0
> prctl(PR_CAPBSET_DROP, 0, 0, 0, 0) = 0
> prctl(PR_CAPBSET_DROP, 0x1, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x2, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x3, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x4, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x5, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x6, 0, 0, 0)= 0
> prctl(PR_CAPBSET_DROP, 0x7, 0, 0, 0)= 0
Re: Mounting a Windows Share
After a reboot, one of my shares will no longer mount. And of course,
it's the big one, the NAS box. Here is output from `strace mount.cifs
//DISKSTATION1/BigVol1 /mnt/bigvol1 -o
vers=2.1,username=***,password=*** (*** is real username and password
covered up):
execve("/sbin/mount.cifs", ["mount.cifs", "//DISKSTATION1/BigVol1",
"/mnt/bigvol1", "-o", "vers=2.1,username=***,password"...], [/* 15
vars */]) = 0
brk(0) = 0x7f98fbf17000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f98fa212000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=27175, ...}) = 0
mmap(NULL, 27175, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f98fa20b000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/usr/lib/x86_64-linux-gnu/libcap-ng.so.0", O_RDONLY|O_CLOEXEC) =
3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@\25\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=22312, ...}) = 0
mmap(NULL, 2117648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f98f9be3000
mprotect(0x7f98f9be7000, 2097152, PROT_NONE) = 0
mmap(0x7f98f9de7000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7f98f9de7000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1729984, ...}) = 0
mmap(NULL, 3836448, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x7f98f983a000
mprotect(0x7f98f99d9000, 2097152, PROT_NONE) = 0
mmap(0x7f98f9bd9000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19f000) = 0x7f98f9bd9000
mmap(0x7f98f9bdf000, 14880, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f98f9bdf000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f98fa20a000
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f98fa208000
arch_prctl(ARCH_SET_FS, 0x7f98fa208740) = 0
mprotect(0x7f98f9bd9000, 16384, PROT_READ) = 0
mprotect(0x7f98f9de7000, 4096, PROT_READ) = 0
mprotect(0x7f98fa214000, 4096, PROT_READ) = 0
mprotect(0x7f98fa009000, 4096, PROT_READ) = 0
munmap(0x7f98fa20b000, 27175) = 0
geteuid() = 0
getpid()= 1580
capget({0 /* _LINUX_CAPABILITY_VERSION_??? */, 0}, NULL) = 0
gettid()= 1580
open("/proc/sys/kernel/cap_last_cap", O_RDONLY) = 3
read(3, "37\n", 7) = 3
brk(0) = 0x7f98fbf17000
brk(0x7f98fbf38000) = 0x7f98fbf38000
capget({_LINUX_CAPABILITY_VERSION_3, 1580},
{CAP_CHOWN|CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|CAP_SETUID|CAP_SETPCAP|CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|CAP_NET_BROADCAST|CAP_NET_admin|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|CAP_SYS_MODULE|CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|CAP_SYS_PACCT|CAP_SYS_ADMIN|CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|CAP_SYS_TIME|CAP_SYS_TTY_CONFIG|CAP_MKNOD|CAP_LEASE|CAP_AUDIT_WRITE|CAP_AUDIT_CONTROL|CAP_SETFCAP,
CAP_CHOWN|CAP_DAC_OVERRIDE|CAP_DAC_READ_SEARCH|CAP_FOWNER|CAP_FSETID|CAP_KILL|CAP_SETGID|CAP_SETUID|CAP_SETPCAP|CAP_LINUX_IMMUTABLE|CAP_NET_BIND_SERVICE|CAP_NET_BROADCAST|CAP_NET_ADMIN|CAP_NET_RAW|CAP_IPC_LOCK|CAP_IPC_OWNER|CAP_SYS_MODULE|CAP_SYS_RAWIO|CAP_SYS_CHROOT|CAP_SYS_PTRACE|CAP_SYS_PACCT|CAP_SYS_ADMIN|CAP_SYS_BOOT|CAP_SYS_NICE|CAP_SYS_RESOURCE|CAP_SYS_TIME|CAP_SYS_TTY_CONFIG|CAP_MKNOD|CAP_LEASE|CAP_AUDIT_WRITE|CAP_AUDIT_CONTROL|CAP_SETFCAP,
0}) = 0
open("/proc/1580/status", O_RDONLY|O_CLOEXEC) = 4
fstat(4, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x7f98fa211000
read(4, "Name:\tmount.cifs\nState:\tR (runni"..., 1024) = 783
close(4)= 0
munmap(0x7f98fa211000, 4096)= 0
prctl(PR_CAPBSET_DROP, 0, 0, 0, 0) = 0
prctl(PR_CAPBSET_DROP, 0x1, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x2, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x3, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x4, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x5, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x6, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x7, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x8, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0x9, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0xa, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0xb, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0xc, 0, 0, 0)= 0
prctl(PR_CAPBSET_DROP, 0xd, 0
Re: Mounting a Windows Share
On Sat, 2 Jan 2016 18:10:19 -0500, you wrote: >There are lots of things that can go wrong. What I found worked recently >when I had a similar problem was: > >#mount -t cifs -o username=,password= >//192.168.1.19/images /mnt/images > >Using the DNS name returned errors but the IP address of the Windows box >worked. That one gave me an error 5, input/output error. I changed back from the address to the DNS name and got error 13. It's a problem on the sharing computer's side. I'll fix it and report.
Re: Mounting a Windows Share
On 02/01/16 05:24 PM, Steve Matzura wrote: On Sat, 02 Jan 2016 16:52:54 -0500, you wrote: The correct mount options are half of what you're actually asking about in this thread, so we should settle those out by the time the thread is done with. For the "dump" and "pass" columns, in my experience 99% of the time they can and should be left as zeroes. (This might be the default, I'm not sure. I've always specified them anyway.) I put them in as 0, still no soap. If you're running that command as root, the fstab entry should not be necessary; if you're running it as non-root, IIRC the "specify both mount point and device to mount" will be rejected as "only root can do that". Either way, this doesn't look quite right. I'm running it as root all right. I also tried '-o user="Steve Matzura"' and got the error 13. After trying to access the share on another Windows machine, I am now sure this is *NOT* a Linux problem though because I can't even get into it from another Windows machine, which means I have set up the share incorrectly. I'll work on that and report. Also, check lusrmgr.msc (or equivalent) on the Windows box, to make sure you're using the actual internal Windows username; at least in my experience, it's pretty rare for a Windows username to have a space in it, although the _display_ name often will. It says that's the username, just as I typed it when I installed it. There are lots of things that can go wrong. What I found worked recently when I had a similar problem was: #mount -t cifs -o username=,password= //192.168.1.19/images /mnt/images Using the DNS name returned errors but the IP address of the Windows box worked.
Re: Mounting a Windows Share
On Sat, 02 Jan 2016 16:52:54 -0500, you wrote: >The correct mount options are half of what you're actually asking about >in this thread, so we should settle those out by the time the thread is >done with. > >For the "dump" and "pass" columns, in my experience 99% of the time they >can and should be left as zeroes. (This might be the default, I'm not >sure. I've always specified them anyway.) I put them in as 0, still no soap. >>> If you're running that command as root, the fstab entry should not >>> be necessary; if you're running it as non-root, IIRC the "specify >>> both mount point and device to mount" will be rejected as "only >>> root can do that". Either way, this doesn't look quite right. >> >> I'm running it as root all right. I also tried '-o user="Steve Matzura"' and got the error 13. After trying to access the share on another Windows machine, I am now sure this is *NOT* a Linux problem though because I can't even get into it from another Windows machine, which means I have set up the share incorrectly. I'll work on that and report. >Also, check lusrmgr.msc (or equivalent) on the Windows box, to make sure >you're using the actual internal Windows username; at least in my >experience, it's pretty rare for a Windows username to have a space in >it, although the _display_ name often will. It says that's the username, just as I typed it when I installed it.
Re: Mounting a Windows Share
On Sat, 02 Jan 2016 16:15:20 -0500
Steve Matzura wrote:
> Nothing that complicated. Just a default system username, which is my
> name, and no login password. I tried:
>
> -o user="Steve Matzura",pass=""
>
Something you might try, if you can organise it: use the same username
and password on client and server, make sure the mounting user has
appropriate permissions on the share (both share permissions and file
ACLs apply) and with luck you won't need to specify anything in advance.
This works with Windows clients ('pass-through authentication') even
between computers and domains which have no trust relationship, but I've
no idea how closely the current Samba client replicates Windows
behaviour.
--
Joe
Re: Mounting a Windows Share
On 02/01/16 02:47 PM, Steve Matzura wrote: I have a Windows machine called 'box' with a directory called 'users' which is shared publicly with no access username or password as 'users2'. On my Jessie system, I created the mount point successfully: mkdir -p /mnt/users I then installed the cifs-utils package as instructed by a Website with a fairly up-to-date article on how to do all of this. In /etc/fstab, as directed by the same article, I have placed the line: //box/users2 /mnt/users cifs I am now trying to mount the Windows share like this: mount -t cifs //box/users2 /mnt/users The system responds: mount error(13): Permission denied Is there a default username and password I'm supposed to use, like maybe the Windows network password, or something else perhaps? Before fiddling around with /etc/fstab. get it to work from the command line.
Re: Mounting a Windows Share
On 02/01/16 04:15 PM, Steve Matzura wrote: On Sat, 02 Jan 2016 15:00:31 -0500, The Wanderer wrote: I presume that the user as which you are attempting to run the later mount command has write and execute permission on this new directory. Yes. It's root, which means it's me, as I'm the only one fooling with this at the moment. Don't mount things as root. Give the mount point a normal user/group. Try chgrp users /mnt/users In /etc/fstab, as directed by the same article, I have placed the line: //box/users2 /mnt/users cifs That looks incomplete to me; it doesn't seem to specify the mount options, or the usual zero values for the "dump" and "pass" columns. You're right. I knew they were missing, but the article that instructed me on how to modify fstab didn't explain what the two 0's at the end of the line are for, so I omitted them, hoping an error message would give me a clue as to what I should put in their places. The full line should be something like: //box/users2 /mnt/users cifs user,username= 0 0 If you're running that command as root, the fstab entry should not be necessary; if you're running it as non-root, IIRC the "specify both mount point and device to mount" will be rejected as "only root can do that". Either way, this doesn't look quite right. I'm running it as root all right. I just now tried: mount -t cifs //box/users2 /mnt/share -o username:"Steve Matzura" and got back: Username specified with no parameter That syntax is invalid. You'd need something like -o username="Steve Matzura", assuming Steve Matzura is a valid username. The system responds: mount error(13): Permission denied Is there a default username and password I'm supposed to use, like maybe the Windows network password, or something else perhaps? You most likely need the username and password of a user account on the Windows box which can access that directory; you may also need to configure the Windows share to specifically grant that user account access to the share. With that done, you will need to specify those credentials in the mount command, with the '-o user=' option. (Technically what you need is a user account on the appropriate _domain_, but for a non-domain-joined Windows computer the "domain" is the name of the computer, and AFAIK does not need to be specified separately. If this computer _is_ domain-joined and you log in to it with a domain account, you will probably need to specify the domain in the mount command as well.) Nothing that complicated. Just a default system username, which is my name, and no login password. I tried: -o user="Steve Matzura",pass="" Probably not a valid user name.
Re: Mounting a Windows Share
On 2016-01-02 at 16:15, Steve Matzura wrote: > On Sat, 02 Jan 2016 15:00:31 -0500, The Wanderer > wrote: >>> In /etc/fstab, as directed by the same article, I have placed >>> the line: >>> >>> //box/users2 /mnt/users cifs >> >> That looks incomplete to me; it doesn't seem to specify the mount >> options, or the usual zero values for the "dump" and "pass" >> columns. > > You're right. I knew they were missing, but the article that > instructed me on how to modify fstab didn't explain what the two 0's > at the end of the line are for, so I omitted them, hoping an error > message would give me a clue as to what I should put in their > places. The correct mount options are half of what you're actually asking about in this thread, so we should settle those out by the time the thread is done with. For the "dump" and "pass" columns, in my experience 99% of the time they can and should be left as zeroes. (This might be the default, I'm not sure. I've always specified them anyway.) >> If you're running that command as root, the fstab entry should not >> be necessary; if you're running it as non-root, IIRC the "specify >> both mount point and device to mount" will be rejected as "only >> root can do that". Either way, this doesn't look quite right. > > I'm running it as root all right. I just now tried: > > mount -t cifs //box/users2 /mnt/share -o username:"Steve Matzura" > > and got back: > > Username specified with no parameter Try it with '-o username=' instead of '-o username:'. Also, check lusrmgr.msc (or equivalent) on the Windows box, to make sure you're using the actual internal Windows username; at least in my experience, it's pretty rare for a Windows username to have a space in it, although the _display_ name often will. (Approximate GUI way to get there: right-click on "Computer" or "My Computer" or your Windows version's equivalent, click "Manage", expand "Local Users and Groups", click "Users". Win8 and/or Win10 may have changed this, I haven't had much experience with them yet.) >>> The system responds: >>> >>> mount error(13): Permission denied >>> >>> Is there a default username and password I'm supposed to use, >>> like maybe the Windows network password, or something else >>> perhaps? >> >> You most likely need the username and password of a user account on >> the Windows box which can access that directory; you may also need >> to configure the Windows share to specifically grant that user >> account access to the share. With that done, you will need to >> specify those credentials in the mount command, with the '-o user=' >> option. >> >> (Technically what you need is a user account on the appropriate >> _domain_, but for a non-domain-joined Windows computer the "domain" >> is the name of the computer, and AFAIK does not need to be >> specified separately. If this computer _is_ domain-joined and you >> log in to it with a domain account, you will probably need to >> specify the domain in the mount command as well.) > > Nothing that complicated. Just a default system username, which is > my name, and no login password. I tried: > > -o user="Steve Matzura",pass="" In my experience, you don't need to specify the password in the command line (although you might need it in the fstab for non-root mounting, which would be a leak if the file is world-readable); if you don't specify it, mount will prompt you for a password. (The environment from which I most commonly do my *nix CIFS mounts has older tools and doesn't accept '-o username=', but does accept '-o user='. The latter is not recommended if the former works.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Mounting a Windows Share
On Sat, 02 Jan 2016 15:00:31 -0500, The Wanderer wrote: >I presume that the user as which you are attempting to run the later >mount command has write and execute permission on this new directory. Yes. It's root, which means it's me, as I'm the only one fooling with this at the moment. >> In /etc/fstab, as directed by the same article, I have placed the >> line: >> >> //box/users2 /mnt/users cifs > >That looks incomplete to me; it doesn't seem to specify the mount >options, or the usual zero values for the "dump" and "pass" columns. You're right. I knew they were missing, but the article that instructed me on how to modify fstab didn't explain what the two 0's at the end of the line are for, so I omitted them, hoping an error message would give me a clue as to what I should put in their places. >If you're running that command as root, the fstab entry should not be >necessary; if you're running it as non-root, IIRC the "specify both >mount point and device to mount" will be rejected as "only root can do >that". Either way, this doesn't look quite right. I'm running it as root all right. I just now tried: mount -t cifs //box/users2 /mnt/share -o username:"Steve Matzura" and got back: Username specified with no parameter >> The system responds: >> >> mount error(13): Permission denied >> >> Is there a default username and password I'm supposed to use, like >> maybe the Windows network password, or something else perhaps? > >You most likely need the username and password of a user account on the >Windows box which can access that directory; you may also need to >configure the Windows share to specifically grant that user account >access to the share. With that done, you will need to specify those >credentials in the mount command, with the '-o user=' option. > >(Technically what you need is a user account on the appropriate >_domain_, but for a non-domain-joined Windows computer the "domain" is >the name of the computer, and AFAIK does not need to be specified >separately. If this computer _is_ domain-joined and you log in to it >with a domain account, you will probably need to specify the domain in >the mount command as well.) Nothing that complicated. Just a default system username, which is my name, and no login password. I tried: -o user="Steve Matzura",pass=""
Re: Mounting a Windows Share
On 2016-01-02 at 14:47, Steve Matzura wrote: > I have a Windows machine called 'box' with a directory called > 'users' which is shared publicly with no access username or password > as 'users2'. On my Jessie system, I created the mount point > successfully: > > mkdir -p /mnt/users I presume that the user as which you are attempting to run the later mount command has write and execute permission on this new directory. > I then installed the cifs-utils package as instructed by a Website > with a fairly up-to-date article on how to do all of this. > > In /etc/fstab, as directed by the same article, I have placed the > line: > > //box/users2 /mnt/users cifs That looks incomplete to me; it doesn't seem to specify the mount options, or the usual zero values for the "dump" and "pass" columns. This may be valid fstab syntax, but it's not a variant I remember having seen. > I am now trying to mount the Windows share like this: > > mount -t cifs //box/users2 /mnt/users As which user? If you're running that command as root, the fstab entry should not be necessary; if you're running it as non-root, IIRC the "specify both mount point and device to mount" will be rejected as "only root can do that". Either way, this doesn't look quite right. > The system responds: > > mount error(13): Permission denied > > Is there a default username and password I'm supposed to use, like > maybe the Windows network password, or something else perhaps? You most likely need the username and password of a user account on the Windows box which can access that directory; you may also need to configure the Windows share to specifically grant that user account access to the share. With that done, you will need to specify those credentials in the mount command, with the '-o user=' option. (Technically what you need is a user account on the appropriate _domain_, but for a non-domain-joined Windows computer the "domain" is the name of the computer, and AFAIK does not need to be specified separately. If this computer _is_ domain-joined and you log in to it with a domain account, you will probably need to specify the domain in the mount command as well.) I routinely mount Windows-server CIFS shares on my work laptop with commands like: mount -t cifs -o user=username,domain=SHORTDOMAIN //server/sharename /mnt/cifs/sharename where 'username' is the name of the user account which I use when logging on to the Windows machine, and SHORTDOMAIN is the all-caps name of the Windows domain, analogous to the "workgroup" name (and not to be confused with the dotted hierarchical name). -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Mounting a Windows Share
I have a Windows machine called 'box' with a directory called 'users' which is shared publicly with no access username or password as 'users2'. On my Jessie system, I created the mount point successfully: mkdir -p /mnt/users I then installed the cifs-utils package as instructed by a Website with a fairly up-to-date article on how to do all of this. In /etc/fstab, as directed by the same article, I have placed the line: //box/users2 /mnt/users cifs I am now trying to mount the Windows share like this: mount -t cifs //box/users2 /mnt/users The system responds: mount error(13): Permission denied Is there a default username and password I'm supposed to use, like maybe the Windows network password, or something else perhaps?
