Solved Shared folder access/permissions issue

[HerpDerp]

We have a shared folder on a Server 2003 server that is somehow inaccessible from just one Windows 7 PC. When I try to access it using the UNC I get the error message:-

\\server_name\share_name is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

This operation is supported only when you are connected to the server.

The 'Everyone' group has 'Modify' permission to the folder, Security and Share permissions, so it's not a permissions issue. If I replace the server name with the server's IP address in the UNC it works, so it's not a connection issue. I can connect to another share on the same server with the server name in the path so it's not a name resolution issue. I can log into the PC next to the affected one with the same user account and access the share just fine.

I've tried reloading the DNS and NetBIOS caches. I've tried removing and readding the computer to the domain. Group policy is being applied successfully and the computer's account is in the same OU as the one next to it.

Does anyone have any advice?

 

[Fred Garvin]

Check the Lm Compatibility Level setting in the registry on the 7 box.

Go to HKLM\SYSTEM\CurrentControlSet\Control\Lsa
If LmCompatibilityLevel isn't there, add it as a new Dword value
Set the value to 1
Reboot the 7 box and try again

 

[chev65]

Here is the fix in a bit more detail. This fix works from the group policy level which may work better for you.

This requires that you change the lanman server parimeters in order to get Windows 7 working with older servers. Do these adjustments on the Windows 7 machines that need to connect to the server.

Control Panel - Administrative Tools - Local Security Policy

Local Policies - Security Options

Network security: LAN Manager authentication level
Set to Send LM & NTLM responses only

Set the Minimum session security for NTLM SSP
Disable Require 128-bit encryption

The screen shots below should be helpful.

Reboot all machines after making the adjustment.

 

[HerpDerp]

Thanks guys, sorry to say that neither of these has resolved the issue, and it's starting to happen on other PCs now.

 

[chev65]

Thanks guys, sorry to say that neither of these has resolved the issue, and it's starting to happen on other PCs now.

Most likely which ever A/V or any type of third party firewall you have installed will also cause this sort of problem. You might need to configure the firewall or disable the A/V's.

 

[HerpDerp]

AntiVirus is FEPP, no firewall between PCs and server.

 

[ashish21]

try to access using ip address. find out ip address of server and \\Ip address\share name..

 

[HerpDerp]

Check my original post; I can access the share if I substitute the server name with its IP address.

 

[HerpDerp]

Just to let you know that we decided to reimage the affected PCs. While doing so hasn't revealed the cause, it has at least resolved the issue. Thanks for your replies.

 

[tuturutko]

chev65@
you are my hero
my situation was different. I have File Server on 2008r2 and TS 2003 and TS 2008, but SMB share was available only from 2008R2 not from 2003. I change
"Set the Minimum session security for NTLM SSP"
to Require 128-bit encryption, and everything fly

 

[chev65]

chev65@
you are my hero
my situation was different. I have File Server on 2008r2 and TS 2003 and TS 2008, but SMB share was available only from 2008R2 not from 2003. I change
"Set the Minimum session security for NTLM SSP"
to Require 128-bit encryption, and everything fly

Yes that setting sometimes requires adjustments for Windows 7 to work with older servers. It's a pretty common adjustment with lots of references at TechNet.

Lucky HerpDerp had those images handy, very wise Herp.