IR 3320/6750 printing via SMB

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sizemore
    • Nov 2024

    IR 3320/6750 printing via SMB

    I have 7 imageRUNNER printers of various makes/models. The problem we are experiencing is scanning to an SMB share. The problem began about 2-3 months ago.

    The configuration of the printers are all identical. I have one machine that is successfully scanning to the shares. 6 of the machines are not.

    We've checked and doublechecked the settings for scanning to the share. No changes have been made to the servershare to block access (Rights/ACLS/GPO Blocks etc.). Nor has any work been done to routing equipment.

    We've monitored the traffic logs using Wireshark to the machine and its been noted that the difference between the machine that works and those that do not, is that the instance after login, an SMB packet is sent to create the file. However on the machines that don't work it jumps to TCP transport. Then it fails three times and spits out the nice "You failed (to scan to the share)" error page.

    At this point we're shy of calling in support and flashing the firmware to try a "reset" test.

    So my two questions are after giving the background on the issue:

    1. Is there a way to reset the software to factory defaults or as delivered?
    2. Has there been an issue like this in the past and how has it been resolved?
  • sizemore

    #2
    <bump>

    Comment

    • Copier_Guy
      Senior Tech

      500+ Posts
      • May 2007
      • 543

      #3
      I'm not too sure about the way you have the equipment setup, so I can't really answer your question as to why it's not working. Questions:
      1. Did the setup work when you first set it up and how long?
      2. Do you have SMB activated on all the machines?
      3. Have you tried using Network Scan Gear for your scan needs from these machines? It's a free download on the Canon website and works well with all the iR models.

      Comment

      • sizemore

        #4
        Hey,
        Thanks for the reply!

        It worked since it was setup which has been easily 6 mos or more with SMB enabled. Is there a way to print all the configurations as with HP machines?

        The Network Scan Gear appears to be a local installation on computers is that the case?

        Tx,
        T
        Last edited by Guest; 09-05-2007, 01:46 PM.

        Comment

        • Copier_Guy
          Senior Tech

          500+ Posts
          • May 2007
          • 543

          #5
          To print the configuration, you have to go into level 1 diagnostics. Press keys: (Additional Functions *), 2 and 8 simultaneously, (Additional Functions *). You then select: Copier>Function>MISC-P, which will take you to the service print pages. P-PRINT will print service mode setting values, USER-PRT will print the user mode list and LBL-PRNT will print the service label. If the setup was working for 6 months before it crapped out, it sounds like your network is probably the problem. I know you say you checked everything, but you have to keep in mind the network, the servers and hosts are ever changing due to updates and so forth. There's a lot that could have affected your setup. Security updates, malware updates, we could go on. Do any of the Machines have Universal Send?
          You could use that feature to scan to your network share. If not, you may be better off going with the normal scanning to desktop feature. Let us know what happens or what you find.

          Yes, the Network Scan Gear is a local setup.

          Comment

          • sizemore

            #6
            Someone that knows something!!!! Jesus I have been saved!!!! Let me plug away on printing the configurations and will post ASAP/ATP.

            Tim

            Comment

            • sizemore

              #7
              In comparing the User Data List (Network) the only difference between the two is IPP is turned on, for the machine that doesnt work. Would this make a difference with scanning to SMB/Share?

              Comment

              • Copier_Guy
                Senior Tech

                500+ Posts
                • May 2007
                • 543

                #8
                It may. You did say that when the SMB packet is sent, the machines that don't work switch to a TCP Transport. I believe IPP stands for Internet Protocol Printing. I may be wrong, it's been a long time since I stuck my nose in a book, and please correct me if I'm wrong. From my limited knowledge, I believe TCP and IP are relative to each other. In other words and to get to the point, turn off the IPP and see what happens. You may have just solved your problem. Sorry for the tangent.

                Comment

                • sizemore

                  #9
                  I finally figured it out. It turns out that the AD admins in advertently pushed down a policy to the server turning on digital signatures for communication. IR Printers do not fully support digital signing.

                  Turned off the GP and everything works out great!

                  Thanks CG for all your help!

                  Tim

                  Comment

                  • Copier_Guy
                    Senior Tech

                    500+ Posts
                    • May 2007
                    • 543

                    #10
                    Great!!!

                    I'm happy you figured it out. That is definately something to keep in mind when setting these printers up on a secure network. Thanks for getting back to us and letting us know how it went.

                    Comment

                    Working...