× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: Using a Scan To Network share (OfficeJet 9130)

Skywalker
NETGEAR Expert

Re: Using a Scan To Network share (OfficeJet 9130)

Does this also happen in Share security mode, or with guest access enabled on the share? I know HP uses Samba in a lot of their products, so there's a good chance that the scanner is actually using Samba too, but maybe in a strange way.
Message 26 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

Hi Skywalker,
Skywalker wrote:
Does this also happen in Share security mode, or with guest access enabled on the share? I know HP uses Samba in a lot of their products, so there's a good chance that the scanner is actually using Samba too, but maybe in a strange way.

In my case I am using User security mode. I have tried with Guest access enabled and disabled. It makes no difference. The printer always reports a username/password error.

Regards,
Ian.
Message 27 of 142
Skywalker
NETGEAR Expert

Re: Using a Scan To Network share (OfficeJet 9130)

IanSav wrote:
In my case I am using User security mode. I have tried with Guest access enabled and disabled. It makes no difference. The printer always reports a username/password error.

I still wonder how it would behave in full share security mode, since that uses a different authentication model. But changing security modes isn't something you really want to do on a live system. Anyone else try this with the NAS in Share security mode?
Message 28 of 142
jarrah
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

Ok, I've found a workaround to the problem. It will required an additional option to be added to one of the share configuration pages (the 'Advanced Options' seem most appropriate). The option would add/remove the following line to the [global] section of the smb.conf file on the ReadyNAS:

use spnego = no

Note that this may affect performance and/or access to shares by other CIFS clients. That's why it needs to be an advanced option.

A discussion of the issue follows.

The problem appears to be either a bug in Samba's session setup protocol or in the printer's implementation of the SMB protocol. It's possible that this will be fixed in Samba 4.0, but not certain. I'll post something to the samba-technical list to see if I can get clarification. In any case, until Samba 4.0 is released I think the only solution is the one described above.

Session setup for user authentication using SPNEGO goes something like this (client is the printer, server is the ReadyNAS Samba server):

1. Client sends a NEGOTIATE to server.

2. Server sends a NEGOTIATE to client specifying available options.

3. Client sends a SESSION_SETUP_ANDX to server to request authentication.

4. Server sends a SESSION_SETUP_ANDX with challenge and a status requesting more data is required (STATUS_MORE_PROCESSING_REQUIRED).

5. Client sends SESSION_SETUP_ANDX with challenge response and username.

6. Server sends a SESSION SETUP_ANDX with authenticated vuid.

7. Client sends a TREE_CONNECT_ANDX using authenticated vuid.

The vuid is then used for any subsequent communication between the client and server. Think of the vuid as a session key that identifies authenticated communication between the client and server.

The problem accurs because the Samba server actually allocates a temporary vuid in step 4 that is different from the vuid supplied to the client in step 6, and includes this in it's message to the client. The printer then uses this temporary vuid rather than the real vuid in step 7. Because the authentication actually succeeded, a message to this effect is logged on the server, which is what we're seeing. However the server then terminates the connection at step 7 when the incorrect vuid is supplied.

The 'use spnego = no' option tells the server to use an older authentication protocol that avoids the two stage process shown above. This avoids the temporary vuid allocation and so the correct vuid is used by the printer.

Greg
Message 29 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

Hey Greg,

Where are you based? I have tried to get HP in Australia to help with this and they weren't interested. Perhaps you can try your local HP support team and see if they can get this looked at for us.

Is there any chance you can feed this back to HP and get them to implement the fix in a firmware patch. That way there is no need to play around with RAIDiator and everyone who still has this series of OfficeJet can also enjoy the fix. The fact that you have the details of what is going wrong may inspire HP to sort out this issue once and for all.

Thanks for investigating this.

Regards,
Ian.
Message 30 of 142
jarrah
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

I'm in the US, but I doubt if HP here will be any more interested. The last firmware update for this printer was nearly two years ago, and this is probably a Samba problem anyway. I'll see what the Samba people say. If we don't get any traction with them, then maybe we can try pursuing it with HP.

Greg
Message 31 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

