ir 7095 not scanning to network

[Guest]

Greetings,

We have an ir 7095 that just doesn't want to work right. First what it DOES do. All users are able to print to the printer. When searching for a network printer it shows up perfectly for all users. Also, it has no problem scanning and emailing a pdf document.

However, it will not scan over the network. We have tried all of the obvious solutions and have made sure that for permissions "everyone" has full permissions. The Canon techs have been out several times and we're still stuck.

We recently upgraded to SBS 2008 and the problems started right after that. Everything else has gotten back to normal except the scanning over the network. This has been going on for several weeks now and we're at the end of our rope.

Any ideas? (please!)

[SCREWTAPE]

Greetings,

We have an ir 7095 that just doesn't want to work right. First what it DOES do. All users are able to print to the printer. When searching for a network printer it shows up perfectly for all users. Also, it has no problem scanning and emailing a pdf document.

However, it will not scan over the network. We have tried all of the obvious solutions and have made sure that for permissions "everyone" has full permissions. The Canon techs have been out several times and we're still stuck.

We recently upgraded to SBS 2008 and the problems started right after that. Everything else has gotten back to normal except the scanning over the network. This has been going on for several weeks now and we're at the end of our rope.

Any ideas? (please!)

Greetings Byran.

Weclome.

Do you mean scan to file folder on you network (SMB)?

[BryanGarner]

Greetings Byran.

Weclome.

Do you mean scan to file folder on you network (SMB)?

exactly... it gives error #751

[SCREWTAPE]

exactly... it gives error #751

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.1\file

Incorrect example:

Host Name: //192.168.1.1/file

I have also seen examples where you get a #751 error if a software based firewall is enabled on the target computer like norton antivirus SW. Try disabling the firewall and retest the SMB send job. If the file gets sent successfully with the firewall disabled an exception will need to be made in the settings of the firewall program.

In addition, a #751 code can occur if the destination computer that you are attempting to send to is not running SMB.

Have you even created a folder on you network yet.
Have you set up a address under address book setting.

[BryanGarner]

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.1file

Incorrect example:

Host Name: //192.168.1.1/file

We have also seen examples where you get a #751 error if a software based firewall is enabled on the target computer. Try disabling the firewall and retest the SMB send job. If the file gets sent successfully with the firewall disabled an exception will need to be made in the settings of the firewall program.

In addition, a #751 code can occur if the destination computer that you are attempting to send to is not running SMB.

Thanks for that screwtape. I had found that info in this post and made sure that my slashes were all correct. We have also made sure that there is a firewall exception and even when we attempted to scan with the firewall disabled our scans were not delivered.

[SCREWTAPE]

Ok this is what a 751 refers to:

-The computer name or IP address to the destination is not
correct.
-The destination computer is down or not functioning.
-The network is down; the server is not reachable.

-Not able to establish connection to the destination.

And what to check:

-Check and verify that the computer name or IP address to the
destination is correct.
-Check and verify that the destination computer is up and
running.
-Check and verify that you have a valid DNS server IP address.
-Try pinging the computer name to se if it resolves to the correct

IP address