2027 SMB scanning

[Jomama46]

I have a customer with a 2027 and while printing is OK, they are having a problem setting up the scanning. The server is SBS 2008. I am wondering if that is the issue, I dont usually have problems with scanning but I know that machines scanning to W7 need new firmware and so maybe Server 2008 has the same issue. This machine has the lastest firmware but of course there hasnt been any new fw since... a while back.
So my question is does Server 2008 have any special issues with SMB scanning?

[tcs04]

There was a firmware issue. Later machines do have an update, but not sure about 2027.

[teebee1234]

Server 2008 uses the newer SMB 2.1 protocol, same as W7. This model does require custom firmware for scan to folder on Server 2003 with SMB packet signing enabled, maybe it's the same requirement for 2008. It's on the TSRC site for this model in the custom firmware section just above the SD firmware list.

addendum: I did search the Knowledge Base and found the list of models that had updated firmware to address the newer SMB issue and it looks like the 2027 didn't make the cut- quote "Due to the amount of change required and the age of the devices, there is no plan to fix pre-04A models."

[PA5RR]

The solution is to disable SMB2 on the server, then the protocol is reset to SMB1 and you can acces the shared folders you created to scan to.
Here is a quote from a manual how to do so...I believe I found it on this site but I'm not sure ;-)

However, while SMB 2.0 seems to do a good job if BOTH client and server OSs support it, in some cases it will slow things down. The reson for this is that the version of SMB used for file sharing is determined during the SMB session negotiation. If both the client and server support SMB 2.0, then SMB 2.0 is selected during the initial negotiation. However, if they don't both support it, SMB 1.0 will be used to in order to preserve backwards compatibility.
The SMB protocol version to be used for file operations is decided during the negotiation phase. During the negotiation phase, a Windows Vista client advertises to the server that it can understand the new SMB 2.0 protocol. If the server (Windows Server 2008 or otherwise) understands SMB 2.0, then SMB 2.0 is chosen for subsequent communication. Otherwise the client and server use SMB 1.0.
When using the terms "client" and "server" in case of file and print sharing, it does not necessarily mean that a client-type OS such as Vista "always" connects to a server-type Os such as Windows Server 2008. Sometimes, a Vista computer will connect to another Vista computer, and in that case, the computer that is "serving" the shares is considered to be the "server".
Here's how SMB is used when related to SMB versions:
•When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used.
•When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
•When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used.
•When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
So, for troubleshooting purposes, mostly in an environment that has mixes operating systems, you might want to consider disabling SMB 2.0. You need to do so on both the "client" and the "server" operating systems. To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
Note there's an extra " " (space) after the "=" sign.
To enable back SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:
sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc config mrxsmb20 start= auto
Again, note there's an extra " " (space) after the "=" sign.
In order to disable SMB 2.0 on the server-side computer, follow these steps:
Warning!
This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.
1.Run "regedit" on Windows Server 2008 based computer.
2.Expand and locate the sub tree as follows.
HKLM\System\CurrentControlSet\Services\LanmanServe r\Parameters3.
Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)
Value name: Smb2
Value type: REG_DWORD
0 = disabled
1 = enabled4.Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0.
5.Reboot the server.


This should do the job, I never tried it. So do it at your own (or the admin's) risk !

[Jomama46]

Thanks for the replies. I was afraid of that. I will present PA5RR's solution to their admin and see if they want to implement it. Otherwise it will be upgrade time.
Thanks again.

[cobiray]

Does the 2027 even support SMB?

[Jomama46]

Yes, email and SMB

[cobiray]

Sorry, I was thinking Gestetner model numbers, not Ricoh. I was even off there too, so TGIF and my bad.