We have placed a 3232 into a Novell 6 network. We explained the waay to scan into Novell and they indicated that the R***h scans directly to Novell using SMB. In disbelief I discovered they were correct. We upgraded the firmware to the 3232 and could not get the Kyocera to work the same way the Other MFG did. Our secondary MFG indicates they can scan via SMB to a Novell CIFS share. Has anyone else had success with this?

To update my post,
The Sharp Jupiter series(MX) can indeed scan to a network share without the use of any utility into a Novell 6 server. There is soon to be released firmware patch that needs to installed but using CIFS on the novell box is the same basic protocol as SMB. We are not sure why Kyocera could scan via SMB as both the Ricoh 2238 and the Sharp MX 4501 could.

CIFS is an expanded version of SMB, basically the updated version:

From Windows 2003 Server MCSE Training Kit (which i'v been totally immersed in lately): Before Windows 2000, SMB in Windows networks was linked to NETBIOS protocol and NetBios names. Since Win2K SMB has been expanded into a version called CIFS (common internet file system). The main advantage of CIFS is that it can bypass NETBIOS and use DNS based names.

So really if either netbios is being used or dns it should be able to find either, if it can't resolve dns names it should default to netbios which i believe can be installed on novell as a service or maybe depending on the version may be installed by default. Most newer novell servers can be set up to use smb/cifs so they can be part of an active directory based domain. But I think the catch is, the novell server must be able to talk to a windows network by having the proper services installed or be part of an active directory/domain.

OK but why CAN we scan to a Sharp mx4501 and NOT to a Kyocera 3232 using CIFS on a Novell 6 server? I have been setting up SMB scanning on Ricohs for 4 years. After I completed my 2000 mcse training Ricoh started using SMB for scanning which was more educational than 12 months of book training at a local college. But, all of that knowledge helped me none when the 3232 failed. My question remains why can the 3232 not do what the sharp can? They both use SMB and this customer doees not want to use windows anything except for the OS.

My bad, I should have read your post more carefully, i perssonally have not set up a 3232 to scan to smb, I'm still using scanner file utility, thought you were talking about the falcon III. Did not know there was an option to use SMB scanning on that model. Think there is an FTP option/