[Bug 1680224] Re: auto.smb fails on Windows administrative shares

[Mark A. Fox]

I honestly don't know. The initial patches from April 12th of 2017 were all
I needed and I haven't messed with it since.

On Wed, Jun 6, 2018, 09:20 Andreas Hasenack, <andreas at canonical.com>
wrote:

> @mark-fox, were those two patches the only changes you needed, or was
> the change to the awk script (removing the quoting of $) also needed?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1680224
>
> Title:
>   auto.smb fails on Windows administrative shares
>
> Status in autofs package in Ubuntu:
>   Triaged
>
> Bug description:
>   This is probably related to #385244.
>
>   I've been unable to get a Windows administrative share (ie. C$)
>   mounted through Autofs. Non-administrative shares work fine.
>   Administrative shares are accessible with the same credentials from
>   other Windows 10 workstations and through smbclient on Ubuntu (16.04
>   LTS) machines. Administrative shares can even be mounted using the
>   same credentials via mount on the command-line. However, autofs will
>   not mount the same shares, using the same credentials, on the same
>   Ubuntu machine.
>
>   Administrative shares are listed under /cifs/WindowsHostName, but a cd
>   /cifs/WindowsHostname/C$ results in "-bash: cd: C$: No such file or
>   directory" from the shell and the following output from 'automount -f
>   -v':
>
>   -----
>   attempting to mount entry /cifs/WindowsHostname/C$
>   >> Retrying with upper case share name
>   >> mount error(6): No such device or address
>   >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
>   mount(generic): failed to mount //WindowsHostname/C\$ (type cifs) on
> /cifs/WindowsHostname/C$
>   failed to mount /cifs/WindowsHostname/C$
>   -----
>
>   Notice that mount complains of failing to mount 'C\$' rather than
>   'C$'. If the bit of awk script that escapes the $ is removed, it then
>   fails to mount 'C', which is also no good. I think if we could
>   actually get mount to try to mount 'C$', it would work.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1680224

Title:
  auto.smb fails on Windows administrative shares

Status in autofs package in Ubuntu:
  Triaged

Bug description:
  This is probably related to #385244.

  I've been unable to get a Windows administrative share (ie. C$)
  mounted through Autofs. Non-administrative shares work fine.
  Administrative shares are accessible with the same credentials from
  other Windows 10 workstations and through smbclient on Ubuntu (16.04
  LTS) machines. Administrative shares can even be mounted using the
  same credentials via mount on the command-line. However, autofs will
  not mount the same shares, using the same credentials, on the same
  Ubuntu machine.

  Administrative shares are listed under /cifs/WindowsHostName, but a cd
  /cifs/WindowsHostname/C$ results in "-bash: cd: C$: No such file or
  directory" from the shell and the following output from 'automount -f
  -v':

  -----
  attempting to mount entry /cifs/WindowsHostname/C$
  >> Retrying with upper case share name
  >> mount error(6): No such device or address
  >> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
  mount(generic): failed to mount //WindowsHostname/C\$ (type cifs) on /cifs/WindowsHostname/C$
  failed to mount /cifs/WindowsHostname/C$
  -----

  Notice that mount complains of failing to mount 'C\$' rather than
  'C$'. If the bit of awk script that escapes the $ is removed, it then
  fails to mount 'C', which is also no good. I think if we could
  actually get mount to try to mount 'C$', it would work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions