Added 2012 R2 domain controller, can't scan via SMB now
Posted on 2013-10-23
Could be bad timing, but. . . We added a 2012 R2 domain controller yesterday to our existing infrastructure (Which additionally contains a 2003, 2003R2 and 2008R2 domain controllers. The 2003 and 2003R2 are being migrated out.)
For ease of discussion, our domain controller is called DC001. The server we scan to is called FILEDC201. The FILEDC201 is the 2008R2 domain controller and just happens to be what we scan to (Remote/small office, so it has both roles.)
Since adding the 2012 R2 domain controller, we can no longer scan to FILEDC201. We have a Kyocera that does SMB to FILEDC201 and gives us almost nothing for an error message. I've verified settings and tried changing the port from 139 to 445.
I am familiar with the changes with SMB (To 3.0) beginning with Server 2012. However, since we're scanning to Server 2008R2, I didn't expect any issues.