Ricoh MP C5503 - Scan to Network Folder (SMB) settings

[Guest]

Hi All,

I have a Ricoh MP C5503 machine and trying to set up "Scan to Network Folder" using SMB protocol. I've tried serveral different methods and troubleshooting, but I am not able to get it to work. I went into Device Management > Address Book > changed option to "Detail Input" (As opposed to Easy Input) > Input all the information and saved it.

I've created a domain user account and added the proper permissions on the network folder. I've also entered it in the Folder Authetnication.

When I try to scan, it goes through but doesnt show up anywhere on the server. As I am using Windows Server 2012, Ricoh suggested I telnet and change the SMB port to 445 as opposed to current 139.

After doing this, I tested a scan and got User Authentication error.

Did anyone have success with this Ricoh copier using Windows Server 2012? In addition, I thought I can manage everything from the GUI of the copier online, however, is there anything I need to do on the screen of the copier? Such as going into settings? Entering the domain user account/password, etc?

Thank you all for your time and consideration.

[slimslob]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

I have never had to change the port to get scan to SMB to work so change it back.

That done, yes you do need to work from the screen on the MFP for the first time you set up SMB scanning. After that, you can add users to the address book with WIM.

From User Tools - System Settings check the following:

1. In network settings, the domain name, if using a domain, is set correctly. If not a domain, Workgroup name must be correct.
2. Login name and password is best set in File Transfer, saves having to set it for every user. I have found it best for the login name used to have administrator rights. This allows you to browse the network from the folder tab of the address book entry.
3. Use the connection test from the address book entry.

When you do a test scan and get an error, print the network settings from User Tools - System Settings - Interface. The last page will have the error listing. If there is no error message, the file has been sent and the problem is at the server. I have a school system where scans do not appear to be in the folder when the folder is opened using a shortcut on the desktop but if IT connects to the server using remote desktop, it is there. I found that if I open the shortcut then go up or down one folder level and then back, it appears.

[copyaction]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

Did you share the folder with read/write permissions

[niceville318]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

I just had this problem last week after a customer upgraded to Windows Server 2012. I was told, by my IT technician, WS 2012 defaults to SMB 3.0. The Ricoh's use SMB 2.0. Their IT administrator will have to make some changes within the server to accommodate this.

[copier tech]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

This is very basic, as said above when you create the shared folder have you given it full read/write permissions?

Do you have print/share enabled?

Does the Ricoh have ALL firmware files updated?

Can you browse the the network from the Ricoh addressbook management settings in user tools?

[mikedci]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

The MP C5503's support SMB 3.

[rthonpm]

Re: Ricoh MP C5503 - Scan to Network Folder (SMB) settings

I just had this problem last week after a customer upgraded to Windows Server 2012. I was told, by my IT technician, WS 2012 defaults to SMB 3.0. The Ricoh's use SMB 2.0. Their IT administrator will have to make some changes within the server to accommodate this.

Server 2012 does default to SMB3, but it can negotiate down to SMB2, or even SMB1 unless the feature has been removed from the server. SMB is not a hard version specific protocol: if it was, Windows 7 computers wouldn't be able to connect to Server 2012 and higher servers, or join a domain hosted by them. Likely the issue is in the permissions set on the folder, especially keeping in mind there are differences between share permissions and NTFS permissions. Depending on how the folder is structured (One folder that everything goes to, or subfolders for different users or departments), there are different ways to setup and secure the share.

For a generic share folder that everyone has access to, I share it to the Domain Users group with Read/Write permissions. Once the folder is shared, change the Security settings from Full Control to Modify (this keeps users from changing the security settings on folders) for the Domain Users group. If the MFP is using an AD account, it will automatically be a part of this group, and everything should work as long as the password and path are correct and there are no third-party firewalls interfering in the connection.

For a more specific share folder, for examples Scans\Department or Scans\User with the departments or users able to access only their folder, you'll need to still share the Scans folder to the Domain Users group, but then change the permissions on the individual folders to NOT inherit the settings of the Scans folder. DO NOT share the individual folders since nested shares cause all kinds of bad things to happen. You then change the Security permissions (NOT share permissions) for each folder to include either the specific AD group or user that should be able to access the folder, granting them Modify permissions, along with grating the MFP's account the same permissions and removing the Domain Users group from the folders. The permissions would look like this:

Folder	Permissions
Scans	Share: Domain Users (Contribute) NTFS: Domain Users (Modify), Administrators (Full Control), SYSTEM (Full Control)
Scans\Department1	NTFS: AD Group Department1 (Modify), Copier (Modify)
Scans\User1	NTFS: User1 (Modify), Copier (Modify)
Scans\User2	NTFS: User2 (Modify), Copier (Modify)

When I get to a server I have access to, I should be able to include pictures of the individual folder permissions.