Scan to Server network drive folder

[Guest]

I am trying to set-up a scan to folder destination on a Samsung 5935. I have tried to set this up many times, but get the same error "file Exists" when trying to send through. I am confused on what the issue is and why it doesn't go through. It has been set up locally to a machine in the same room, but the companies needs have changed and they want to send the scans to a network drive with a Scans folder within it. The thing that is stumping me is the Share name section under the sever name. Is this where i enter the file path like "\Public\Scans" Public being the network drive name and scans the folder within it. SCreen shots would be awesome. I am having a hard time setting it up to do this, Yet I know the file path is correct when I trype it in to a network PC and I know the username and password are correct because I can remote to the server as well. Really confused why it doesn't like the way i set it up. I kinda mirrored the set-up to be similar to the scan to folder locally that already works, except I made the changes needed for scanning to the server and not a local machine. Can anyone help that has done this before?

Thanks,
Nick

[rthonpm]

Re: Scan to Server network drive folder

A couple of things:

1. Is the shared folder set up on a server or a workstation?

2. What operating system is on the machine?

3. Is authentication needed? If it's going to a server you're going to need to use a valid user name and password for the domain.

[Nick k]

Re: Scan to Server network drive folder

This function has been set up before and worked properly. The drive is on the server/network. A domain username and password are needed and I have a correct one for use. The problem I have is how to set up the file path and other informaiton other than the username and password so it works properly. I have trouble mostly I think with the file path directing it to a network drive. I am not sure what the structure should look like. Also do the usernames need all of the extensions on them as well like: username@powerco.local? or Powerco/username for older set ups? The mapping of the network drive is the most difficult thing I need to get down. I am not sure if need to put it in like \\server\Public\Scans Public is the drive name and scans is the folder or do I need to call it \\server\P:\Scans for the actual drive letter it is named? This is what is confusing me. The login credentials are correct, I can log in to the PCs just fine, also on the network PCs, I can follow the file path \\server\Public\Scans straight to the folder. This is why I am confused as to how to point to a network drive in the file path and how the host name for the server should be entered.

[rthonpm]

Re: Scan to Server network drive folder

Is the copier configured with the correct DNS servers? If not, then using the share name will never work as there is nothing to translate it. The general configuration in more machines is just the user name and password as the domain name should be picked up by the NIC if configured correctly. For the share folder it would be: \\Server\Public\Scans

You may want to make sure however that the user name has read/write access to the folder just to be safe.

[mojorolla]

Re: Scan to Server network drive folder

You can enter the network path in the "run" box at the work station. Start, Run, enter the path into the box. If you can hit the folder that way, you are connected and is most likely an authentication problem on the server. Also, make sure the machine is on the same default gateway as the server. You could also try using the server IP address as opposed to the server name in the path. If the PC is a Windows 7 machine and has Live Essential installed, uninstall it. This is known to cause authentication problem

[mrfixit]

Re: Scan to Server network drive folder

Based on your first post I would think it was set up properly but there is a file naming issue. The file exists message suggests the machine is accessing the folder fine but a file with that name already exists in said folder. Make sure the folder is empty and try again. good luck.

[Nick k]

Re: Scan to Server network drive folder

The folder is empty and the device is set to rename the files being sent so that they don't get over written. I think its permissions issue or just how the set up for the host name and file path need to be on the device compared to how I am putting it in. I would love an example or a walkthrough on something similar. I can setup scan to local drive on a PC and to a folder on that drive but when I try to send it to a server and a network drive I get an error and it never goes through. Stumped.

[Redarmy]

Re: Scan to Server network drive folder

Hi Nick,
When you type '\\<Server IP>\Public\Scans' into your 'search programs and files' field (Windows 7) or 'run' (WINDOWS XP) does it pull up the scans folder?
I guess ensure on the server it is shared with full read/write permissions for everyone under the security tab. If the server is hosting a domain (eg. People.local) ensure the username includes the domain name (eg People\<username), or (<username@people)

[RRodgers]

Re: Scan to Server network drive folder

Or it may just flat out not work on that server, as I found out yesterday with a Bizhub 200 trying to scan to a 2003 server yesterday. DOH!!! I was pulling my hair out trying to get this thing to work, only look in the all active solutions and find out that box doesn't support 2003. LOL So I just scanned to an XP box and linked that PC's to that box.

[Nick k]

Re: Scan to Server network drive folder

I was thinking about possibly creating a shortcut locally to the network drive within the C drive and pointing the device to that folder that is actually a shortcut to the network drive. Does anyone think that might work? I can't get the server to allow the device through to the folder, so I was thinking this might be a way around the network paths altogether. ?

[rthonpm]

Re: Scan to Server network drive folder

You can't scan to a shortcut folder as that's not a valid SMB location. You may want to make sure that all of your firmware on the machine is up to date as well if you haven't already.

[Autenien]

Re: Scan to Server network drive folder

Or it may just flat out not work on that server, as I found out yesterday with a Bizhub 200 trying to scan to a 2003 server yesterday. DOH!!! I was pulling my hair out trying to get this thing to work, only look in the all active solutions and find out that box doesn't support 2003. LOL So I just scanned to an XP box and linked that PC's to that box.

Not correct. The issue you were having scanning to a 2003 server is one that is fixed by installing special firmware on the copier that allows for SMB signing, which is basically a security signature. When the 2003 server is acting as a domain controller, SMB signing is requiring for incoming SMB scans. I have set up many Bizhub 200/250/350 copiers to work in a 2003 server environment where they SMB scan to the server.