Utax DC 6240 SMB error 1105

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • numarkDM1050
    Technician
    • May 2025
    • 12

    #16
    By default, the file name is set to include the date and time.
    I can't find the option to change the file name anywhere in the printer menus.

    Comment

    • PrintWhisperer
      Trusted Tech

      250+ Posts
      • Feb 2018
      • 464

      #17
      System Menu->Send Functions->File Name Entry would be the usual place but I'm still not sure what (US) model you are on, so you'll need to find an Operation Guide on your own.

      I looked over the Wireshark again, and it has 3 tries which is typical for a Network scan attempt.
      "Being ignorant is not so much a shame, as being unwilling to learn" - Benjamin Franklin

      Comment

      • numarkDM1050
        Technician
        • May 2025
        • 12

        #18
        There is no such option in the web settings of the machine.
        On the machine itself : Functions -> Enter file name entry ->
        -> None
        -> Data and time
        -> Job No.
        -> Job No. & data and time
        -> Data and time & Job No.
        I tried them all and the error is still the same.

        Comment

        • PrintWhisperer
          Trusted Tech

          250+ Posts
          • Feb 2018
          • 464

          #19
          Well congratulations, I'm stumped. The device simply stops before issuing the SMB_Create_Request and there is no indication of why in the trace that I can see.

          You should attempt SMB scan to a Windows share (running wireshark) as a test on this machine. If it fails as well then the machine is suspect.

          SMB steps in the trace:
          SMB2 Negotiate - Attempted with success to dialect SMB 2.* (wildcard)
          SMB2 Session Setup - Attempted with success NTLMSSP Auth for WORKGROUP\Ivo (user), GSS token issued
          Tree Connect Request - Resolved to share \\172.18.4.44\123 with read write access. (123 sharename? Permitted but yuck)

          To proceed, the machine must send the SMB_Create_Request to open the share and negotiate the file transfer...but it never does and instead (within milliseconds) sends a Tree Disconnect and Session logoff.

          This indicates that the Send Operation is stopped by failure or intention in the machine programming at the point when it should create a file and send it. If it was an internal programming or hardware (memory) error I would expect some kind of System Error code.

          Load known good firmware.





          "Being ignorant is not so much a shame, as being unwilling to learn" - Benjamin Franklin

          Comment

          Working...