I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared printer that I cannot set up but I am not sure if this is a CentOS issue or a Samba issue. When I run the printer setup GUI, it is not able to find any shared printer. If I run smbclient I get this error: smbclient -L dap001 -N Unable to initialize messaging context Anonymous login successful ?????????????? Sharename???????????? Type?????????? Comment ?????????????? ---------???????????? ----?????????? ------- smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] Error returning browse list: NT_STATUS_REVISION_MISMATCH Reconnecting with SMB1 for workgroup listing. Anonymous login successful ?????????????? Server???????????????????????????? Comment ?????????????? ---------?????????????????????? ------- ?????????????? Workgroup?????????????????????? Master ?????????????? ---------?????????????????????? ------- I understand the "Unable to initialize ..." error can be ignored but I don't know what to do about the "NT_STATUS..." error. If it matters the printer share name includes spaces. Please advise. TIA. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On 14/10/2019 16:55, gw1500 via samba wrote:> I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared > printer that I cannot set up but I am not sure if this is a CentOS issue > or a Samba issue. When I run the printer setup GUI, it is not able to > find any shared printer. If I run smbclient I get this error: > > smbclient -L dap001 -N > Unable to initialize messaging context > Anonymous login successful > > ?????????????? Sharename???????????? Type?????????? Comment > ?????????????? ---------???????????? ----?????????? ------- > smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] > Error returning browse list: NT_STATUS_REVISION_MISMATCH > Reconnecting with SMB1 for workgroup listing. > Anonymous login successful > > ?????????????? Server???????????????????????????? Comment > ?????????????? ---------?????????????????????? ------- > > ?????????????? Workgroup?????????????????????? Master > ?????????????? ---------?????????????????????? ------- > > I understand the "Unable to initialize ..." error can be ignored but I > don't know what to do about the "NT_STATUS..." error. If it matters the > printer share name includes spaces. Please advise. TIA. >Try adding '-m SMB2' to the command Rowland
On 10/14/2019 12:10 PM, Rowland penny via samba wrote:> On 14/10/2019 16:55, gw1500 via samba wrote: >> I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared >> printer that I cannot set up but I am not sure if this is a CentOS issue >> or a Samba issue. When I run the printer setup GUI, it is not able to >> find any shared printer. If I run smbclient I get this error: >> >> smbclient -L dap001 -N >> Unable to initialize messaging context >> Anonymous login successful >> >> ?????????????? Sharename???????????? Type?????????? Comment >> ?????????????? ---------???????????? ----?????????? ------- >> smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH >> Reconnecting with SMB1 for workgroup listing. >> Anonymous login successful >> >> ?????????????? Server???????????????????????????? Comment >> ?????????????? ---------?????????????????????? ------- >> >> ?????????????? Workgroup?????????????????????? Master >> ?????????????? ---------?????????????????????? ------- >> >> I understand the "Unable to initialize ..." error can be ignored but I >> don't know what to do about the "NT_STATUS..." error. If it matters the >> printer share name includes spaces. Please advise. TIA. >> > Try adding '-m SMB2' to the command > > Rowland > > >Thanks but no difference. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Mon, Oct 14, 2019 at 5:55 PM gw1500 via samba <samba at lists.samba.org> wrote:> > I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared > printer that I cannot set up but I am not sure if this is a CentOS issue> smbclient -L dap001 -N > Unable to initialize messaging context > Anonymous login successful > > ?????????????? Sharename???????????? Type?????????? Comment > ?????????????? ---------???????????? ----?????????? ------- > smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] > Error returning browse list: NT_STATUS_REVISION_MISMATCHFor this specific error, see https://bugzilla.samba.org/show_bug.cgi?id=14151 https://bugzilla.samba.org/show_bug.cgi?id=14152 It appears to be an issue with smbclient; a workaround until the issue is solved could be client min protocol = SMB2 in smb.conf. In any case, if you still have issues you should try using a valid Windows username/password; once you have it working that way you can then try accessing as guest/anonymous if you really need it.
On 10/14/2019 1:54 PM, Giulio via samba wrote:> On Mon, Oct 14, 2019 at 5:55 PM gw1500 via samba <samba at lists.samba.org> wrote: >> I am running CentOS 7 with Samba version 4.9.1. I have a Windows shared >> printer that I cannot set up but I am not sure if this is a CentOS issue >> smbclient -L dap001 -N >> Unable to initialize messaging context >> Anonymous login successful >> >> ?????????????? Sharename???????????? Type?????????? Comment >> ?????????????? ---------???????????? ----?????????? ------- >> smb1cli_req_writev_submit: called for dialect[SMB2_10] server[dap001] >> Error returning browse list: NT_STATUS_REVISION_MISMATCH > For this specific error, see > https://bugzilla.samba.org/show_bug.cgi?id=14151 > https://bugzilla.samba.org/show_bug.cgi?id=14152 > > It appears to be an issue with smbclient; a workaround until the issue > is solved could be > client min protocol = SMB2 > in smb.conf. > > In any case, if you still have issues you should try using a valid > Windows username/password; once you have it working that way you can > then try accessing as guest/anonymous if you really need it. >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: "/etc/samba/auth.dap001.my username"?? <== note white space in name In that file I put: username = "my username" password = xxxxxxxxxx Some documentation mentions the file "/etc/samba/smbusers" but that file does not seem to exist with CentOS 7. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus