Getting Copier/Scanner to Scan to Network Folder

Thanatos

So, I've got a Sharp AR-M700N that is being used as a networked scanner/printer (it's a copy machine). I want said copy machine to scan to a network folder. It currently scans and e-mails without a problem, but I would like to be able to have it scan directly to folders. I've gone into the configuration and set it up to scan to a network folder, but I always get a CE-02 error. I think the problem is that I'm not putting in the proper path, and I'm not sure how I'm supposed to do that; I initially tried just directing it to the network drive, then to the IP of the server, but neither worked. Oh, and it definitely has write permissions to the folder in question (in fact, it has the same permissions I do), so that's not the issue, either.

Any help?

Erandus

Any firewall running between it and the server?

EDIT: Google is also telling me that there's often some associated "Network Scanning Tool" software for Sharp machines attempting to scan to a network location.

Thanatos

Erandus wrote: »

Any firewall running between it and the server?

EDIT: Google is also telling me that there's often some associated "Network Scanning Tool" software for Sharp machines attempting to scan to a network location.

Yeah, I found that, too, but it seemed to be something for PCs rather than the printer, and for hitting folders on specific workstations rather than network folders. At least, that's how I read it.

Erandus

I assume by "write permissions to the folder" you meant NTFS? Have you checked the share permissions to make sure that the actual share is either wide open or at least open to the credentials the device authenticates with?

Also, in the device itself, did you set the domain as well as the login/pass? If there's no blank specifically for domain, you may either have to specifiy it as part of the username (DOMAIN\username) or try creating a local account on the server with similar login/pass to what the device is hitting it with. This may be a useful troubleshooting step regardless.

But definitely check the share permissions, I forget those all the time. Combination of NTFS/Share permissions always uses the most restrictive, so if the account doesn't have modify rights to the share, all the NTFS rights in the world aren't doing it any good.

Thanatos

Erandus wrote: »

I assume by "write permissions to the folder" you meant NTFS? Have you checked the share permissions to make sure that the actual share is either wide open or at least open to the credentials the device authenticates with?

Also, in the device itself, did you set the domain as well as the login/pass? If there's no blank specifically for domain, you may either have to specifiy it as part of the username (DOMAIN\username) or try creating a local account on the server with similar login/pass to what the device is hitting it with. This may be a useful troubleshooting step regardless.

But definitely check the share permissions, I forget those all the time. Combination of NTFS/Share permissions always uses the most restrictive, so if the account doesn't have modify rights to the share, all the NTFS rights in the world aren't doing it any good.

By "write permissions," I was actually referring to the share permissions.

I just got into the Admin panel, and it looks like that might be where the problem is: the domain is set to "printer." I'm guessing if I change that to our actual domain, there's a good possibility it will fuck up all of our network printing, right?

Erandus

Its possible, but not likely. Network printing doesn't utilize any sort of Active Directory login unless that's one goofy ass printer. You also know what to change it back to. If that device is like most network printers, it's built with a "local" TCP/IP port on a single server and jobs are submitted by users via the server. At that point the server submits the job on their behalf over the TCP/IP port, but there's no NTFS or AD credentials involved in that transaction. You should be able to set the domain in the admin panel to your actual domain without breaking anything. Just send a test job to the device from the server it's built off immediately after making that change. If the test print doesn't work, change it back.

Thanatos

Erandus wrote: »

Its possible, but not likely. Network printing doesn't utilize any sort of Active Directory login unless that's one goofy ass printer. You also know what to change it back to. If that device is like most network printers, it's built with a "local" TCP/IP port on a single server and jobs are submitted by users via the server. At that point the server submits the job on their behalf over the TCP/IP port, but there's no NTFS or AD credentials involved in that transaction. You should be able to set the domain in the admin panel to your actual domain without breaking anything. Just send a test job to the device from the server it's built off immediately after making that change. If the test print doesn't work, change it back.

I'll have to fuck with this at some point when I'm here after 5:00 or something, and bringing down a printer doesn't have the potential to be a total disaster.

I'm inclined to agree with your assessment, but if the printer goes down during work hours, it's going to be my ass.

Erandus

Thanatos wrote: »

Erandus wrote: »

Its possible, but not likely. Network printing doesn't utilize any sort of Active Directory login unless that's one goofy ass printer. You also know what to change it back to. If that device is like most network printers, it's built with a "local" TCP/IP port on a single server and jobs are submitted by users via the server. At that point the server submits the job on their behalf over the TCP/IP port, but there's no NTFS or AD credentials involved in that transaction. You should be able to set the domain in the admin panel to your actual domain without breaking anything. Just send a test job to the device from the server it's built off immediately after making that change. If the test print doesn't work, change it back.

I'll have to fuck with this at some point when I'm here after 5:00 or something, and bringing down a printer doesn't have the potential to be a total disaster.