Hi Greg,
jarrah wrote:
I'm in the US, but I doubt if HP here will be any more interested. The last firmware update for this printer was nearly two years ago, and this is probably a Samba problem anyway. I'll see what the Samba people say. If we don't get any traction with them, then maybe we can try pursuing it with HP.

Sorry to correct you but the latest OfficeJet firmware is just on 7 months old. HP Officejet All-in-one Firmware SMR3010D 22 Nov 2006

Regards,
Ian.
Message 32 of 142
jarrah
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

That's typical of HP. If you select Mac OS X for your operating system, then go to the Firmware page, it shows version SMR3009P dated 30 Sep 2005. So people using Mac's get older firmware than people running Windows. Nice. 😞
Message 33 of 142
jarrah
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

Update: I just installed Samba 4.0.0 TP4 on my Linux box and it seems to fix the authentication problem! They seem to have re-written a large portion of the offending code and this appears to have solved the bad vuid issue.

Unfortunately this is a 'technology preview' version (i.e. pre-alpha) and there is no indication of when a stable release will be available.

I still think the best way forward for us ReadyNAS users would be to add a simple option to the share configuration page. I'll post something to the feature request forum and see what they say.
Message 34 of 142
jarrah
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

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
Message 35 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

Hi Greg,

Message of support added. I wonder if we are in time for a RAIDiator 4 fix?

Regards,
Ian.
Message 36 of 142
renato1
Aspirant

HP 7780 OfficeJet

Hello,

I am wondering if I experience the same problem with my Officejet 7780.

When I ry to scan directly to my ReadyNas NV+, it starts to write the file to the selected directory, but after creating the file (a 8KB file size IS created), the systems halts. The OfficeJet never ends its scanning action, the file does not grow.

I am pretty confident the user/passwd setting is correct (as the file IS created)......

Grtz,
R.
Message 37 of 142
renato1
Aspirant

OfficeJet 7780 - more details

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.
Message 38 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

Hi Renato,

In my case I can't get the initial connection to work. No file is ever created.

Regards,
Ian.
Message 39 of 142
DawgDaze
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

I also have a 7780 that won't write to my ReadyNAS NV+. I can't even get mine to go through the scan process. It fails attempting to select the scan-to folder saying that the share is full or write-protected (which of course it isn't). I've tried all manner of user/pass combos as well as modifying the access permissions on the share itself, and even creating a dedicated share just for the scanner. This combo would be the best thing my network ever did for me b/c it would be both a place to keep original scans that is redundant, and would relieve me from having to boot a machine to scan anything. Please Netgear or Infrant (whatever you like to call yourselves these days) dedicate some resources to making sure the samba on this thing is compatible with these scanners. Having the ReadyNAS was one of the reasons I bought the printer that would do the "scan-to-network-share" thing. I'll be very disappointed in both devices if I never get this working.
Message 40 of 142
Piggelmee
Aspirant

Officejet L7680

I have exactly the same problem as described by Renato. My Officejet 7680 starts scanning but stalls after writing approx. 7kb to the ReadyNAS share (usermode). I have to hard-reset the printer in order to get it back online. The (piece of) file on the Readynas share remains locked, I can't delete it...
Message 41 of 142
DawgDaze
Aspirant

Re: 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.
Message 42 of 142
bhoar
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

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

-brendan
Message 43 of 142
Skywalker
NETGEAR Expert

Re: OfficeJet 7780 - more details

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.
Message 44 of 142
Skywalker
NETGEAR Expert

Re: Using a Scan To Network share (OfficeJet 9130)

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.
Message 45 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

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.
Message 46 of 142
Skywalker
NETGEAR Expert

Re: Using a Scan To Network share (OfficeJet 9130)

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.
Message 47 of 142
IanSav
Apprentice

Re: Using a Scan To Network share (OfficeJet 9130)

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.
Message 48 of 142
DawgDaze
Aspirant

Re: Using a Scan To Network share (OfficeJet 9130)

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 尀㄀㤀㈀⸀㄀㘀㠀⸀㄀㜀㜀⸀㔀尀洀攀æ
Message 49 of 142
Skywalker
NETGEAR Expert

Re: Using a Scan To Network share (OfficeJet 9130)

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. 😞
Message 50 of 142
Top Contributors
Discussion stats
Announcements