Thanks:
0
Likes:
0
Dislikes:
0
-
Guy
50+ Posts
- Rep Power
- 34
Canon iRC3200 - Windows SMB Scan Error #751
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!
-
Trusted Tech
50+ Posts
- Rep Power
- 34
There is a possible problem with the scan motor. Not sure if that's the code you would get
-
Possible Work Around
According to Canon:
Workaround :
An SMB send job can fail with error code #751 if the user enters forward slashes (/) when specifying the destination. Back slashes (\) must be used when specifying the destination, not forward slashes (/).
Correct example:
Host Name: \\192.168.1.33\share
Incorrect example:
Host Name: //192.168.1.33/share
In addition, a #751 code can occur if the destination computer that you are attempting to send to is not running SMB. For example, if you attempt to send via SMB to a NetWare Server that is not configured for CIFS, it will fail with a #751 code.
-
Guy
50+ Posts
- Rep Power
- 34
Why then does it work sometimes and then fail..rendering the scan feature non-functional until a restart is performed?
Seems to me like it somehow loses communication to the host it is scanning to... addresses are entered correctly since it DOES work....albeit not consistently.
It seems to be a SMB communication error... I just dont know what to do about it or even how to track it.
-
Guy
50+ Posts
- Rep Power
- 34
Why then does it work sometimes and then fail..rendering the scan feature non-functional until a restart is performed?
Seems to me like it somehow loses communication to the host it is scanning to... addresses are entered correctly since it DOES work....albeit not consistently.
It seems to be a SMB communication error... I just dont know what to do about it or even how to track it.
Also, at the end of the transmission, one customer reports seeing a message blink quickly saying "No Response".
Why does it all of a sudden lose communication w/ the host?
-
follow up
You may have already considered these, but I'll throw them out for review.
1. Does the computers that you are scanning to have static IP addresses?
2. When SMB "push scan" fails, can you still Ping the copier?
These may not help you, but your responses may help us zero in on the problem. I have never liked SMB scanning to P2P because, like your customers, sometimes the copier has to be rebooted to "see" the other computers on the network.
-
Guy
50+ Posts
- Rep Power
- 34
Thanks for the input.
In the P2P install the customer has been having problems with their router not responding to DHCP requests (this is from their IT guy) which would tell me that their IP's are assigned automatically rather than static. Not sure why this would change anything though since the host name/share would remain the same regardless. They are having a new router installed this week.
In the other scenario, the scans are going to a server, which is static. They are experiencing no other network problems. The other 2 copiers on their network (non canon) are scanning to these folders w/o any problems. All computers accessing these shares are all terminals (about 50) and have no major network problems...
In both cases, we can not only ping the copier, but can print to it and receive the Remote User interface through IE.
It's very strange indeed.
One other important discovery I just made was that, when the copier is in this "No scan" state, and go to add a new scan location into the address book by hitting "Browse"... it comes up and says "No Response" or the equivalent... The network is gone...it can no longer "see" the network..but we can see it..
wth. How can we keep this alive?
-
Sounds just like the problem I had on an IRC3200. I had to make the IP a static address for the P2P computer and, if I remember correctly, code in the IP address instead of the computer name for the share - based on Canon's recommendations. This may still not work, but it is something to ponder. If I think of anything else, I'll let you know. Good luck!
-
Guy
50+ Posts
- Rep Power
- 34
That sounds very plausible....
I will give this a try, thank you very much for this info.
-
scan issue
sounds like a timeing issue like timing out? or memory allication issue.
people wonder why we drink.
canon boxes can be so picky verses other box's
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
Bookmarks