SMB Scanning not working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • hemansheth
    • May 2025

    #1

    SMB Scanning not working

    Hello,

    I have a Canon iE 3320i MFP printer and facing a issue with SMB scanning. I have windows server 2012 R2. Scanning is not working with the server and throws error of #801 and throws error of check the server.

    i have created a shared folder on one of the driver and gave permission to everyone for read and write but still its not getting scanned.

    what can be the possible reasons behind the same? can it be the SMB versions or firmware issue?

    thanks,
    Heman Sheth
  • hemansheth

    #2
    Re: SMB Scanning not working

    Originally posted by terramobil
    As far as I know, the Canon iR 3320i is too old to support SMB V3. The easiest way is to use an old Win 7 PC as a scan-server.
    hi how can i check the SMB version in windows server 2012? and can i make it work on the lower SMB version?



    i tried installing the update on server but still the problem persists. what is the SMB version on Canon iR 3320i??

    Your reply is highly appreciated.

    thanks,

    Comment

    • Gbr
      Technician

      50+ Posts
      • Nov 2011
      • 50

      #3
      Re: SMB Scanning not working

      Originally posted by hemansheth
      Hello,

      I have a Canon iE 3320i MFP printer and facing a issue with SMB scanning. I have windows server 2012 R2. Scanning is not working with the server and throws error of #801 and throws error of check the server.

      i have created a shared folder on one of the driver and gave permission to everyone for read and write but still its not getting scanned.

      what can be the possible reasons behind the same? can it be the SMB versions or firmware issue?

      thanks,
      Heman Sheth
      Hello, i think sharing folder in WIN SERVER is also done trough security tab. If both share permissions and file system permissions are set for a shared folder, the more restrictive permissions apply when connecting to the shared folder. Then turn on Network Discovery in Network and Sharing Center.
      Also check if firewall is blocking your traffic.

      Tim

      Comment

      • JPiek
        Trusted Tech

        250+ Posts
        • Oct 2014
        • 435

        #4
        Re: SMB Scanning not working

        I wouldn't setup a low SMB version on the network just for the copier with al the crypoware and malware arlund these days.
        I'd consider using scan-to-mail or scan-to-ftp...
        Johan

        Comment

        • hemansheth

          #5
          Re: SMB Scanning not working

          Originally posted by Gbr
          Hello, i think sharing folder in WIN SERVER is also done trough security tab. If both share permissions and file system permissions are set for a shared folder, the more restrictive permissions apply when connecting to the shared folder. Then turn on Network Discovery in Network and Sharing Center.
          Also check if firewall is blocking your traffic.

          Tim
          Hi Tim,

          many thanks for the prompt response. Please note that the folder is shared and Few other copiers such as Canon iR 3225i is able to scan to the folder that is created on the server so the issue is with the Canon iR 3320i which is newly added to the network. Any idea on the SMB version that the copier would be using? as i can cross check with the incoming traffic created over SMB on the server log.

          thanks,
          Heman

          Comment

          • parsmehregan
            Technician

            50+ Posts
            • Jun 2012
            • 97

            #6
            Re: SMB Scanning not working

            Suppose that you checked the machine has access to destination folder by PING command in network setting from MFP control panel.Connecting the new added MFP directly to a system with cross over cable (or a separate hub) and check the smb scanning may clarify if the problem is with network or machine setting.also try scanning to ftp.
            Last edited by parsmehregan; 01-24-2018, 07:17 PM.

            Comment

            • teckat
              Field Supervisor

              Site Contributor
              10,000+ Posts
              • Jan 2010
              • 16083

              #7
              Re: SMB Scanning not working

              SMB 1 : This may not be an exact classification as it was the default version used in Windows Operating Systems prior to Windows Vista.

              SMB 2.0 : This was one of the enhancements included with Windows Vista. In short, the aim of this was to reduce the amount of traffic generated by commands which are used as part of the normal operation of SMB traffic.

              SMB 2.1 : This version showed up on Windows 7 and Server 2008 R2 with a new Opportunistic Locking Mechanism. Opportunistic locking is a feature that locks files and handles local caching of files in order that other users do not modify files at the same time. This feature is applies to other Windows Operating systems, but has been improved for Windows 7 and Server 2008 R2.

              SMB 3.0 : Windows 8 and Server 2012 use this version of SMB which includes the capability of SMB Direct Protocol, otherwise known as SMB over RDMA. Also included was something called Multichannel which supports multiple connections for an SMB session.

              SMB 3.2 : This is part of the feature set included with Windows 8.1 and Server 2012 R2.

              Now a breakdown on what device has which version.

              Generation 1 and 2 imageRUNNER Advance use SMB 1

              Generation 3 imageRUNNER Advance uses SMB2

              If it is necessary to use a Gen 1 or Gen 2 device within an SMB 2 environment, please use Authorized Send which adds additional SMB version support.

              SMB protocol has a limit of 10 connections to the device and has a default timeout of 15 minutes. In a medium to large office environment, it is preferred to print through the Standard TCP/IP or LPR port otherwise the users will not be able to connect to the printer when the connection limit is reached.
              **Knowledge is time consuming, exhausting and costly for a trained Tech.**

              Comment

              Working...