An unresolved problem with Samba

In other words, now the scanning of the copy scanning machine is very rich, the scanned file can be sent by mail, can be sent to Windows sharing. Always use Windows sharing, but the Windows system takes up a little bit of memory and wants to put this share under CentOS.

Installed version of samba4.1.1 (ip:172.16.4.20)

The printer is Konica (ip:172.16.4.30)

1, first, encountered the first phenomenon, after the SMB service is enabled, Win7 under no password access normal, can read and write files, but the scan prompt error, the end of the server-side grab packet, it is obvious that the port is unreachable, the problem is normal after enabling NMB

2, solve the above problem, the scanned file or dead or alive can not send to the server, log God horse can not find the problem, continue to view the packet.

Here try to use smbclient to connect to the server, it is normal to find that when smbclient and Win7 can use the Samba server normally, then the scanner problem is more likely.

① printer connection to Samba server failed

②smbclient connection samba-4.1.1, normal

③smbclient connection samba-3.0.22, normal (due to suspected samba version caused by a problem deliberately replaced by a lower version of the scanner connection)

By comparing the messages of each normal and abnormal situation, we find the problems, summarize them, explain

Using smbclient connection, the result of negotiation is to use "NT LANMAN 1.0", and Konica printer Each negotiation result is "NT LM 0.12", so suspicion is because two different authentication mechanism caused by different results, then the problem comes, The printer cannot customize the settings using which protocol.

You can find that the printer interrupts the TCP connection directly after receiving the session Setup ANDX response from the server.

Keep This problem, you can have new ideas when you meet again.

An unresolved problem with Samba