2012 R2 File Server Access

I recently upgraded a File Server to Windows 2012 R2 Datacenter.  Everything went well and worked fine for weeks.  

A couple of days ago I enabled de-duplication on the server.  Now, I have one XP Professional Client and three Sharp MFP machines that cannot access the file server, or any of the SMB shares on the server.

When we try to scan to a network folder we get a send error code 80-0000.

I know that others have seen this before, but I haven't found a resolution to this issue.  Any assistance would be greatly appreciated.

Thank you,

Greg SartinAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Make sure the SMB1.0/CIFS feature is installed. Most MFPs nor XP can talk SMB2 or 3. I'm guessing it got removed around the same time dedup got turned on.
Greg SartinAuthor Commented:
I have confirmed that SMB 1.0/CIFS is installed.  

When browsing from the XP machine, I can see the file server, but none of the shares.  It's like network discovery is not enabled, but it is.  

I have set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel value to 0 so that the file server will send LM & NTLM responses.  

I have tried to get an error to present itself in the logs, but the XP client can't even see the shares to try and connect to them.
Cliff GaliherCommented:
Network discovery does not control shares. Inky machine and device visibility. Allowing LM is a huge security risk. Even with XP, which as old as it is, still supports NTLMv2. Dedup happens at the filesystem level, lower than the networking stack that presents SMB to connecting devices, so enabling it would not impact file sharing. Something else was changed.
Greg SartinAuthor Commented:
Cliff,  Thank you for chiming in.  I agree with everything that you have stated above.  Sometimes it just helps to have someone to bounce things off of.  I resolved my issue by uninstalling SMB 1.0.CIFS and then re-installing the feature.  Somehow the feature became corrupt.  I was able to identify this using the Best Practices Analyzer.  It said that SRV.sys was not running.  Even after running "sc config srv start=demand", BPA said the same thing.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.