Bizhub 368 (non E) SMB error 16714711

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rrrohan
    Service Manager

    Site Contributor
    1,000+ Posts
    • Sep 2011
    • 1977

    #16
    Re: Bizhub 368 (non E) SMB error 16714711

    thats a weird error code

    normally it would be "server connection error" or similar

    this is the error list out of user manual but it doesnt list that code
    https://1drv.ms/u/s!Ah_79nptMOdwgYU9...Yz0GQ?e=OQZabv (download then open in a browser otherwise youll just see the source code)
    Last edited by rrrohan; 11-24-2020, 06:00 AM.

    Comment

    • n25an
      Service Manager

      Site Contributor
      1,000+ Posts
      • Jul 2008
      • 1030

      #17
      Re: Bizhub 368 (non E) SMB error 16714711

      a couple of ideas I forgot to include...

      are there any big programs that are hogging resources... quickbooks... graphics software... games... anything like that... if so that could cause issues...

      also is it an old desktop... is there dust in the case... if the case is full of dust... this can also cause performance issues as the computer overheats... performance suffers...

      is memory on the computer good... is ram working ok... etc...

      also some of the newer hard drives... might have capacity but they slow down when doing file transfers...

      also a lot of times when windows updates it turns on settings that you turned off... its also good to check if any windows updates past or present have issues with smb and need to be rolled back...

      sometimes you will find that the most unlikely things block smb scanning because they affect the computer performance...

      its also a good idea to ask the customer what they are doing when these issue occurs... if they are surfing the net or watching netflix or playing games online... or doing a conference call on the same pc that does smb scanning... depending on the program and the power of the pc that can also cause performance issues...

      some customers like to have everything open on the computer when scanning and the computer simply can't handle it so something gives...

      in short...

      so if its not the copier...
      its not the pc maintenance
      its not programs on the pc...
      its not pc hardware...
      it could be customer computer routine...

      a good test if you can do it... is to have the copier scan to two destinations... the desired pc and another pc with no issues... just make the normal scan a group scan and then see if all works out... verify with customer this is ok... let them know its for testing purposes...
      then you can always trace back in the logs when the scanning failed to the customers computer... and you can see if its the computer or the copier...if it fails to send to two places... its the copier/network... if it fails to send to one that being customer computer... its the customers computer...

      just throwing out some ideas...
      Sad To Say I Don't Have a Life
      I do this stuff on the weekends too

      Comment

      • Copier Addict
        Aging Tech

        Site Contributor
        10,000+ Posts
        • Jul 2013
        • 14521

        #18
        Re: Bizhub 368 (non E) SMB error 16714711

        I have had some luck fixing SMB scanning issues by, with the customer's approval of course, creating a new user with admin privileges on the computer. The new user account needs a password. Then use the new user credentials to setup your SMB one touch. This doesn't always work, but a lot of the time it does.

        Comment

        • BillyCarpenter
          Field Supervisor

          Site Contributor
          VIP Subscriber
          10,000+ Posts
          • Aug 2020
          • 16311

          #19
          Re: Bizhub 368 (non E) SMB error 16714711

          Originally posted by copier addict
          I have had some luck fixing SMB scanning issues by, with the customer's approval of course, creating a new user with admin privileges on the computer. The new user account needs a password. Then use the new user credentials to setup your SMB one touch. This doesn't always work, but a lot of the time it does.
          I try to do the same because customers are always changing their passwords. Some customers look at me sideways when I ask them if I can create a new user on their computer.
          Adversity temporarily visits a strong man but stays with the weak for a lifetime.

          Comment

          • Copier Addict
            Aging Tech

            Site Contributor
            10,000+ Posts
            • Jul 2013
            • 14521

            #20
            Re: Bizhub 368 (non E) SMB error 16714711

            Originally posted by BillyCarpenter
            I try to do the same because customers are always changing their passwords. Some customers look at me sideways when I ask them if I can create a new user on their computer.

            I find that once you convince them they won't have to monitor the new account they are okay with it.

            Comment

            • BillyCarpenter
              Field Supervisor

              Site Contributor
              VIP Subscriber
              10,000+ Posts
              • Aug 2020
              • 16311

              #21
              Re: Bizhub 368 (non E) SMB error 16714711

              Originally posted by copier addict
              I find that once you convince them they won't have to monitor the new account they are okay with it.

              I always name the new user KYOCERA (as opposed to BOB) and tell them that the copier needs to log on to their computer in order to scan and the copier is the only one with the password. That seems to comfort them.
              Adversity temporarily visits a strong man but stays with the weak for a lifetime.

              Comment

              • CP-1015
                Trusted Tech

                Site Contributor
                250+ Posts
                • Nov 2020
                • 308

                #22
                Re: Bizhub 368 (non E) SMB error 16714711

                smb1.jpg

                Comment

                Working...