[Samba] Cannot Find Windows Shared Printer

[gw1500]

On 10/15/2019 10:13 AM, Rowland penny via samba wrote:
> On 15/10/2019 14:23, gw1500 via samba wrote:
>> On 10/15/2019 6:03 AM, Giulio via samba wrote:
>>> On Mon, Oct 14, 2019 at 9:41 PM gw1500 via samba
>>> <samba at lists.samba.org> wrote:
>>>
>>>> Thanks. I tried the workaround but it was no help. I'm a little
>>>> fuzzy on
>>>> how to add a Windows user/pwd. I THINK I'm supposed to create the
>>>> file:
>>> I understand you want to access a windows printer from Linux, and you
>>> are testing with "smbclient .. -N".?? (-N=don't ask for password).
>>>
>>> I'm suggesting you do these tests using "smbclient ....
>>> -Uuser%password?? ....." where user and password are valid Windows
>>> user/password.
>>> No configuration on samba (no smbusers).
>>> Once you have this working, then you can try with "-N", after having
>>> turned off "password protected sharing" on Windows.
>>>
>> Thanks. Sorry, I misunderstood. Here is what I get:
>>
>>> smbclient?? -L dap001 -U"my username"%xxxxxxx
>> Unable to initialize messaging context
>>
>> ?????????????? Sharename???????????? Type?????????? Comment
>> ?????????????? ---------???????????? ----?????????? -------
>> ?????????????? ADMIN$?????????????????? Disk?????????? Remote Admin
>> ?????????????? C$?????????????????????????? Disk?????????? Default share
>> ?????????????? DVD???????????????????????? Disk
>> ?????????????? E$?????????????????????????? Disk?????????? Default share
>> ?????????????? HP DJ 1110 series Printer???? HP DJ 1110 series
>> ?????????????? IPC$?????????????????????? IPC???????????? Remote IPC
>> ?????????????? print$?????????????????? Disk?????????? Printer Drivers
>> Reconnecting with SMB1 for workgroup listing.
>>
>> ?????????????? Server???????????????????????????? Comment
>> ?????????????? ---------?????????????????????? -------
>>
>> ?????????????? Workgroup?????????????????????? Master
>> ?????????????? ---------?????????????????????? -------
>>
>> So that much is working but I don't know where to go from here. I do not
>> mind configuring Samba to use username/password but I don't understand
>> why that is necessary. Permissions for "Everyone" on Windows looks
>> correct to me. I don't see anywhere to turn off password protected
>> sharing just for the printer.
>>
> Yes, but a standalone server doesn't know who 'Everyone' is.
>
> Authentication works like this:
>
> You need to create Unix users on the Samba standalone server and then
> make them Samba users with 'smbpasswd -a username'.
>
> If you do not want to do the above, then you can use guest access. To
> do this, you must have 'map to guest = bad user' in the [global]
> portion of smb.conf and 'guest ok = yes' in any share that you want to
> allow guest access to. After making the changes and restarting Samba,
> any user unknown to Samba will be authenticated as the guest user
> (usually 'nobody'), this authentication is done before the user gets
> anywhere near any shares.
>
> If, after connecting to the share, the guest user isn't allowed access
> by the permissions, then the guest user will still not be allowed
> access even if Samba will allow it.
>
> Rowland
>
>
>
So I added:

map to guest = "my username"

to [global] and

guest ok = Yes

to [printers].

Now smb will not start. I am guessing that is because there is no
password for "my username". However, trying to set it does not work
(perhaps because of the space in the username?):

>sudo smbpasswd -a "my username"
WARNING: Ignoring invalid value '"my username"' for parameter 'map to guest'
WARNING: Ignoring invalid value '"my username"' for parameter 'map to guest'
Can't load /etc/samba/smb.conf - run testparm to debug it

>testparm
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: Ignoring invalid value '"my username"' for parameter 'map to guest'
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
WARNING: Ignoring invalid value '"my username"' for parameter 'map to guest'
Error loading services.

-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus