Using a Scan To Network share (OfficeJet 9130)

I have my NAS in share mode, perhaps that's the difference in our experience. However, they're both broken... so... not much help yet. Would be nice to know if anyone had tried this in another mode, like attached to an active directory, to see if that yielded different results.

Just a hunch - try using the toggleoplocks add-on.

-brendan

renato wrote:

More details on the problem above (about my Officejet 7780): the smbd.log says: [2007/06/28 16:58:58, 0] smbd/reply.c:reply_write_and_X(3057) write_andX: End of header assumed at 64 but was at 59. [2007/06/28 16:58:58, 0] smbd/reply.c:reply_write_and_X(3061) write_andX: SMB headerlength of 59. Fall back to regular write reading 1380 bytes My hunch is some tech-savvy at Infrant might know what happens here.....? Greetinx, R.

The message tells me that it's not acting like a modern CIFS client. We may be able to get a workaround going for this problem in RAIDiator 4.

jarrah wrote:
I've put in a feature request for this option: http://www.infrant.com/forum/viewtopic.php?t=11482 Please indicate your support if you'd like to see this option added. Regards, Greg

You can try this addon to do that right now.

Hi Skywalker,

Thank you for the plugin. It took me a few goes before my NV+ would accept the plugin (IE browser kept reporting page not found) but it did eventually take and the plugin installed.

The good news is I can now authenticate my HP OfficeJet 9130 to my ReadyNAS NV+. The bad news is I now get a network error trying to transfer a scan to the ReadyNAS. Here is the samba log of my two attempts:

[2007/07/04 10:07:31, 0] smbd/server.c:main(805)
smbd version 3.0.22 started.
Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/07/04 10:09:52, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/04 10:10:05, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 10:10:05, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 408 bytes
[2007/07/04 10:10:05, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 10:10:05, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 1392 bytes
[2007/07/04 10:10:35, 0] lib/util_sock.c:receive_smb_header_raw(807)
Packet read error. Expected 110981 bytes but received 0.
[2007/07/04 10:11:12, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/04 10:11:20, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 10:11:20, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 408 bytes
[2007/07/04 10:11:20, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 10:11:20, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 1392 bytes
[2007/07/04 10:11:50, 0] lib/util_sock.c:receive_smb_header_raw(807)
Packet read error. Expected 10336 bytes but received 0.

Even though the logs say that 0 bytes were transferred I do get a file created for each scan attempt with about 6KB of data. The data does look like the beginning of a valid PDF file. (This is now starting to sound like the other problem with the 7xxx series units.)

Is there anything else I can do to help you identify the issue?

Regards,
Ian.

Okay, I kinda expected to see that. I posted a new addon that *might* fix this. You'll have to install it once to toggle the change off, then install the new addon once more to enable the new one.

Hi Skywalker,

Well either I or my NAS is now confused.

After I installed the new patch the first time I was told that the option was enabled but my OfficeJet wouldn't connect (like the original error) so I installed the option again and it now says that the option is disabled but I can connect again. It looks like the enable/disable message is reversed.

I am still unable to achieve a proper scan. I get about 6KB of the PDF and the OfficeJet reports a network error. (This is the same as before.)

smbd version 3.0.22 started.
Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/07/04 11:38:08, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/04 11:38:17, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 11:38:17, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 408 bytes
[2007/07/04 11:38:17, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 11:38:17, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 1392 bytes
[2007/07/04 11:38:48, 0] lib/util_sock.c:receive_smb_header_raw(807)
Packet read error. Expected 128191 bytes but received 0.
[2007/07/04 11:39:27, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/04 11:39:34, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 11:39:34, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 408 bytes
[2007/07/04 11:39:34, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/04 11:39:34, 0] smbd/reply.c:reply_write_and_X(3061)
write_andX: SMB headerlength of 59. Fall back to regular write reading 1392 bytes
[2007/07/04 11:40:05, 0] lib/util_sock.c:receive_smb_header_raw(807)
Packet read error. Expected 126003 bytes but received 0.
[2007/07/04 11:42:02, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded

Anything else I can try for you?

Regards,
Ian.

This is all I see in the log (smbd.log) when my printer (7780) attempts to scan to the ReadyNAS:

[2007/07/04 10:41:36, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [media] -> [media] -> [media] succeeded
[2007/07/04 10:53:15, 0] smbd/service.c:make_connection(846)
192.168.177.7 (192.168.177.7) couldn't find service 尀㄀㤀㈀⸀㄀㘀㠀⸀㄀㜀㜀⸀㔀尀洀攀æ

Looks like there aren't many more ways to go here without having the OfficeJet in our hands here. I'll try to get ahold of one so we can hopefully get this resolved. It may take a little while though. :(

Hi Skywalker,

Thank you for trying to sort this out for us.

Perhaps HP can lend you one for the purposes of fixing compatibility issues. ;)

Regards,
Ian.