Scan to SMB

[tsbservice]

Appreciate the welcome, but I have finished reading and it sounds like I wasn't far off. And No... I see a lot of over thinking being done. Plus what do you care what the hell I do, or my process by which I do it * shake my f*cking head* , I wasn't answering your question, but thanks....

Billy if I offended you by assuming and jumping ahead my apologies sir! Unless they have a network guy and a server and he has been messing around this is a small network or a copier issue...KISS

I'm sure u really carefully read all replies 2 minutes after your "brainstorming". Keep it coming.

[slimslob]

Apologies I have not read the entire thread just brain storming. Last thing I am not trying to be insulting , but you are not using SMB Scan_to_file( public ) are you? This will of course share the file out to anyone with access to the shared folder.

Not necessarily so. Especially if the scan folder is on an Active Directory file server. Even though individuals may have access to the folder, it does not guarantee rights to the file. I have encountered instances where the file was saved with the owner, name used to scan the file, and any server administrator as the only ones with any access. If the name being used was a name created for scanning only and not one that any domain member used, the administrator had to take ownership and then change read file permission to valid domain group.

[slimslob]

But AD requires a server not individual workstations using copier scan capabilities.... Am I missing something sir?

When I was saying create user profile I meant locally on the workstation. I was under the impression there was no server or cloud based services applicable to this situation.

Keep it up and I am sure that other members will red card you as well. We have enough egomaniacs IT people on here already.

PS: I just looked at your profile and you say that you are an end user and don't like formal training which means you are not mush more than a high school jock with a computer.

[J_Arnold]

Keep it up and I am sure that other members will red card you as well. We have enough egomaniacs IT people on here already.

PS: I just looked at your profile and you say that you are an end user and don't like formal training which means you are not mush more than a high school jock with a computer.

Not seeing that....hmmmmmmm. I am really good at sports though.

[BillyCarpenter]

I guess I should follow up on this thread since I started it.



J_Arnold, as I stated, the network consisted of about 10 PC's and they all printed wirelessly.

I wish I had an explanation for the phenomenon of scanning to 2 different PC's at the same time but alas, I have no answer. I haven't had any callbacks since the day I was there. I did delete the shared folders and create new ones, so I'm guessing that solved the problem.

[AndresM]

I ran into a strange occurrence the other day that I'm having a hard time wrapping my mind around. Perhaps some can shine some light on it.


I have a client (car lot) that has about 15 PC that scan to folder. This is all wireless. I was called out because a handful of PC would no longer scan. After I updated the PC's, I ended up having to delete the shared folder and create new ones in order to get it to work.

Here's the strange thing that happened. When I scanned to one of the PC's, the document appeared in the scan folder on the intended destination but also was in the scan folder on a totally different PC.

Thoughts?

Best practice on Kyocera machines and always works. Pinpoint application never fails and is easy to use.

Good luck


Andy