I've looked into this, but got mixed messages.

Couple of IT guys are appalled that the "path" in Command Center is not really a path. And very upset that scanning to a Mapped Drive is not as straight forward as other Copiers.

Is it possible, if so any dumbed down way to explain it to me?

Thanks in advance.

It is a path, just not a local path with a drive letter. It's a UNC path or share path. The SMB protocol doesn't understand drive letters, just shares. For example, if you had a shared folder called "scans" on the c:\ drive (c:\scans) you could express it as \\computername\scans to be compatible with SMB. In Command Center you just need to set the host as "computername" (or the IP address) and set the path as "scans". If you had a subfolder under scans like "c:\scans\subfolder" your path in Command Center would be "scans\subfolder". IT will have to make sure that the appropriate permissions exist on the subfolder. I hope this helped instead of making it more confusing.

As I understand it, you cannot scan to a MAPPED drive only a resident drive (C: D: etc).
Also, if you have a folder shared (ie- SCANS) you needn't add the location (C\SCANS) just the shared folder name.

That half of it you helped me with, however, you're using the C drive in your example. The customer "needs" it to go to a mapped drive (Z or X or something).

Kyo will error out if I put the scans folder from the mapped drive in the path field.

I'm not doing X:\scans....just "scans". I tried the servers credentials for logon/password too with no luck. Does it need to be on the C drive?

Thanks again bud.

No, KM says it does but I had a tech call the other day with a similar question. Scanneing to the E: (attached to server) and he input the shared folder name and it scanned no problem.

If the customer needs it to go to a mapped drive, then you'll have to change the host to the computer name of the actual computer that the mapped drive is mapped to.
Example:
Mapped drive X: on computer PC1 is mapped to shared folder C:\data\scans on PC2 and is shared as \\PC2\scans. To scan to X:\ on PC1 you would set host as "PC2" and path as "scans". Does that clear it up?

It looks to me like we're getting a little cross-fired here between 'scan to file' and 'scan to smb' which have completely different rules.
'Scan to File' does not support 'Mapped' drives (which are a virtual drive representation of an SMB path). Therefore 'Scan To File' must be installed on the machine with the destination hard drive physically in it (which is prohibitive if that happens to be a Linux or Unix Server - since the utility doesn't exist for these platforms).
'Scan To SMB' is as standardized as you're going to get. While the path is broken down to make it easier for the layman (allegedly) - instead of '\\server\path\subfolder' the host is separate 'server' and the path is 'path\subfolder"
A mapped drive can be illustrated as follows:
Drive X: = \\server\scans
So SMB scanning CAN scan to mapped drive 'X' - the copier just doesn't map it as 'X', but it goes to the same place.

To simplify deployment of SMB I use a batch file to set up credentials, create the folder and share it. You can find it here:
SMB Batch File

Odd, KM Tech support and 3 regional reps have told me SMB to a mapped drive is not possible. You have done this I take it?
Z

A 'Mapped' drive is just an alias for an SMB share - ie X: = \\server\share, so while you can't scan to 'X:' you can certainly scan to \\server\share - which is the same location as the user's drive 'X:'

Ditto what scoful said. You are not going to scan to the end workstation where you are seeing the mapped drive. You are going to scan to the computer where the mapped drive points to. It should be straight-forward since mapped network drives are just a convenient shortcut to a shared folder on a network. Your end user just does not understand how to see where that map is pointing to.

Is this simply a matter of Kyocera staying away from IT support, or do you think they're not aware of how simple this is?

(I have not tried it, I showed them it works to c: and told them to go crazy with their own tweaks after that, but I would like to learn)

There are issues with scanning SMB directly to a server running Windows 2003. Some issues with digital signing that must be resolved by changing policies on the server, and also giving read/write permissions to the account that the scanner uses.

In our own office, I can SMB scan to our server only with the older machines with black/white operation panels. The Falcon 3 boxes and newer will error out every time. I would try to fix it, but the management in their wisdom did not feel right having their outsourced IT support give me admin rights on the network like I used to have.

Perhaps this is what is going on and causing the IT people to scratch their heads?

Chris - the 'Signed Communications' requirement was corrected in a firmware update some time ago. (That's what the mysterious SSL references are all about - its SMB signing, not SSL for SMTP - which I think all of us that have to deal with AT&T DSL need to see.)

You just have to follow the DOMAIN\user authentication rules.

quote:

Originally posted by scoful:
Chris - the 'Signed Communications' requirement was corrected in a firmware update some time ago. (That's what the mysterious SSL references are all about - its SMB signing, not SSL for SMTP - which I think all of us that have to deal with AT&T DSL need to see.)

You just have to follow the DOMAIN\user authentication rules.

Scoful, you are correct. I checked our setup and there is a change of syntax between the older machines and newer machines for sub-folders. You use "/" on older machines, and "\" on newer models. Discovered that error reviewing the Scan To SMB (PC) Setup Guide ver 3 which is available to download from KMAconnect. It's listed under the manuals for the TaskAlfa machines. Good read for techs and the IT people when you are installing a new machine. It could be of help in this problem too.

Thanks guys, this discussion has cleared up a few things. Now to the server.........

Chris - Can I grab a copy of that from you pls,
These guides are not listed on the KMUK login and obviously I can't access KMAconnect

My email is in my profile -

Thanks in advance
Regards,
Mark

Mark and everybody:

The Scan to SMB setup guide is available at Kyoceramita.com also. Direct link below.

http://usa.kyoceramita.com/ame...MB-PC-EN-setupR3.pdf