I'm inclined to agree with your assessment, but if the printer goes down during work hours, it's going to be my ass.

Huh.. they're that concerned about a printer? I mean, I understand any outage is not something you want, but a single printer for a few minutes seems a bit extreme.

Thanatos

Erandus wrote: »

Thanatos wrote: »

Erandus wrote: »

Its possible, but not likely. Network printing doesn't utilize any sort of Active Directory login unless that's one goofy ass printer. You also know what to change it back to. If that device is like most network printers, it's built with a "local" TCP/IP port on a single server and jobs are submitted by users via the server. At that point the server submits the job on their behalf over the TCP/IP port, but there's no NTFS or AD credentials involved in that transaction. You should be able to set the domain in the admin panel to your actual domain without breaking anything. Just send a test job to the device from the server it's built off immediately after making that change. If the test print doesn't work, change it back.

I'll have to fuck with this at some point when I'm here after 5:00 or something, and bringing down a printer doesn't have the potential to be a total disaster.

I'm inclined to agree with your assessment, but if the printer goes down during work hours, it's going to be my ass.

Huh.. they're that concerned about a printer? I mean, I understand any outage is not something you want, but a single printer for a few minutes seems a bit extreme.

Like I said, I'm inclined to agree with your assessment, but if the two of us are wrong about breaking it by changing the domain, and also wrong about being able to just change it back to fix it, it could very well be for longer than "just a few minutes." Like I said, I don't think we are, but it's possible, and lord knows that when it comes to networking, not everything works the way you think it should.

The industry I work in is incredibly deadline-driven, so this printer being down for more than a few minutes during work hours would be a very bad thing.

Erandus

Fair enough. After hours it is. Let me know if we were right though.

Caelum Militis

We've got a Sharp MX-4501N here at work. If the AR-M700N uses the same style setup/control panel, then the domain under Network Settings name shouldn't matter. Our is set to Sharp-Printer, which I can assure you is not our domain. Under DNS settings, it's set to our website's domain name, which isn't our networks domain.

On the one here, after creating an address book entry for Network Folder, the folder path must be set as such:

\\serverName\path\to\shared\folder. (our share is Docs, and it's saving to a folder within called Licenses, so the folder path is \\serverName\Docs\license)

Beyond that, just make sure you have the domain user filled in properly (for this one, it's just the username, not domain\username), and the usernames password correct.

Of course if your model uses a different control panel, this will be completely unhelpful

Thanatos

Caelum Militis wrote: »

We've got a Sharp MX-4501N here at work. If the AR-M700N uses the same style setup/control panel, then the domain under Network Settings name shouldn't matter. Our is set to Sharp-Printer, which I can assure you is not our domain. Under DNS settings, it's set to our website's domain name, which isn't our networks domain.

On the one here, after creating an address book entry for Network Folder, the folder path must be set as such:

\\serverName\path\to\shared\folder. (our share is Docs, and it's saving to a folder within called Licenses, so the folder path is \\serverName\Docs\license)

Beyond that, just make sure you have the domain user filled in properly (for this one, it's just the username, not domain\username), and the usernames password correct.

Of course if your model uses a different control panel, this will be completely unhelpful

Okay, this got me a CE-03 error instead, fixed that by having it login as me, which got me a CE-00 error. I know I have write permissions to the folder (since I do stuff there every day), and I know it's not the cabling. Any ideas?

Caelum Militis

Double check that you have valid DNS settings. You probably do since you said it scans to email fine, but your smtp settings may be put in ip address instead of domain, in which case DNS wouldn't matter for email.

I also found a semi-obscure reference to disabling RARP (Network Settings -> Protocol Settings in my control panel) fixing this if it's on. RARP is off on ours. (like earlier discussed solutions, this shouldn't keep the printer from functioning by changing this, but do at your own risk).

Beyond that, nothing else springs to mind.

Thanatos

RARP is disabled, the domain name is correct under "DNS Setup" (though there is an IP for "Primary DNS Server," which there should be, right?).

Caelum Militis

Yea, there should be an IP for primary DNS server (and secondary doesn't hurt, in case the primary isn't working). Do you know if the IP address is actually a DNS server? It probably is, but confirming wouldn't be a bad idea.

All I can find regarding the error is that CE-00 seems to indicate that the scanner can't find the server.

Thanatos

Caelum Militis wrote: »

Yea, there should be an IP for primary DNS server (and secondary doesn't hurt, in case the primary isn't working). Do you know if the IP address is actually a DNS server? It probably is, but confirming wouldn't be a bad idea.

All I can find regarding the error is that CE-00 seems to indicate that the scanner can't find the server.

Except that e-mailing still works just fine.

The DNS server looks like it's our server. Which would make sense, since it really only has to communicate with that.