Server 2012 SMB 3.0 file cluster issues with Streaming media services 2008 R2
-
Thursday, October 18, 2012 5:11 AM
So I have a file server setup with the always available feature turned off on this brand new cluster. Everything seems to function normally and I can hit files from the shares no problem.
My issue I built a brand new 2008 R2 machine and created an on-demand publishing point to point to my 2012 file share cluster. I created a windows account for my windows media service to run as and applied read only to my video share. Media services see the video files on the server in the GUI so I know its got connectivity, but when I go to test locally or externally it will not play the stream at all. It complains of access even know I know that is not the issue. I have verified the setup and the ACL stuff is turned off on both the root and the publishing point. I can login to the Media server as my service account and play files from the share no problem. IIS media services can stream the files with no problem and yeah everything seems more like something possibly with SMB 3.0 and something in media services.
I have a country rule where my data is not allowed in other countries so I have multiple video services on a domain with tunnels and what not my US Streaming services is working great but has a server 2008 R2 file cluster server. If I take that one to my out of the country publishing point to test it streams great as they use the same services account. If I take my out of the country file share to the US I get the same result just will not work. I have poke prodded and banged my head and since I get this result I have concluded it must be something with the new security of SMB 3.0.
Does anyone have this working or tested? Also I am using the exact same video file to test all of this. Or is there secret I missed to either make smb 3.0 even more compatible or make streaming services play nice.
Anything helps please let me know.
Thanks,
Adam
- Edited by Jugganutz1871 Thursday, October 18, 2012 5:11 AM
All Replies
-
Thursday, November 01, 2012 2:34 PMOwner
I'd recommend calling in for support on this one. Things aren't adding up. Probably the most useful thing to do would be to do a network trace of the WMS server connecting to the remote server over SMB.- Marked As Answer by David Bristol [msft]Microsoft Employee, Moderator Thursday, November 01, 2012 2:34 PM

