Color 550 w/ Builtin Fiery - Network Scanning to Yosemite Server SMB Share

[ezek1992]

Hey Joe,

Although I did not use your solution it was a valid workaround. I ended up setting up an FTP repository in CentreWare since it's so easy to get FTP going in Yosemite. That way I'm not training people on a new process for Network Scanning.

I don't understand why the SMB protocal hasn't been updated. The 550/560/570 are still relevant and SMB3 has been around quite awhile and on enterprise servers no less.

Thanks again!

[Joe Arseneau]

The 560 itself can't scan to Yosemite, but the Fiery can as long as you put a domain, even a fake one before the username.

You can't just use the "labuser" name because EFI requires a Domain, but "MSHOME" is just pretty much universal at this point and works fine as a placeholder so just use that.

For any combination of scanning I tried to 10.10 using a tempate and repository on the 560 itself the result was 027-516, which is a protocol error. Usually because of an SMB version that is not understood. On Server 2012 for instance it uses SMB3, the printer doesn't understand it so you need to allow SMB2 server side. This is as far as I know not an option on OSX. So for now, just use the Fiery templates instead.

[ezek1992]

Hello,

I have a new mac mini running Yosemite and the latest version of the OSX Server App. I've set up a network scanning share on the server and configured the File Repository but am still unable to scan to the share. I have this setup exactly how it was on our previous OSX Server (10.4) which has worked perfectly for years. 

Has anyone else had problems setting up Network Scanning over SMB to Yosemite?

Thanks!