An authentication error occurs when trying to mount SMB mounts with dollar signs in them. These mounts are for administrators' uses only. Standard mounts work properly. How-To-Repeat: optimus# mount_smbfs '//yoshimitsu/c$' /mnt/smbfs/ Password: mount_smbfs: unable to open connection: syserr = Authentication error
FWIW, works here: darklight# mount_smbfs -Eutf-8:cp866 //yuri@lifebane/c$ /mnt Password: darklight# mount <snip> //YURI@LIFEBANE/C$ on /mnt (smbfs) Are you sure that you are using correct user credentials? FreeBSD darklight.org.ru 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Thu Oct 18 21:58:19 MSD 2007 yuri@darklight.org.ru:/usr/obj/usr/src/sys/DARKLIGHT amd64 Yuri
Garrett Cooper wrote: > Standard mounts work properly. >> How-To-Repeat: > optimus# mount_smbfs '//yoshimitsu/c$' /mnt/smbfs/ > Password: > mount_smbfs: unable to open connection: syserr = Authentication error If you Windows share is in the Microsoft Domain you should try use -W flag: # mount_smbfs -I 10.0.0.4 -E koi8-r:cp866 -W MYDOMAIN \ //ElsukovAV@ELSUKOV-AV/C$ /mnt/smbfs In my case with our domain politics i should use -W MYDOMAIN and real computer name (ELSUKOV-AV). Only with this conditions i can mount SMB share from computer in the MS Domain. In another case i've got the same error. -- WBR, Andrey V. Elsukov
I can't seem to reproduce this issue anymore, pending the fact that my kernel now hardlocks after I execute the command. Will submit a PR for that little issue ... pending feedback from some other folks on current@. -Garrett
Don't kill this PR yet. The issue still occurs, but only when I use administrative mounts. The fact that it now hardlocks on me is quite annoying >:(... I'm going to attempt to reproduce this issue from my 7.0 RELEASE VM. -Garrett
Reproducible using an 8-CURRENT VM on my Macbook compiled with the same options as my desktop (and with less cruft / zero ports). Replacing SCHED_ULE with SCHED_4BSD. -Garrett
On Tue, Jun 10, 2008 at 9:35 AM, Garrett Cooper <yaneurabeya@gmail.com> wrote: > Reproducible using an 8-CURRENT VM on my Macbook compiled with the > same options as my desktop (and with less cruft / zero ports). > Replacing SCHED_ULE with SCHED_4BSD. > -Garrett > Issue occurs with SCHED_4BSD as well =(. -Garrett
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
I have reproduced this recently, but it seems to be a change in the way Windows behaves and not a bug. Microsoft seems to have finally realized that the {drive}$ shares are a huge security hole and decided that only members of the Administrators group are allowed to mount them.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped