On Tue, 1 Jul 2025 19:52:40 +0200 JPT via samba <samba at lists.samba.org> wrote:> Hi, > > I try to make my old printer send scans to the samba server. (because > the linux scanner driver does not work yet) > This does not work. Samba 2:4.22.2-1 says "server does not support > any of the listed dialects" > > since the printer at least speaks LANMAN1 and 2, perhaps NT1 too > I believe samba simply does not understand the keywords sent for > these dialects? > are they defined anywhere? > > These are the dialects my printer announces: > > ?PC NETWORK PROGRAM 1.0 > ?MICROSOFT NETWORKS 3.0 > ?DOS LM1.2X002 > ?DOS LANMAN2.1 > ?windows for workgroups 3.1a > ?NT LM 0.12 > > (fetched using wireshark) > > Of course I tried different "client min protocol" values like LANMAN1 > LANMAN2, NT1 > > But this did not change anything. >Your printer is the client (which knows the protocols it uses) and your Samba server is (well, obvious really) the server (which, at the moment doesn't know the protocols that the client uses), so try 'server min protocol = NT1' in the Samba servers smb.conf Rowland
On 01.07.2025 20:31, Rowland Penny via samba wrote:> On Tue, 1 Jul 2025 19:52:40 +0200 > JPT via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I try to make my old printer send scans to the samba server. (because >> the linux scanner driver does not work yet) >> This does not work. Samba 2:4.22.2-1 says "server does not support >> any of the listed dialects" >> >> since the printer at least speaks LANMAN1 and 2, perhaps NT1 too >> I believe samba simply does not understand the keywords sent for >> these dialects? >> are they defined anywhere? >> >> These are the dialects my printer announces: >> >> ?PC NETWORK PROGRAM 1.0 >> ?MICROSOFT NETWORKS 3.0 >> ?DOS LM1.2X002 >> ?DOS LANMAN2.1 >> ?windows for workgroups 3.1a >> ?NT LM 0.12 >> >> (fetched using wireshark) >> >> Of course I tried different "client min protocol" values like LANMAN1 >> LANMAN2, NT1 >> >> But this did not change anything. >> > Your printer is the client (which knows the protocols it uses) and your > Samba server is (well, obvious really) the server (which, at the moment > doesn't know the protocols that the client uses), so try 'server min > protocol = NT1' in the Samba servers smb.conf > > Rowland > >Hi, Forget about OKI. I spent too much time trying to setup scanning from an OKI?MC883 (A3-copier) to a shared folder. I even installed newer firmware. When I contacted local support, I got a 20 minute lecture that it is not easy, and I should try FTP, or something like that. On a 4 year old copier? And one of their top line models? We have a bunch of copiers of other brands, in an age span from 10 years old, to recent ones. Worked out of the box on all models. The last OKI in the company, rest assured. I wish you good luck. Peter
> Your printer is the client (which knows the protocols it uses) and your > Samba server is (well, obvious really) the server (which, at the moment > doesn't know the protocols that the client uses), so try 'server min > protocol = NT1' in the Samba servers smb.confAh, thanks. That got me a step further. now there is a problem with authentication. It tries to log on with User: PrintServer\okiscan instead of okiscan. Could this be the problem? Is there anything I can do about it from the side of Samba? whieshark dump is here: https://mega.nz/file/bZhkkDaT#7bmmK0ceI0GJKiutrxxsFICM8Np1HIZo1WNeOCbDfxU (my clipboard currently does not work well, else I would paste the relevant parts in text format) Thank you very much. If there is no solution for this I give up on oki+samba as some people suggested. Jan