Ricoh MPC3300 printing and scan to file setup

[jonbonse]

Hi all

I am just researching a little info regarding setting up a clients MPC3300 on their network prior to installation..

The MPC3300 is brand new from Ricoh and it will be installed on a Windows 2008 64bit server with workstations running Windows 7.

They will be using user authentication with copying, printing and scanning functions.

Is this an easy task to setup the above functions?

If there are any problems I can avoid before I start, please let me know!

Many thanks!

[TonerMunkeh]

Setting up user codes is a piece of piss. Just make sure the customer remembers to put their user code in the "vald access" tab in the printer driver. Use the PCL5 driver, not PCL6. It's more stable.

The bitch is setting up scan to folder on Win7, it's a total anus. My advice - don't. Do scan to email instead.

[jonbonse]

Will it come with ScanRouter?

[Oze]

+1 on the scan to email

[teebee1234]

Will it come with ScanRouter?

Forget scanrouter, that is no longer supported and was only supported up to XP. You might be ok setting up scan to shared folder on the 2008 server. If you were setting the shared folder on a Windows 7 os, then most likely you will have problems. If you can't get it going, do what was suggested - try and convince the customer to stick to scan to email.

[jonbonse]

Forget scanrouter, that is no longer supported and was only supported up to XP. You might be ok setting up scan to shared folder on the 2008 server. If you were setting the shared folder on a Windows 7 os, then most likely you will have problems. If you can't get it going, do what was suggested - try and convince the customer to stick to scan to email.

Thanks teebee1234!

The machine is brand new so will have to setup scan to folder so the documents are scanned on the copier and saved on the server. Then share this folder on the network. . . . . This is possible right?

I won't be installing on windows 7.

I will share a folder on the server if this can be done?

[jonhiker]

This machine will have SMB scanning built in.

yes, create a folder on the server and shareit. also, make sure to give the folder full permissions. then, go to the address book in user tools, set up a new program, go to folder, type in either the server IP address or server name, and touch "browse network". you might be prompted to input a login name and password. then, you should be able to see the folder and create the path. be sure to touch save a couple of times.

+2 on the scan to email.

[KenB]

Just a quick note on ScanRouter - it will not even connect to most of the newer machines, and can not be made to.

ScanRouter is a dead product now, as almost all current MFPs can scan to email and folder on their own.

+3 on the Scan to Email.

[Vulkor]

+4 on Scan to Email
or a NAS or Hell anything but a server OS past the Win 2003 version. I've seen nothing but complains with SMB on Win2008 and 7. Perhaps FTP?

[zed255]

A nice back office Linux box would be great for scan-to-folder and sharing out to network users, but it's too bad most IT people can't get their collective heads out of Bill's ass...

[Vulkor]

A nice back office Linux box would be great for scan-to-folder and sharing out to network users, but it's too bad most IT people can't get their collective heads out of Bill's ass...

Ehh file sharing easier on an XP machine. At least it was for me compared to UBUNTU. Ubuntu kept loosing its ability to browse the network. Samba would go belly up.

[zed255]

Ehh file sharing easier on an XP machine. At least it was for me compared to UBUNTU. Ubuntu kept loosing its ability to browse the network. Samba would go belly up.

Guess mileage varies, but I've had good luck using different Linux distributions. Best not to use a desktop version however, a server variant is more stable albeit more difficult to configure. Or at least strip out the un-needed services and only use the X environment for administration.

[Vulkor]

Guess mileage varies, but I've had good luck using different Linux distributions. Best not to use a desktop version however, a server variant is more stable albeit more difficult to configure. Or at least strip out the un-needed services and only use the X environment for administration.

Got a lot of Linux Knowledge? A Fav distro and setup tips? Wish to post in Connectivity? Would be awesome.

[zed255]

Got a lot of Linux Knowledge? A Fav distro and setup tips? Wish to post in Connectivity? Would be awesome.

I don't suggest I'm some kind of guru in any specific discipline. I do have some Linux experience, beginning with RedHat 6 and moving on from there. I have used RedHat, Fedora, Debian, Ubuntu, Slackware, Suse , Gentoo and others less noteworthy.

I like Ubuntu and Suse for desktops as they have decent graphical tools for configuration and it's easy to get 'non-open' software working. If you want to play God, and you think you're hot stuff than something like Slackware or Gentoo is for you. They are tougher to get operating as you want but are extremely flexible for the knowledgeable. I've always had a soft spot for Fedora and while it's reasonably easy to get 'non-open' stuff working it does take some work to do it. Fedora is quite well developed.

I'll see if I can put together some decent instructions for putting a basic, open share together on a linux box that pretty much any SMB/CIFS client should be able to access. Integrating into an AD/PDC environment isn't as easy if your looking for authenticated shares where the PDC's AD is referenced for authentication. An in-between solution is to have users set up in SAMBA and authenticate the windows username locally on the Linux box. I'd assume for the purposes of scanning and file retrieval open shares are desired.