* Steve Matzura [2016-01-10 11:19 -0500]:
> On Sun, 10 Jan 2016 14:48:55 +0100, Sven wrote:
>
> >You might want to check /var/log/messages for more verbose error
> >message.
>
> In three days, this is all messages has in it:
[...]
Well, that sould be /var/log/syslog.
On Sat, 2016-01-09 at 17:00 -0500, Steve Matzura wrote:
> Mea culpa. I didn't read far enough down the page.
It was quite easy to miss. I will try to remember to quote the relevant
parts in the message to the list, instead of just adding the URL.
After all, web sites change and can become
On Sat, 2016-01-09 at 17:00 -0500, Steve Matzura wrote:
> Mea culpa. I didn't read far enough down the page.
>
> After trying `vers=2.1', now I get error 13, permission denied.
> Getting closer. Now it's probably a username or password problem, but
> the Windows account has no password. I suppose
On Sunday 10 January 2016 02:31:54 Steve Matzura wrote:
> Let me rephrase/clarify that. There are lots of things on which
> screenreaders can be blamed, but this one wasn't one of them.
>
> On Sat, 09 Jan 2016 20:49:59 -0500, you wrote:
> >On Sat, 9 Jan 2016 22:46:20 +, Lisi wrote:
> >>On
On Sun, 10 Jan 2016 14:48:55 +0100, Sven wrote:
>You might want to check /var/log/messages for more verbose error
>message.
In three days, this is all messages has in it:
Jan 8 06:25:02 pugville rsyslogd: [origin software="rsyslogd"
swVersion="8.4.2" x-pid="569"
I added the "Everyone" username object to the list of those permitted
to access the drives, and it worked. No username or password required.
Now I have to get it into fstab and I'm totally done with system
setup!
On Sat, 9 Jan 2016 21:05:40 +
Joe wrote:
>
> And as I've said, Windows clients will silently use the current user's
> credentials if they are accepted by the server, and only request
> credentials if they are not. I don't know if mount.cifs tries this.
>
A moment's
On Sat, 9 Jan 2016 21:05:40 +, Joe wrote:
>> I've not heard cifs mounting without password but this is interesting
>>
>
>Yes, it can be arranged, but of course it's a bad idea unless the
>network is guaranteed (!) to be secure.
Not sure what would mean "guaranteed" for you, but two
The Windows username is my own name, I have no password set on that
acount. It mounts flawlessly from another Windows machine, but when I
try:
# mount -t cifs //box1/d /mnt/d -o username="Steve
Matzura",password=""
I get:
mount error(121): Remote I/O error
Refer to the mount.cifs(8) manual page
On Sat, 2016-01-09 at 13:59 -0500, Steve Matzura wrote:
> I tried it, but nothing changed. And it's not even the same error.
> Mine is 121, an I/O error of some kind, while the one in the article
> is error 12, a memory error.
The link is to a comment on the article, with the same error.
--
On Sat, 09 Jan 2016 21:47:02 +0100
deloptes wrote:
> Steve Matzura wrote:
>
> >
> > I tried it, but nothing changed. And it's not even the same error.
> > Mine is 121, an I/O error of some kind, while the one in the article
> > is error 12, a memory error.
>
> I've not
Mea culpa. I didn't read far enough down the page.
After trying `vers=2.1', now I get error 13, permission denied.
Getting closer. Now it's probably a username or password problem, but
the Windows account has no password. I suppose if I must put one on,
in order to make this work, I will, but
On Sat, 2016-01-09 at 11:04 -0500, Steve Matzura wrote:
> The Windows username is my own name, I have no password set on that
> acount. It mounts flawlessly from another Windows machine, but when I
> try:
>
> # mount -t cifs //box1/d /mnt/d -o username="Steve
> Matzura",password=""
>
> I get:
>
On Sat, 09 Jan 2016 17:53:38 +0100, Sven wrote:
>On Sat, 2016-01-09 at 11:04 -0500, Steve Matzura wrote:
>> The Windows username is my own name, I have no password set on that
>> acount. It mounts flawlessly from another Windows machine, but when I
>> try:
>>
>> # mount -t cifs //box1/d /mnt/d
On Saturday 09 January 2016 22:00:46 Steve Matzura wrote:
> Mea culpa. I didn't read far enough down the page.
The fact you have to do so is clearly the result of your screen reader,
Steve - the link actually opens at the comment in a GUI.
Lisi
Let me rephrase/clarify that. There are lots of things on which
screenreaders can be blamed, but this one wasn't one of them.
On Sat, 09 Jan 2016 20:49:59 -0500, you wrote:
>On Sat, 9 Jan 2016 22:46:20 +, Lisi wrote:
>
>>On Saturday 09 January 2016 22:00:46 Steve Matzura wrote:
>>> Mea
On Sat, 9 Jan 2016 22:46:20 +, Lisi wrote:
>On Saturday 09 January 2016 22:00:46 Steve Matzura wrote:
>> Mea culpa. I didn't read far enough down the page.
>
>The fact you have to do so is clearly the result of your screen reader,
>Steve - the link actually opens at the comment in a GUI.
>
17 matches
Mail list logo