Newly deployed Windows 7 workstations cannot access Windows server 2003 file shares
We are rolling out Windows 7 workstations. Users are having issues accessing folders that they used to be able to. We checked the permission carefully at the folder and share level and all looks right. Any suggestions as to how to fix.
The server we are accessing is Windows server 2003.
August 7th, 2012 4:07pm
There are several procedures that may help:
1. Force W 7 to use SMB 1 instead of SMB 2:
sc config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc config mrxsmb20 start= disabled
(Return path
sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc config mrxsmb20 start= auto
)
2. Autotuning
netsh int tcp set global autotuninglevel=disabled
3. Heuristics
netsh int tcp set heuristics disabled
4. Is this workgroup or Active Directory?
5. It is helpful to analyze network traffic (eg. Wireshark)
Regards
Milos
Free Windows Admin Tool Kit Click here and download it now
August 7th, 2012 4:16pm
Milos,
So I assume we would run this on the fileserver sharing up the files/folders?
This is AD not workgroup.
One note of interest, if we provide the user Domain Admin privledges (temporaily) the problem goes away
Thanks,
Chris ...
August 7th, 2012 4:32pm
Hi Chris,
Please check if this KB You cannot access shared files or shared printers in Windows 7 or in Windows Server 2008 R2 helps.
If not, please try the following:
1. Temporarily disable the firewall and anti-virus program
2. What about to access the share folder by \\XXX.XXX.XXX.XXX<IP Address>and see how it works?
3. Test the issue in
Clean Boot.
Hope this helps.
Vincent Wang
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
August 9th, 2012 5:08am
Hi Chris,
Please check if this KB You cannot access shared files or shared printers in Windows 7 or in Windows Server 2008 R2 helps.
If not, please try the following:
1. Temporarily disable the firewall and anti-virus program
2. What about to access the share folder by \\XXX.XXX.XXX.XXX<IP Address>and see how it works?
3. Test the issue in
Clean Boot.
Hope this helps.
Vincent Wang
TechNet Community Support
August 9th, 2012 5:18am