SOLVED HP Officejet 8600

[Darren Myers]

So i have a OfficeJet 8600 N911n, it was configured to scan to a share on my windows server; but that share no longer exists since i moved all my data to my FreeNAS server.

The issue i am having is i can not get the Scan to network to function, i have tried it by the FreeNAS servers host name and IP address with no luck. I have the share mapped via CIFS, the share i am trying to get the OfficeJet to access is \\freenas\Internal\Scans or its IP address, neither work.

At the moment i have it mapped to one of my windows servers \\2k12\Scans and that works flawlessly, its also using DOMAIN\<username> and <workgroup>\<username>. I tried using FreeNAS\root and DOMAIN\root and <workgroup name>\room but doesnt work either....any solutions?

 

[anodos]

Verify that you can ping the printer from your FreeNAS server
Post smb4.conf file. /usr/local/etc/smb4.conf
Post relevant entries from /var/log/samba4/log.smbd

 

[Darren Myers]

I can successfully ping the printer from FreeNAS, files are below.

this is from the log that i think is relivant:

Code:

[2015/04/08 16:45:06.106483,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.1.10.16
[2015/04/08 16:45:06.106989,  0] ../source3/smbd/negprot.c:674(reply_negprot)
  No protocol supported !
  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.1.10.16 != (NULL)
[2015/04/08 16:45:37.984973,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.1.10.16
[2015/04/08 16:45:37.985492,  0] ../source3/smbd/negprot.c:674(reply_negprot)
  No protocol supported !
  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 10.1.10.16 != (NULL)
[2015/04/08 16:47:13.237742,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
  matchname failed on 10.1.10.16

 

[anodos]

It appears that the HP's CIFS client is trying to negotiate an NT1 (or less) connection. Decrease "minimum protocol" in your CIFS config to NT1 (although you can just as well leave it blank).

You should also set "max protocol" to "SMB2". "SMB2" allows automatic negotiation of any type of SMB2 connection. There is no advantage to setting it to "SMB2_24", which is a pre-release version of the spec that was finalized as SMB3.
Vista = SMB2_02
W7 = SMB2_10

You can get rid of the event log spam related to hostnames by unchecking the box "hostname lookups" in your CIFS config (or by fixing your DNS) ;)

 

[Darren Myers]

So how did you determine that? Because to me its all kinda jiberish lol

 

[anodos]

So how did you determine that? Because to me its all kinda jiberish lol

My preferred method of debugging samba issues is haruspicy. :D

"No protocol supported !"
Was the tipoff. Most printers use buggy / out of date samba clients. Probability of smb2 support is low.

 

[Darren Myers]

My preferred method of debugging samba issues is haruspicy. :D

"No protocol supported !"
Was the tipoff. Most printers use buggy / out of date samba clients. Probability of smb2 support is low.

I wouldnt of caught that, or knew where to look lol. Thank you Anodos :D