Canon iRC3200 - Windows SMB Scan Error #751

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • phorts
    Guy

    50+ Posts
    • Sep 2007
    • 59

    #16
    Originally posted by SmudgerUK
    If you are using Windows 2003 have you disabled both digital signings in group policy or just one? Canon were advising on one only through their help desks. I have a word doc that I can email you if you wish on changing both.

    I have just learned that they have scan locations on two servers, one is a 2003 Server and one is a 2000 Server. I beleive we only edited one policy on the 2003 server.. Here is the document I was following for that:

    Universal Send to push a file to a SMB share

    Comment

    • SmudgerUK
      Technician
      • Mar 2008
      • 17

      #17
      That is pretty much the same as my doc but I have screen shots in mine. The 2000 server should not require this to be set.
      Is this happening just after or as the copier goes into sleep mode? I have had some issues with older hubs/switches going offline or halting functions after the copier has entered sleep mode. Try setting it to 4 hours to see if it happens less.
      I have just flicked through some of the system software bulletins and can't find anything for dropping off the network in the recent ones, maybe worth ensuring you have the latest.
      You have me beat, this is a strange one indeed.

      Comment

      • phorts
        Guy

        50+ Posts
        • Sep 2007
        • 59

        #18
        Originally posted by SmudgerUK
        That is pretty much the same as my doc but I have screen shots in mine. The 2000 server should not require this to be set.
        Is this happening just after or as the copier goes into sleep mode? I have had some issues with older hubs/switches going offline or halting functions after the copier has entered sleep mode. Try setting it to 4 hours to see if it happens less.
        I have just flicked through some of the system software bulletins and can't find anything for dropping off the network in the recent ones, maybe worth ensuring you have the latest.
        You have me beat, this is a strange one indeed.

        Thanks again for the reply. Do you think you could forward me that doc anyhow? Alot of times I send my link over to customers and they're a little clueless...actually, pretty much every time A Guide may help...

        I was thinking the same on the Sleep Timer. They say it's happening 1-3 times per day. And not sure if I mentioned this before, but it's happening on BOTH of their machines. They do a good deal of scanning/printing/faxing from these machines, so i'm really not sure it's timeing out.. but maybe it's set to something low like 30 minutes. I'll definitely check it out.

        If/When I go out I will definitely get them up to the latest firmware.. as i doubt that they are.

        Thanks again for the reply. and if you can email me that doc my email is:

        phorts@hotmail.com

        thanks!

        Comment

        • SmudgerUK
          Technician
          • Mar 2008
          • 17

          #19
          It's in cyber space now.
          Cheers
          Dave

          Comment

          • phorts
            Guy

            50+ Posts
            • Sep 2007
            • 59

            #20
            Back Again..Same Problem

            Ok, so I'm back and I come bearing bad news. Not only is the problem still not resolved at my previous 2 customers, but I have another customer who has been going strong now for 6 months and all of a sudden he's having the SAME problem described in this thread, same machine, same error, EVERYTHING.

            In order to work around the issue with one of our clients (The p2p network), I had them switch to scan to email. They are now scanning happily and without interruption, but the scan to file (via SMB) is still not working!

            In the corporate environment, they are STILL rebooting BOTH of their machines multiple times per day in order to restore scanning. This is beyond the point of annoyance and may ultimately lose the contract for us. The IT guy over there is a good friend of mine and we've done EXTENSIVE network testing and ALL other network resources are functioning flawlessly. It's very very disappointing and frustrating that this issue will NOT go away and no resolution can be found.

            THis new customer is similar to the first, a small p2p network. Scanning for 6 months no problem, now all of a sudden, it will just fail. I DO have some new information however:

            I changed the timeout settings from 90 mins to 10 mins and restarted the machine. I tested a scan upon restart and it went through as expected. I waited 15 mins and tried again, FAIL. Test print, RUI, ping...all OK.

            I then changed the timeout to 4 hours and restarted the machine. Tested scan on restart - OK. I then forced it into sleep by pressing the On/Off button, waited a minute, and pressed the On/Off button again and tested - FAIL!

            Currently I have the machine maxed out on the timer settings for Sleep and Low Power Mode to 4 hours, hoping that it will only need a restart in the morning to resume scanning capabilities.

            This will be just a temporary solution. I need a permanent one.

            Has ANYONE found ANYTHING on this? This is my 4th customer in the matter of a few months with this issue and I can't imagine they'll be the last. I'm desparate now!


            Thanks for ANY insight you may have..

            Comment

            • phorts
              Guy

              50+ Posts
              • Sep 2007
              • 59

              #21
              Well, so much for that theory. Customer called back 30 minutes after restart and it failed to scan. SO, apparantly the whole timeout test was just a coincidence.

              I called another dealer who seems to think it's an issue with IP conflicts. I have a hard time beleiving this since we saw no evidence of network conflicts in both my other test networks, but may reinvestigate this with the new customer.

              ugh.

              Comment

              • trex0314

                #22
                NETBIOS of TCP

                Guys,
                I had no problems with this until I disable Netbios on the server receiving the scanned files. Turned it back on and now it works.

                For me the challenge is getting it to work without Netbios over TCP\IP.
                Hope this helps;

                Comment

                • phorts
                  Guy

                  50+ Posts
                  • Sep 2007
                  • 59

                  #23
                  Were you experiencing the same problem I was? Where the machine would work for awhile and then all of a sudden fail to receive SMB scans, yet still remain able to print, get RUI, etc?

                  Also, two of my clients that are experiencing this issue are p2p networks and are using Windows XP machines as their file servers. The default for Netbios on a WinXP machine is the following:

                  Default: "Use NetBios Setting from the DHCP Server. If static IP address is used or the DHCP server does not provide NetBios, enable NetBios over TCP/IP."

                  Other options are "Enable NetBios" and "Disable NetBios".

                  It would appear that, since they are not receiving NetBios settings from any server, and since i doubt their gateway is providing NetBios, that the default setting is enabling NetBios.

                  Should I just tick the "Enable NetBios" button to be sure?

                  Thanks for your help

                  Comment

                  • trex0314

                    #24
                    Enable Netbios

                    My problem is not exactly the same as yours and it only occured after I disabled Netbios Over TCP/IP. I would try enabling it like you said to see what happens. However, I am also sure what you mean by P2P network?

                    Comment

                    • phorts
                      Guy

                      50+ Posts
                      • Sep 2007
                      • 59

                      #25
                      Ok, yeah it didnt sound like it was the same issue.

                      and by p2p (peer to peer) network i meant that it's a simple workgroup, no server.

                      Comment

                      • Techiechic

                        #26
                        Originally posted by phorts
                        This is happening at two different customers of mine. I can't find this error code in the manual for this machine and I can't find it online anywhere. The only way the customer is able to resolve the issue is to restart the machine.

                        Networks differ at each customer. One is scanning to a Win2k3 Server and one is scanning to XP/Vista machines in a P2P network. Scanning will be working fine, and then all of a sudden stop working.

                        It will say "sending...sending....resending"... and then sit on resending.

                        I am trying to get more information from each customer.

                        Can anyone tell me what Error #751 is and how to resolve it?

                        thank you!

                        Hey

                        I got the same error here. Its a total mystery. The poor helpdesk lads are rebooting cannon printers all the time due to error #751 and not being able to scan. We are scanning to a file share on a nas box

                        Did you fix your issue?

                        Techiechic

                        Comment

                        • CBSPJ

                          #27
                          I just had the exact problem with both an IRC5185 AND an IRC3380 at the same location. After using a packet analyzer we found nbstat traffic indicating WINS replication. We turned OFF WINS on the ImageRunners and they both worked.

                          Comment

                          • bubblegoose72
                            Technician
                            • Jun 2008
                            • 49

                            #28
                            smb...

                            I too am dealing with this, and have an open thread. All the common sense network stuff is in order and still I have this failure. I'll let you know if I stumble on it first.

                            Good Luck,

                            Chris

                            Comment

                            • bubblegoose72
                              Technician
                              • Jun 2008
                              • 49

                              #29
                              Try this...

                              This is going to be my next step...

                              Fix for SMBC lib failed to tree connect error in Printers/scanners | Windows Reference

                              Chris

                              Comment

                              • Techiechic

                                #30
                                Originally posted by Techiechic
                                Hey

                                I got the same error here. Its a total mystery. The poor helpdesk lads are rebooting cannon printers all the time due to error #751 and not being able to scan. We are scanning to a file share on a nas box

                                Did you fix your issue?

                                Techiechic

                                Hi

                                Just to let you know we resolved our error. The location of the files on the server did not have a wins entry on the server. There for the printer kept loosing network connectivity. wins was then turned back at the printer level..

                                Comment

                                Working...