Server 2012 SMB scan using LD528 (D084)

[oldtech]

Question, customer goes to 2012 set as domain controller and scan breaks. I go out and update firmware (NCS v7.38) and the offsite IT manager says it still don't work. I ask him if he is sure the credentials are correct and the folder share is good. He says yes. I call Ricoh and they tell me that this model even with latest firm won't scan to 2012 if it is configured as domain controller? So my boss contacts our regional Ricoh Rep and he says it should work. Anybody here have one of these working with 2012 domain controller?

[rthonpm]

As a general practice, you really wouldn't want to use a domain controller as a scan destination, but if it's the only server then you may be forced to do it.

The other question is whether the server is Server 2012 or Server 2012 R2, which uses a different version of SMB. Check out the following link for a little more detail there: Windows Server 2012 R2: Which version of the SMB protocol (SMB 1.0, SMB 2.0, SMB 2.1, SMB 3.0 or SMB 3.02) are you using? - Jose Barreto's Blog - Site Home - TechNet Blogs

It may be that the machine will work with Server 2012 (SMB3), but not with the second release (SMB3.2)...

[anothertech]

What version is your system firmware?

[slimslob]

Question, customer goes to 2012 set as domain controller and scan breaks. I go out and update firmware (NCS v7.38) and the offsite IT manager says it still don't work. I ask him if he is sure the credentials are correct and the folder share is good. He says yes. I call Ricoh and they tell me that this model even with latest firm won't scan to 2012 if it is configured as domain controller? So my boss contacts our regional Ricoh Rep and he says it should work. Anybody here have one of these working with 2012 domain controller?

NCS v7.38 is the correct firmware for scan to SMB for Windows 8 and Server 2012.

As a general practice, you really wouldn't want to use a domain controller as a scan destination, but if it's the only server then you may be forced to do it.

The other question is whether the server is Server 2012 or Server 2012 R2, which uses a different version of SMB. Check out the following link for a little more detail there: Windows Server 2012 R2: Which version of the SMB protocol (SMB 1.0, SMB 2.0, SMB 2.1, SMB 3.0 or SMB 3.02) are you using? - Jose Barreto's Blog - Site Home - TechNet Blogs

It may be that the machine will work with Server 2012 (SMB3), but not with the second release (SMB3.2)...

SMB 3.2 to used on both Server 2012 R2 and Windows 8.1. What I have heard is that Windows 8.1 SP1 is fully backwards compatible with SMB 2.0 and 2.1. I haven't tried it yet myself. My guess is that, as rthonpm stated, it has to do with the fact that it is a Domain controller. See the following from OCE. It is for Server 2003 and 2008 but I have a feeling it also applies to Server 2012. If I am correct, you may have to have their IT look into disabling digitally signed communications.
Connectivity Information:Impossible to create a SMB Scan to File destination: Windows Server 2003/Server 2008 (Océ TDS/TCS): ColorWave (CW) 300, CW600, CW600 Poster Printer,CW650, PlotWave (PW) 300, PW350, PW900, Print Exec Workgroup, Publisher Selec

[anothertech]

Any luck getting this going?

[oldtech]

Yes we have it working. I had to deal with an offsite IT guy that assured me the user and log in were good as well as folder shared correct. Our lead connectivity tech finally talked him into letting him web in and check the config. Turns out the user they wanted to authenticate with did not have a good log in or maybe rights. Long story short the v7.38 firmware did work with SMB 3.
Thanks to all who took the time to look and comment.