Lexmark Scan to network setup

If the Lexmark uses the SMB protocol to connect to the shared folder, and that shared folder resides on a Lion Mac, then this could be the problem. Apple changed the SMB protocol in Lion and this has stopped many devices from push scanning to a shared folder via SMB.

If the Lexmark is using a different protcol to SMB or you are not using Lion then you may need to install a Lexmark utility on the Mac so that the printer can locate the computer and thus the shared folder on the network.

rross3 wrote:

Thanks for the imput...I've tried using the IP address combo with no luck. I'm guessing then it must be with Lion then. Maybe the next update will resolve some of these issuses.

As I mentioned, if you are trying to scan to a shared folder on Lion using SMB then this will not work as Apple changed the SMB protocol used by Lion. As for the next update resolving this, don't hold your breath. Apple made the change for financial reasons and I doubt they will make any further changes to it so that vendors like Lexmark can scan again via SMB. Instead, it will be the vendors that have to change the protocol used by their scanning devices to be compatible with Lion.

Well then can you describe the procedure you are performing when you get that "cannot connect to server" message.

Thanks for the explanation. We have a similar function on our Canon copier. But while we enter smb://computer/share on the Mac, on the Canon we need to enter the path as \\computername\share.

The other thing to note is that you have may have an issue with IP address to NetBIOS name resolve. In other words, the Lexmark may not be able to get the computer name RMR3 resolved to an IP address. So if you use the IP address instead of the computer name, such as \\ip_address\share, then this may also help.

The last thing to mention is that the Lexmark appears to be using the SMB syntax. And the SMB protocol in Lion has changed and is no longer compatible with a number of multifunction copiers/printers. So even if you do get the correct syntax, you get errors when you try to scan stating that your user credentials are incorrect - which is not the case. If you are not scanning to a Lion Mac but to a Windows computer, then this SMB compatibility is not going to be the issue.