Now I understand what you're trying to do. KenB is correct, you can only send scans to a local drive. Can't you just create a shared folder on the server that others can access?
-
-
Has the account that is running the Scanrouter service got permissions for the mapped directory?Comment
-
I'm with Ken on this one, Scanrouter can only access local drives on the machine on which it is installed.
As Teebee said, put a new folder onto the server and either add it to their login script, add a shortcut to it on each PC manually (if you have that much time!) or just put the destination folder inside a folder which the users can already access.Comment
-
Finally I have almost everything working, using local disk, but all users are now scaning to folders.
But I have only 2 situations:
1- I have to log on to Scanrouter to initialize! (I installed as a service)
2- I have a IS2220D in a branch office in a subnet 10.0.10.0 (main office 10.0.0.0) and AD is replicating to the branch. I installed scanrouter on the branch office server (server 2008std) and added the printer, folders and users, everything like I did in the other IS2220D I have in the main office, but this one in the branch is not getting the destinations from scanrouter!
I tried with firewall off and still no luck!
Any clue what could be the problem?
ThanksComment
-
Just wanted to share a method I've used when all else fails, to get scan to folder working on machines that doesn't have that feature. You can set up a unique mail account that's only used for this specific function, wheater the customer is using pop3 or exchange doesn't matter as long as you get access for creating a new account.
After that you need to set up Outlook to be on 24/7 on a computer that no one uses, usually the server is the best option, and connect this newly added mail account to that. After that, install an extension called 'Attachment Auto Saver' (here's a link, it costs like $10) and point to the folder you want to save the files to.
Put the Outlook shortcut in the servers startup folder so that it starts automatically when anyone logs in on it, then instruct the customer they need to log in on the server after each reboot.
What happens is that you send the mailscan with the attached scanjob to Outlook on the server and as soon as the mail comes in the extension saves the attached file to the folder of your choice. The only thing the customer needs to do is to log in on the server after a reboot for Outlook to start up.
It's a bit tricky, yes, but it does the job. Of course it's much easier if you're the one administering their server as well as I was in this case. You could go a step further and install Outlook as a service which would take away the need for logging onto the server after a reboot, but that's another story.Peace sells, but who's buying?Comment
-
I don't have 100% sure, but I think I had scanrouter working on my management server (2008std - EBS) and because of the problem of not getting network folder working I moved scanrouter to my datacenter (2003storage server).
So I was hopping that scanrouter would work on my 2008std branch office!
I think I would install a VM on the branch server with XP and hope that would do the trick!Comment
-
Yeah getting Scanrouter to work past 2003 has been pretty much non existant. For Win Vista I had to turn off User Account Control. Kill Firewalls and still half the time it wouldn't work unless I opened and closes the Scanrouter software and walked around the desk for 15 minutes. It was extremely slow in delivery.
Its scan to email or nothing for these old machines.Comment
-
check firewall port 3670 in exceptions.Comment
-
Firewall off. mentioned above.Comment
-
with the release of Windows 2003, Microsoft removed the dcom module that scanrouter needs to map to networked folders. If you can get your hands on Windows 2000 or older, your problem is solved...I'm trying to think, but nothing happens...
Comment
-
Scanrouter lite is just that LIGHT, and since it is free, limited in what it can do. As stated before, Only LOCAL HDDs will be seen. Also, it rarely works outside of its local IP'd subnet. So a WAN will be very problematic, slow, intermittant and frustrating.
It is true the PORT 3670 needs unblocked everywhere that cold possibly block it, and some AV programs are puting in port blocking to non standard ports, 25,110,80...are usually open.
Customers should UPGRADE and take advantage of the great pricing that is out on MFP's. We are replacing 2 YO equipment just because of the improved leasing prices over time.
Good luck!Comment
-
I tryed with firewall disabled and still no luck.
At my branch I'm using win xp VM machine on a server2008std host, and can't figure out why the address list are not send to the copier!
Done everything like it is on main office running server 2003r2, but no ideia why its no working!Comment
-
Your problem is 2008. The LITE SW was DISCONTINUED in 2006. It did NOT work in a x64 envirnment, it did not work on a 2003SBS with email enabled, It wont work on Vista or Win7 of any version. The software was inherently UNSECURE and Ricoh was not going to fix it to make it secure as all the NEW products had these features embedded in them.
Your best bet shoud be the VMware and a copy of XP Pro as stated by gaiex above.Comment
-
I'm Gaiex!!
The VM thing It's not working, I don't understand why!
In my branch I have the 2008std running a VM with XP pro, all firewall off and still no luck!
10.0.10.0 network at the branch, 10.0.0.0 at main office.
What other software options do I have in order to make it work?
ThanksComment
-
Is the XP Pro have SP3? Then it will NOT work. SP3 killed the sw as well. Reload your VM with at most XP SP2 and do all the other updates, but not SP3.I'm Gaiex!!
The VM thing It's not working, I don't understand why!
In my branch I have the 2008std running a VM with XP pro, all firewall off and still no luck!
10.0.10.0 network at the branch, 10.0.0.0 at main office.
What other software options do I have in order to make it work?
ThanksComment
Comment