Bizhub 368 (non E) SMB error 16714711

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • richmods
    Technician
    • Aug 2013
    • 91

    [Misc] Bizhub 368 (non E) SMB error 16714711

    I have a Bizhub 368 installed in a Law office with 1 user. SMB scanning stopped working out of the blue and gives an error code of 16714711, so I went in and checked that the ethernet adapter was not set to public and that none of the SMB features had been turned of in windows features. All checked out ok. Checked for antivirus programs and temporarily disabled--no change. I tried using a static IP instead of the hostname--same error. I tried deleting everything (shared folder and user acct) and started over--same error. At this point I setup my laptop as a test and it worked fine so I know its a PC isssue but was wondering if anyone else has ever run into this and were you able to resolve it? I believe the issue is in win registry but not sure where. Any help would be appreciated.

    Also, If anyone has the movie data for this machine I would be willing to trade or buy.

    Thanks

    edit: the machine is set to NTLM V1/V2
  • Phil B.
    Field Supervisor

    10,000+ Posts
    • Jul 2016
    • 22808

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

    Originally posted by richmods
    I have a Bizhub 368 installed in a Law office with 1 user. SMB scanning stopped working out of the blue and gives an error code of 16714711, so I went in and checked that the ethernet adapter was not set to public and that none of the SMB features had been turned of in windows features. All checked out ok. Checked for antivirus programs and temporarily disabled--no change. I tried using a static IP instead of the hostname--same error. I tried deleting everything (shared folder and user acct) and started over--same error. At this point I setup my laptop as a test and it worked fine so I know its a PC isssue but was wondering if anyone else has ever run into this and were you able to resolve it? I believe the issue is in win registry but not sure where. Any help would be appreciated.

    Also, If anyone has the movie data for this machine I would be willing to trade or buy.

    Thanks
    what version of SMB is setup for the unit?

    what OS are the PC's running?

    what OS is on your laptop?

    so many questions so little information given.

    Comment

    • richmods
      Technician
      • Aug 2013
      • 91

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

      Originally posted by Phil B.
      what version of SMB is setup for the unit?

      what OS are the PC's running?

      what OS is on your laptop?

      so many questions so little information given.
      I've setup 100s of these and if you read my post I have already covered the basics and them some.

      WIN10
      SMB 1.0 and on1y 1 user

      Comment

      • Synthohol
        Certified Konica Expert

        Site Contributor
        5,000+ Posts
        • Mar 2016
        • 5463

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

        smb 1.0 is dead. especially with win10 and the slew of scanner killing windows updates.
        you would have better luck with FTP.
        i want to help however i can, relying on smb 1.0 is beating a dead horse especially if the OS is "home" ed.
        We know a thing or two because we've seen a thing or two.
        The medication helps though...

        Comment

        • BillyCarpenter
          Field Supervisor

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

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

          Originally posted by Synthohol
          smb 1.0 is dead. especially with win10 and the slew of scanner killing windows updates.
          you would have better luck with FTP.
          i want to help however i can, relying on smb 1.0 is beating a dead horse especially if the OS is "home" ed.

          Yep.


          How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows

          See link for instructions:


          How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows | Microsoft Docs
          Adversity temporarily visits a strong man but stays with the weak for a lifetime.

          Comment

          • BillyCarpenter
            Field Supervisor

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

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

            Originally posted by richmods
            I've setup 100s of these and if you read my post I have already covered the basics and them some.

            WIN10
            SMB 1.0 and on1y 1 user

            I didn't see where you listed the operating system nor the SMB version.
            Adversity temporarily visits a strong man but stays with the weak for a lifetime.

            Comment

            • Phil B.
              Field Supervisor

              10,000+ Posts
              • Jul 2016
              • 22808

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

              Originally posted by richmods
              I've setup 100s of these and if you read my post I have already covered the basics and them some.

              WIN10
              SMB 1.0 and on1y 1 user
              I did read your post.. you left out what version of SMB what OS you were running on the PC and your lapper.

              WIN10 disables SMBv1 soooo..... No you didn't cover everything in the OP THAT's WHY I ASKED.

              and it sounds like you were starting to get snippy in your reply.

              I saw information I needed to help WASN'T given so I asked.

              sorry if you got your feathers ruffled. You won't have to worry about me trying to lend a hand to you anymore...

              Hava great life.

              Comment

              • Phil B.
                Field Supervisor

                10,000+ Posts
                • Jul 2016
                • 22808

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

                Originally posted by BillyCarpenter
                I didn't see where you listed the operating system nor the SMB version.
                Billy,

                Thanks for the confirmation. I read it a few times that's why I questioned SMB and OS ... basics of SMB shit.

                you know an old stuffed brain sometimes has to review things several times before typing.

                Comment

                • BillyCarpenter
                  Field Supervisor

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

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

                  Originally posted by Phil B.
                  Billy,

                  Thanks for the confirmation. I read it a few times that's why I questioned SMB and OS ... basics of SMB shit.

                  you know an old stuffed brain sometimes has to review things several times before typing.

                  I read it several times myself before making that post....just to be sure. He says he's done thousands but doesn't know that SMB 1 has been disabled in Windows 10? Okay....
                  Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                  Comment

                  • Phil B.
                    Field Supervisor

                    10,000+ Posts
                    • Jul 2016
                    • 22808

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

                    Originally posted by BillyCarpenter
                    I read it several times myself before making that post....just to be sure. He says he's done thousands but doesn't know that SMB 1 has been disabled in Windows 10? Okay....

                    Comment

                    • richmods
                      Technician
                      • Aug 2013
                      • 91

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

                      Originally posted by Phil B.
                      I did read your post.. you left out what version of SMB what OS you were running on the PC and your lapper.

                      WIN10 disables SMBv1 soooo..... No you didn't cover everything in the OP THAT's WHY I ASKED.

                      and it sounds like you were starting to get snippy in your reply.

                      I saw information I needed to help WASN'T given so I asked.

                      sorry if you got your feathers ruffled. You won't have to worry about me trying to lend a hand to you anymore...

                      Hava great life.
                      I see you still don't have anything to add...

                      Comment

                      • Phil B.
                        Field Supervisor

                        10,000+ Posts
                        • Jul 2016
                        • 22808

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

                        Originally posted by richmods
                        I see you still don't have anything to add...
                        just these few things:

                        don't say you gave that information to us Wrong you didn't


                        getting snippy with a senior tech will NOT get you respect/help from that tech again or even others.

                        and has earned you a CARD ...

                        done with you.

                        Comment

                        • n25an
                          Service Manager

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

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

                          Originally posted by richmods
                          I have a Bizhub 368 installed in a Law office with 1 user. SMB scanning stopped working out of the blue and gives an error code of 16714711, so I went in and checked that the ethernet adapter was not set to public and that none of the SMB features had been turned of in windows features. All checked out ok. Checked for antivirus programs and temporarily disabled--no change. I tried using a static IP instead of the hostname--same error. I tried deleting everything (shared folder and user acct) and started over--same error. At this point I setup my laptop as a test and it worked fine so I know its a PC isssue but was wondering if anyone else has ever run into this and were you able to resolve it? I believe the issue is in win registry but not sure where. Any help would be appreciated.

                          Also, If anyone has the movie data for this machine I would be willing to trade or buy.

                          Thanks

                          edit: the machine is set to NTLM V1/V2
                          Did you verify that the user login and password did not change... for access to smb folder on the destination computer
                          did you verify that the user login is admin...
                          Did you verify that the hostname of the computer did not change...
                          Did you check for IP conflict... by turning off the computer and pinging to it... any response conflict...
                          Did you check for ip conflict... by turing off the copier and pinging to it... any response conflict
                          did you try giving your computer the ip address of the copier and related settings that copier have... turning off the copier... and then tried moving files from your laptop to the destination pc to see if that works... might give some insights...
                          Did you check if the hard drive is full on the destination pc.. that can stop scanning...

                          Is the admin login used for scanning the default admin login for a server... if so it has a limited amount of concurrent connections it can maintain at a time... so if it has over a certain limit then it stops taking requests until it kills one of those connections or it times out... this is a setting that can be set at creation of the account... its a security feature that sometimes causes trouble for scanning... because scanning to folder can trigger this feature if its enabled in the account... fix is to create an admin account with the limited login feature disabled... rarely seen this one...

                          ***did you try enabling smb in additional features...
                          did you turn off firewall on destination pc and test...
                          some antivirus also kill scanning so turn off and test...
                          ***did you check if the destination pc network setting was public if so that will stop scanning sometimes windows will turn it from private to public...
                          *** did you check if the computer has pending windows updates... that can also stop scanning...
                          *** (triple asterisk mark those are the things that have most often killed scanning for me)
                          Sad To Say I Don't Have a Life
                          I do this stuff on the weekends too

                          Comment

                          • richmods
                            Technician
                            • Aug 2013
                            • 91

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

                            Originally posted by BillyCarpenter
                            Yep.


                            How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows



                            See link for instructions:


                            How to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows | Microsoft Docs
                            thanks for the link. I have win10 and smb 1.0 working at 500+ customers. The updates that are killing the scanning must be recent because this is the first time I have not been able to resolve an SMB issue.

                            Comment

                            • BillyCarpenter
                              Field Supervisor

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

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

                              Originally posted by n25an
                              Did you verify that the user login and password did not change... for access to smb folder on the destination computer
                              did you verify that the user login is admin...
                              Did you verify that the hostname of the computer did not change...
                              Did you check for IP conflict... by turning off the computer and pinging to it... any response conflict...
                              Did you check for ip conflict... by turing off the copier and pinging to it... any response conflict
                              did you try giving your computer the ip address of the copier and related settings that copier have... turning off the copier... and then tried moving files from your laptop to the destination pc to see if that works... might give some insights...
                              Did you check if the hard drive is full on the destination pc.. that can stop scanning...

                              Is the admin login used for scanning the default admin login for a server... if so it has a limited amount of concurrent connections it can maintain at a time... so if it has over a certain limit then it stops taking requests until it kills one of those connections or it times out... this is a setting that can be set at creation of the account... its a security feature that sometimes causes trouble for scanning... because scanning to folder can trigger this feature if its enabled in the account... fix is to create an admin account with the limited login feature disabled... rarely seen this one...

                              ***did you try enabling smb in additional features...
                              did you turn off firewall on destination pc and test...
                              some antivirus also kill scanning so turn off and test...
                              ***did you check if the destination pc network setting was public if so that will stop scanning sometimes windows will turn it from private to public...
                              *** did you check if the computer has pending windows updates... that can also stop scanning...
                              *** (triple asterisk mark those are the things that have most often killed scanning for me)
                              That's a pretty good checklist. I just saved it in my database. Thanks.
                              Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                              Comment

                              Working...