Scanner File Utility & 2008 Server

[scoobysteve]

I've got a client who was running Scanner File Utility on a Win 2000 workstation where the scans were being sent to destinations on a 2003 Server via a mapped drive.

the clients have now upgraded to server 2008 however the win 2000 workstation is still running the utility. the mapping of the drive and path to scanned destinations are still the same.

Now, the problem is i when i go to choose the scan destination i get an "incorrect destination parameter". I'm not sure what is going on here since it used to work fine for 2003 server. if i set the scan destination to point to a local C: drive folder, all is ok as well.

So my question is, does anyone know if 2008 server has any new security settings that may stop the utility from storing the scans onto any of the 2008 server's folders?

lastly, i know you need the latest Scanner filt utility version for 2008 Server but because i'm actually running it on Win2000, i would think that i do NOT need it.

anyhow any opinions would be much appreciated. thank you.

[scoobysteve]

Update... not really but another similiar scenario...

I went out to a client yesterday who had a scanning problem with their KM-4035.

I ended up loading the scanner file utility on a XP Pro workstation but had the scans sent to a mapped drive which linked to a 2003 Server share. I had exactly the same problem as above.

strangely enough it was working til friday.

So, can someone please see if they can scan to a mapped drive on a Server 2003 or 2008 share (via Scanner File Utility) and let me know. thanks in advance

[n25an]

ok... this might help

nothing is wrong with the copier...
nothing is wrong with the scanner...
nothing is wrong with the scanner file utility...

something is wrong with the mapped drive configuration...
consult Microsoft article on mapped drive connection to network may be lost

in other words... the network administrator has to fix the problem... or pay you to fix it for a nice fee...

this is also why in general kyocera does not support mapped drives because they cannot guarantee that it will reliably work all the time...

[Jules Winfield]

Not sure if this will help in your particular case, but try this:

Try using the IP address instead of the server name when creating the share, this will usually bypass any DNS issues the network may have and make connecting via mapped drives a whole lot easier.
For example, if there is a mapped drive called "X:" that points to a share called \\Computername\share and the IP address of "Computername" is 192.168.1.12, try creating the mapped drive in this way:
\\192.168.1.12\share.

[scoobysteve]

thanks guys for your suggestions... i dont think scanner file utility likes UNC for paths.. i think i actually tried that at one point.

i managed to sort it out yesterday with help from a Kyocera HQ specialist.

He suggested I install the scanner file utility in "Desktop Mode" as opposed to "Service Mode". Because the service mode installation runs before a user is logged onto the computer and network, the map to the network drive occurs only after a user has logged on, thus the scanner utility service isnt able to get access to the mapped drive- whereas in desktop mode, the user logs onto the network in which all the maps are created then the service is started manually.

the only strange thing is that with my problem with 2008 server, i wasnt able to see the directory of the mapped drive when i did a browse (it just froze the program) however if i just manually typed in the path and hit "OK", it was happy to work. 2003 server i didnt have any freezing problems.

Anyhow thanks again for the advice.