cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Oce PlotWave scan to folder

SmlBizAdmin
Contributor

I'm trying to setup scan to network folder on an Oce PlotWave 345.

 

Per the manual I've done everything correctly, except I get errors when saving the external locations. The type is SMB of course since the scans are going to a shared folder on a Windows server.

 

The format of the path is \\servername\sharename. I've tried various usernames and their password but all give the same error so I'm sure it's not a credential issue.

 

The error I'm getting is that the hostname can't be resolved. The server where the scan share is located is on the DNS server and the plotter's network settings use the DNS server's IP as the DNS server. So I don't see why the hostname can't be resolved.

 

If I bypass DNS and enter \\ipaddress\sharename, then I get an error that says the remote destination can't be tested because the remote destination has reached the maximum number of connections.

 

This error has me stumped. There are several shared folders on the server and people are connecting to it all day long with no problem. I rebooted the server just in case something in memory or a cache needed clearing but that didn't help.

 

Has anyone here run into this before? If so, how did you resolve it?

 

Thanks,

Jonathan

4 REPLIES 4

Stephen
Moderator
Moderator

Hi, Jonathan, thanks for posting!

While our Forum Community members are welcome to chime in, our team does not directly support Canon Solutions America products. You'll find the most up-to-date suport options on the Canon Solutions America Support Site HERE

 

DRITAdmin
Apprentice

Did you every find a solution to this issue?  

That was so long ago I don't even remember who the customer was so, no, I don't recall if I ever found a solution.

 

Jonathan

WonQcpBi
Apprentice

I was getting the very misleading error "the remote destination can't be tested because the remote destination has reached the maximum number of connections"

In my case, the credentials (username and password) to authenticate to the SMB location were wrong.

Announcements