<div>
Have you tried using the ip address of the file server instead of the host name?<br />
On a few occasions, use the ip address then browse to the folder. If that works then you may have a dns or domain naming issue.
</div>


Have you tried using the ip address of the file server instead of the host name?
On a few occasions, use the ip address then browse to the folder. If that works then you may have a dns or domain naming issue.

<div>
As usual with technology, just started working.
</div>


As usual with technology, just started working.

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


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.  

Thoughts?

Added 2012 R2 domain controller, can't scan via SMB now

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.