M3655idn Intermitant Send error 1102 on SMB

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • green4go
    Technician
    • Jan 2022
    • 49

    #1

    M3655idn Intermitant Send error 1102 on SMB

    Hello everyone

    I have a customer that updated their servers (server 2019. DC and file server application) and now they have issues with SMB scanning. You can scan one time and the scans will go through alright and the next time it will error out with a 1102. In order for it to start scanning again, you have to restart the device and hope that it starts working. They keep blaming the device (M3655idn), but when I hook up my laptop with a server 2019 vm to the device, I can scan any type on job big or small and it work 100% everytime.
    Firmware is up to date.

    Has anyone seen a case like this?

    Thanks in advance
  • Ropariva
    Senior Tech

    500+ Posts
    • Mar 2016
    • 628

    #2
    Re: M3655idn Intermitant Send error 1102 on SMB

    Got some screen shots of your machines network set up and SMB set up?
    Could it be a dns issue?

    Comment

    • green4go
      Technician
      • Jan 2022
      • 49

      #3
      Re: M3655idn Intermitant Send error 1102 on SMB

      I don't have the Network Status Page, but it is on a static IP address, GW, and DNS including the domain name. the destination is set to the IP (not the server host name) and path.

      It would test OK from the Command Center RX unless it errored. then the test will error out as well. reboot the machine and you may get it to work until the next time it errors.

      I have tried different user accounts just to eliminate any rights issues. all user accounts i used have have god right to the folders.

      Comment

      • Santander
        Senior Tech

        Site Contributor
        500+ Posts
        • May 2009
        • 768

        #4
        Re: M3655idn Intermitant Send error 1102 on SMB

        Agree with Ropariva, you may have a DNS issue. You said they update the domain controller, are they using static IP addresses? I have seen cases where they set a static IP for the machine but fail to enter the DNS servers IP addresses or even the default gateway. Had a case late last week where the client had moved a machine from one location to another and it would work only intermittently. The overall network was the same but the new location used different DNS servers so it could not always connect to the scan folder which was located on the same server as the old location. Entered the IP's from an old unit for the DNS servers and worked like a charm.

        Comment

        • green4go
          Technician
          • Jan 2022
          • 49

          #5
          Re: M3655idn Intermitant Send error 1102 on SMB

          Thanks for relying.
          All network settings were entered manually. No settings were left to get from DHCP server. The SMB destination used the file server IP rather then the server name.

          Comment

          • PrintWhisperer
            Trusted Tech

            250+ Posts
            • Feb 2018
            • 452

            #6
            Re: M3655idn Intermitant Send error 1102 on SMB

            Originally posted by green4go
            Thanks for relying.
            All network settings were entered manually. No settings were left to get from DHCP server. The SMB destination used the file server IP rather then the server name.
            "Being ignorant is not so much a shame, as being unwilling to learn" - Benjamin Franklin

            Comment

            • green4go
              Technician
              • Jan 2022
              • 49

              #7
              Re: M3655idn Intermitant Send error 1102 on SMB

              Thank for replying. It is set to port 445. Port 139 does not work unless you enable SMBv1 on the server.

              Comment

              • dalewb74
                Service Manager

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

                #8
                Re: M3655idn Intermitant Send error 1102 on SMB

                i had an IT guy tell me once that his kyocera wasn't correctly because the copier had issues. come to find the issues only occurred after he updated his server. after i finally got him to understand that he needed to test the issue by bypassing the server and try the operation directly from a PC. this is after i told him like 3 times to try this. he finally called me back and admitted the process i told him to try in the beginning actually worked. so then he understood it was a server issue, and not the copier. so you might suggest that as an option. good luck, may the 4th be with you..

                Comment

                • PrintWhisperer
                  Trusted Tech

                  250+ Posts
                  • Feb 2018
                  • 452

                  #9
                  Re: M3655idn Intermitant Send error 1102 on SMB

                  Originally posted by green4go
                  Port 139 does not work unless you enable SMBv1 on the server.
                  "Being ignorant is not so much a shame, as being unwilling to learn" - Benjamin Franklin

                  Comment

                  • bronco31
                    Trusted Tech

                    Site Contributor
                    100+ Posts
                    • Aug 2009
                    • 174

                    #10
                    Re: M3655idn Intermitant Send error 1102 on SMB

                    green4go..." when I hook up my laptop with a server 2019 vm" SKILLS!

                    Comment

                    • green4go
                      Technician
                      • Jan 2022
                      • 49

                      #11
                      Re: M3655idn Intermitant Send error 1102 on SMB

                      Worked with the IT group today. After multiple tries with mixed Job sizes. the devices worked every time.
                      However, the difference is that today the offices were closed so their work load was way down and we think the issue is with network bandwidth. We will be checking next week once they are open.

                      Comment

                      Working...