Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Oct 2019 14:27:18 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: Using '@' in user name with "mount_smbfs"
Message-ID:  <20191022142718.00005069@seibercom.net>
In-Reply-To: <20191022170225.581cf496.freebsd@edvax.de>
References:  <20191022094301.0000716b@seibercom.net> <20191022170225.581cf496.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/UjesBSH4SGPS649ABzui4f9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, 22 Oct 2019 17:02:25 +0200, Polytropon commented:
>On Tue, 22 Oct 2019 09:43:01 -0400, Jerry wrote:
>> I am stumped as to how I can accomplish using a user name with an '@'
>> in it with the "mount_smbfs" command/
>>=20
>> Assuming a user name of: user@domain.com, how would I get it accepted
>> by the mount_smbfs command.
>>=20
>> /usr/sbin/mount_smbfs -N -f 0644 -U me -W WORKGROUP
>> //user@domain.com@WIN-PC/Share $HOME/Win-Pictures
>>=20
>> I have tried both single and double quotation marks, but that fails.
>> =20
>
>Did you try using /etc/nsbm.conf for worgroup, username, and PC name
>instead of providing it directly on the command line? If I remember
>correctly, something like this (not tested!) should work:
>
>	[WIN-PC:user@domain.com]
>	password=3D12345
>
>The format is <server>:<user>:<share>, with the last two entries
>being optional. See "man 5 nsmb.conf" as well as the comment header
>of /etc/nsmb.conf for details.
>
>You can then use:
>
>	mount_smbfs <more options> //WIN-PC/Share $HOME/Win-Pictures
>
>Similarly, you can use a rule derived from this command in /etc/fstab
>in case you need this mount command more than once.
>
>Memory fragment from long time ago... ;-)
>
>
>
>PS. Common suggestion is to use "example.com" (instead of "domain.com")
>    as a placeholder.

That isn't working either. I found a post on Google that stated it will
never work due to a bug in the program. In any case, I have found a
work-a-round.

--=20
Jerry

--Sig_/UjesBSH4SGPS649ABzui4f9
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEIQb/tTwl6I1ueEVtOHMGOIfexWQFAl2vSgcACgkQOHMGOIfe
xWTHqAgAhKEkG7u2XR/JZzIVN72t+J2mWBWW0+DTwQ9a9Ho9VYVPSk+/Helcgoza
YxJqT8LXAz2t4UzO8bSW3FifILKHbiqyEwnhcgtMVNa87zsbP9W3CzlOCEY8DxbU
G4sraG/y1ui14Z+yLkJKdAhmup+8/+bNH7t34Rm0Ta56VT81QOidWcWEXfTSJ0Ca
Mp3/FgWSqoz1FRbI/FMQq+6g8t82SKFttKjjc9Rz//T5ZxxRrnVHoYhqc5N2bXli
ihFVyacw/MHbWbzEt7BNdojbHStkqCS1p400tZGlvNi933uxRWtTrywjd6t05seC
/oDz8iZL/Xs0MtmrBo97zEr4SqRitQ==
=etgC
-----END PGP SIGNATURE-----

--Sig_/UjesBSH4SGPS649ABzui4f9--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191022142718.00005069>