Windows 10: SMB BranchCache issues

Hi There,We have implemented SMB BranchCache in Hosted environment . Main office/Branch cache .Brach cache server showing when using power shell command get-bcstatus showing connected .But Cache is not effect in Branch cache nor in clients . We have used perfmon tool to see with SMB cache counters/CSC counters Client side cache too but its not showing any cache results .Please help us .Thanks ,Naresh.

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Safety of Login credentials for SMB...

Ok so similar but slightly different question:

Background:

• Storage hosted by my Linksys WR32X Router (see screenshot) with authentication credentials
• SMB v1, v2, and v3 are all enabled on my Win10 PC via the "Enable Features" window (and I've restarted my PC)
• My Windows 10 account uses my MS Live email address as a username and I have 2-step authentication set up as well

A Timeline:

• The NAS successfully shows up and is accessible from the Network page in Win Explorer
• I've successfully mapped the storage to a Network Drive in Windows using the authentication credentials I set in my router's settings page (again see screenshot)
• When I try to access the SMB share via a separate device on my network (my FireTV device running Kodi 17--which supports up to SMB v3), I get caught in an endless loop of it asking for a username and password.
  • I've tried using the credentials I set in my router settings, which worked when I mapped the share to a network drive in windows, and it didn't work in Kodi
  • I've tried un-mapping and re-mapping the share to a network drive using my windows 10 account username and password instead of the credentials set in my router settings, which did not work for either mapping the drive in windows or for accessing it in Kodi
  • I also tried generating an app-specific password via my Microsoft account settings in case the 2-step authentication set on my account was causing the issue (much like you have to do to add your account to Outlook Desktop App when 2-step is set up)

I just want to access my SMB share from my FireTV device (or any network device for that matter) without having to create a new local user. I saw some responses saying that I need to set up a new local account and use it's credentials to map the drive and
then it should work, but is this REALLY necessary? It seems like a redundant workaround...

So, what if I don't want to create a new local user? I like having jut one account on my Win10 PC and that uses my
MS email address as the Win10 Account username.

Any suggestions? What am I missing here? Thanks in advance MS community!

 

How to solve problems with accessing, discovering and connecting to NAS with SMB connection from Windows 10

I am experiencing difficulties with accessing, discovering and connecting to my NAS with SMB connection from Windows 10.

I have tried most of the solutions suggest on the Web, but avail, none of them worked.

• Enabling SMB v2 and restarting
• Checking SMB v1 in Windows components is ticked on
• Etc.

It seems that Microsoft has broken something though their patches

If anyone can supply me with a permanent/ final fix,
not workaround, please post it here.