2
I am trying to set up File sharing on a friend's machine who is using Windows 7 64 bit Ultimate edition. In advanced sharing settings, I select the radio button "Turn on file and printer sharing" and click on Save Changes. But when I come back to the screen, it reverts back to off.
I searched on the net and found many people facing similar issues, and I tried many steps like turning off WIndows firewall, netsh command, checking predefined rules in Firewall, starting the Server service and HomeGroup Listener service, verifying all required services are started, group policy editor, running the troubleshooter, etc, but nothing seems to be working in my case.
I am not able to see this computer in the Network Places, even though Network Discovery is on. The computer is connected to internet using a wireless connection. The HomeGroup troubleshooter says "Some Homegroup problems are network related" but the network troubleshooter does not find any problems.
Is there no tool to forcibly turn this setting on?
Will really appreciate any help on this. Already spent a lot of hours on this simple yet nagging issue.
Thanks.
EDIT 1:
I remember having turned off SMB through DriverPack online tool, while installing the drivers. Could that be the reason? If so, how can I reenable it without having to reinstall OS?
I had already tried this one, but did not help. I am strongly suspecting that disabling SMB has broken the file sharing, as given in this link: https://www.sevenforums.com/network-sharing/408117-after-disabling-smb-v1-file-print-sharing-refuses-stay.html
– AllSolutions – 2017-06-24T21:23:36.487@AllSolutions, I have edited the post describing how to turn on SMB, try that. – El8dN8 – 2017-06-24T21:24:38.610
It seems the command you have given is for Windows 8 and Windows Server 2012, I am trying a different command for Windows 7 as given in this link: https://support.microsoft.com/en-ie/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server
– AllSolutions – 2017-06-24T21:29:38.457But instead of running the command through PowerShell, I already tried editing the Registry directly and also restarted the system. Still the problem persists. – AllSolutions – 2017-06-24T21:30:52.393