SMB not working after latest Windows 11 update

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BillyCarpenter
    Field Supervisor

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

    #1

    SMB not working after latest Windows 11 update

    I have not found a good resolution to this problem. Having the problem with multiple computers and multiple locations. Just a heads up.
    Adversity temporarily visits a strong man but stays with the weak for a lifetime.
  • bsm2
    IT Manager

    25,000+ Posts
    • Feb 2008
    • 29942

    #2
    Wow nothing changes with the lack of information

    What's the failure code?
    Scan to PC or server?.
    Using host name or ipaddress ?

    Comment

    • dalewb74
      Service Manager

      Site Contributor
      1,000+ Posts
      • Feb 2018
      • 1135

      #3
      firmware is up to date? smb 1-3 is on or off? firewall? software blocking it? i agree with bsm2..... as johnny 5 said need more input.

      Comment

      • BillyCarpenter
        Field Supervisor

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

        #4
        Originally posted by dalewb74
        firmware is up to date? smb 1-3 is on or off? firewall? software blocking it? i agree with bsm2..... as johnny 5 said need more input.
        I didn't go on these calls, our technician did. But here's the information:

        - Firmware up to date
        -1101 and 2202 are the error codes - I don't think either are the problem.
        - SMB is on. He even tried enabling SMB 1
        - Tried with firewall off
        - Don't see any software that is blocking SMB

        This problem didn't occur until the latest windows 11 update...according to our tech. And it's happened on 2 machines at 2 different locations. But the fact that no one on this site has reported any issues makes me skeptical that a Window update is the problem. I'm going out there tomorrow. We have them temporarily set up on scan to email.

        Today I tried to recreate the problem on a Windows 11 machine at our shop and I had no problem whatsoever. So there's that.


        Adversity temporarily visits a strong man but stays with the weak for a lifetime.

        Comment

        • ihatefinishers13
          Senior MFP Technician

          500+ Posts
          • Feb 2020
          • 680

          #5
          Originally posted by BillyCarpenter

          I didn't go on these calls, our technician did. But here's the information:

          - Firmware up to date
          -1101 and 2202 are the error codes - I don't think either are the problem.
          - SMB is on. He even tried enabling SMB 1
          - Tried with firewall off
          - Don't see any software that is blocking SMB

          This problem didn't occur until the latest windows 11 update...according to our tech. And it's happened on 2 machines at 2 different locations. But the fact that no one on this site has reported any issues makes me skeptical that a Window update is the problem. I'm going out there tomorrow. We have them temporarily set up on scan to email.

          Today I tried to recreate the problem on a Windows 11 machine at our shop and I had no problem whatsoever. So there's that.

          It's highly possible that when their computer came back on after an update, that they reconnected on the "Public" network, which would block scanning with that error. That's one of the first things to check when troubleshooting scanning for us

          Comment

          • Don N.
            Trusted Tech

            250+ Posts
            • Nov 2011
            • 409

            #6
            A tech told me yesterday that after trying everything, an IT guy uninstalled SMB service from W and reinstalled it. Fixed.

            Comment

            • BillyCarpenter
              Field Supervisor

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

              #7
              Originally posted by ihatefinishers13

              It's highly possible that when their computer came back on after an update, that they reconnected on the "Public" network, which would block scanning with that error. That's one of the first things to check when troubleshooting scanning for us

              Yeah, he checked that. A couple of years ago someone posted checklist on this site and it covered everything to check, including pending updates that can some times break SMB. I wish I could remember his name.

              Adversity temporarily visits a strong man but stays with the weak for a lifetime.

              Comment

              • carolscurriculum
                Technician
                • May 2017
                • 38

                #8
                Originally posted by BillyCarpenter
                I have not found a good resolution to this problem. Having the problem with multiple computers and multiple locations. Just a heads up.
                It could have something to do with the Microsoft internet outage.

                Comment

                • BillyCarpenter
                  Field Supervisor

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

                  #9
                  Originally posted by carolscurriculum

                  It could have something to do with the Microsoft internet outage.
                  SMB isn't internet dependent. It's intranet dependent.

                  Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                  Comment

                  Working...