Using a Scan To Network share (OfficeJet 9130)

Okay, we got a 7780 in today, and I may have a solution. You can try this addon out. It should fix both of those issues. DawgDaze (and anyone else in Share security mode), you'll need to use the share name as the user name in the OfficeJet setup. If you don't have a password set on the share, just leave the password field empty.

NOTES:
* If you have any Unix/Linux clients on the network using CIFS, this addon will probably make them behave strangely. Mac OSX should be fine.
* This probably will not work in Domain security mode.

Skywalker,

Whatever it is they pay you, it's not enough. That worked perfectly! Thank you so much for your diligence in looking into this. The ReadyNAS is awesome, but this forum and people like yourself make it the best out there by a wide margin.

Thanks again!

Hi Skywalker,

I tried this update as well. In my case, on my HP OfficeJet 9130, I have returned to the situation where I can not logon to the ReadyNAS share even though the logs indicate that the login was successful:

smbd version 3.0.22 started.
Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/07/17 15:34:15, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/17 15:35:17, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/17 15:35:43, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [xxxxxxxx] -> [xxxxxxxx] -> [xxxxxxxx] succeeded

Should I be using both patches or just the latest patch? Is the SPNEGO patch incorporated into this patch? When the SPNEGO patch was enabled I could login with the scanner but file writes failed.

If I need to use both patches then in what order should they be installed and/or enabled? Given that I don't know what state my NAS is in is there a clean and easy way to check the status of these patches?

Regards,
Ian.

IanSav wrote:
Should I be using both patches or just the latest patch? Is the SPNEGO patch incorporated into this patch? When the SPNEGO patch was enabled I could login with the scanner but file writes failed.

Well, the SPNEGO patch should have been incorporated with this one, but it's being done on a client architecture basis, instead of a global basis. Perhaps the SPNEGO happens too early for the patch to work (before figuring out the client architecture). You can install the last addon (ToggleSPNEGO) once more to see if that helps. That will disable it globally. Sounds like HP fixed the bug in the 7780, but not the 9130...

Hi Skywalker,

Skywalker wrote:

IanSav wrote: Should I be using both patches or just the latest patch? Is the SPNEGO patch incorporated into this patch? When the SPNEGO patch was enabled I could login with the scanner but file writes failed. Well, the SPNEGO patch should have been incorporated with this one, but it's being done on a client architecture basis, instead of a global basis. Perhaps the SPNEGO happens too early for the patch to work (before figuring out the client architecture). You can install the last addon (ToggleSPNEGO) once more to see if that helps. That will disable it globally. Sounds like HP fixed the bug in the 7780, but not the 9130...

Trust HP to make this difficult. ;)

I will try to add the SPNEGO patch one more time and see what happens...

Edit: No go :(

The logs show that I can once again login but I now get the old data transfer error.

smbd version 3.0.22 started.
Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/07/17 16:32:09, 2] auth/auth.c:check_ntlm_password(307)
check_ntlm_password: authentication for user [iansav] -> [xxxxxxxx] -> [xxxxxxxx] succeeded
[2007/07/17 16:32:32, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/17 16:32:32, 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/17 16:32:32, 0] smbd/reply.c:reply_write_and_X(3057)
write_andX: End of header assumed at 64 but was at 59.
[2007/07/17 16:32:32, 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/17 16:33:02, 0] lib/util_sock.c:receive_smb_header_raw(807)
Packet read error. Expected 81863 bytes but received 0.

What should I try next?

Regards,
Ian.

Hello, Skywalker et al.

The pach FixOfficeJet_0.1.bin works PERFECTLY for my 7780.

Thanks a lot!

This community and your support is another reason to recommend an Infrant NAS to my colleagues and friends (2 sales so far ;-)

R.

Hi All,

Skywalker and I have moved our discussions to PMs for the moment. Skywalker has a patch that does work on the HP OfficeJet 1930 but he wants to improve it before release.

One of us will post back when packet traces and tests are complete.

Regards,
Ian.

Hi All,

I believe that Skywalker has now improved his fix for the HP OfficeJet 9130. I believe that the fix for this and the 7780 OfficeJets will now be incorporated into the RAIDiator 4 release.

Keep an eye open for more information when the release comes out.

Regards,
Ian.

Ok, I've finally managed to get my network set up again, having moved across the country.

Sounds like things have been making progress here.

Is there an addon that works for RAIDiator 3? I tried FixOfficeJet_0.1.bin but I'm still seeing the successful authentication/invalid username problem. I'm reluctant to use the beta 4 version as this is a production network.

Thanks.

Hi Jarrah,

Welcome back! :)

jarrah wrote:
Is there an addon that works for RAIDiator 3? I tried FixOfficeJet_0.1.bin but I'm still seeing the successful authentication/invalid username problem. I'm reluctant to use the beta 4 version as this is a production network.

Skywalker did create a patch called FixOfficeJet9130_0.1.bin but I am not sure if he wants it given out. There were issues using this patch if there are any Win 2K machines on the network. The revised patch in RAIDiator 4 does not have the limitation but it can't be applied to the RAIDiator 3 generation product.

Perhaps Skywalker can offer you the file directly if he is happy for it to be used.

Regards,
Ian.