SMB scan to folder problem, Canon IR c3100n

[kevindv10]

I've searched on related items but haven't come up with a solution.

I have an ImageRunner c3100n on a W2K3 domain. I just swapped out an old W2K domain controller with which scanning to the shared folder worked. All users/passwords/permissions were duplicated directly from the old server to the new. The new server also has the same IP address and domain name as the old server.

I've disabled/enabled all the suggested SMB settings on the Domain Controller's Security policy but to no avail.

I'm at the end of my rope here!! Anyone have anymore ideas before I blow a gasket?????

[TheOwl]

Which SMB security settings have you enabled / disabled? Is the 2003 Server a Small Business Server?

[kevindv10]

The server is 2003 SE.

I've tried a variety of combinations of the settings below, all under Computer Config>Windows Settings>Security>Local Policies>Security Options:

Microsoft Network Server: Digitally sign...(always) set to Disable.
Microsoft Network Server: Digitally sign...(when permitted set to Enable.

Microsoft network client: digitally...(always) set to Disable.
Microsoft network client: digitally...(permitted) set to enable.

I've also tried Domain member settings.

I also came across a post about allowing NTLM authentication which I tried but still didn't have any success.

After every change I always gpupdate /force.

Thanks for the quick response.

[TheOwl]

Is the machine reporting a reason why the the scan failed?

Here is what I would do to test the machine.

1. Make sure that the username / password hasn't expired or the account is locked.
2. Setup a share on a laptop / workstation and test.
3. If possible, use a local user name and password on your server.
4. Check the Event log and security to see if the machine is attempting a logon.
5. Try the fully qualified username (ie. copier@test.local).
6. Make sure the copiers username has privilages on the parent directories which contain the share.
7. Upgrade the firmware in the machine.

You could also try using the administrator username and password as I have seen user accounts become corrupted which stops the machines logging on successfully.