SMB 3.0 fails from one office to another

i've started using server 2012 take advantage of de-dup. switched on surface tablet recently. while setting new sccm 2012 environment noticed couldn't navigate unc path on main sccm server.

today realized latest oses (either windows 8 or server 2012; i'll 2012 on) can't perform file sharing 2012 system isn't local.

let's assume following (fake ips):

office austin, tx

* server a1, server 2012, 100.1.2.100
* server a2, server 2012, 100.1.3.100
* server a3, server 2008, 100.1.2.101

office boston, ma

* server b1, server 2012, 10.2.2.100
* server b2, server 2012, 10.2.3.100
* server b3, server 2008, 10.2.2.101

unc/ file sharing works a1 a2, fails a1 b1 or b2. conversely, boston servers can't use file sharing austin. a3 , b3 (server 2008) can access 6 servers.

can ping of them, rdp them, etc. unc ip address fails, it's not dns issue. on windows firewall domain firewall turned off (and block locally if issue).

appears server 2012 -> 2012 communication uses smb 3.0. i'm having firewall guy port 445, however, article confuses me: http://support.microsoft.com/kb/204279

>  if both direct hosted , nbt interfaces enabled, both methods tried @ same time , first respond used.

sounds me it'd use smb 2.0 when smb 3.0 blocked. 445 port used active directory, works cross office. ideas? should have networking guys at? never had problem smb 2.

check if smb1 or smb2 enabled.

use powershell ise:

get-smbserverconfiguration | select enablesmb1protocol, enablesmb2protocol

to enable:

set-smbserverconfiguration -enablesmb1protocol $true

set-smbserverconfiguration -enablesmb2protocol $true

check if helps solve issue.  :)

---

every second counts..make use of it. disclaimer: posting provided no warranties or guarantees , confers no rights.
it stuff quick bytes

Windows Server  >  Windows Server 2012 General