I have a computer running Windows 7 that shares a Git repo on drive D. Let's call this PC "win7
". This repo is the origin of a project that we push to and pull from.
The network is a wireless network. One PC on this network is running on Windows 10. Let's call this PC "win10
". Win10
can ping every other PC on the network including win7
. Win7
can ping win10
. Win7
can access all shared files on win10
. Neither of the PCs have passwords.
Problem: Win10
cannot access any shared files on win7
, not from Explorer, nor from Git Bash or any other Git management system (E-Git on Eclipse or Visual Studio). So, win10
cannot pull/push. Every other PC on the network can access win7
shared files and push/pull to/from the shared Git origin.
What's wrong with Windows 10?
I have tried these:
Control Panel\All Control Panel Items\Network and Sharing Center\Advanced sharing settings\ File sharing is on, Discovery is on, Password protected sharing is off
Adapter Settings\Properties\QoS Packet Scheduler uninstalled and re-installed
- Adapter Settings\Properties\File and Printer Sharing uninstalled and re-installed
- Adapter Settings\Properties\EVERYTHING uninstalled and re-installed
gpedit.msc\Computer Config\Win Settings\Security Settings\Local Policies\Security Options:
Enabled These:
- Network access: Allow anonymous SID/name translation
- Network access: Let Everyone permissions apply to anonymous users
Disabled These:- Network access: Restrict anonymous access to Named Pipes and Shares
- Network access: Do not allow anonymous enumeration of SAM accounts
- Network access: Do not allow anonymous enumeration of SAM accounts and shares
netsh int ip reset
, and then restartednetsh winsock reset
, and then restarted- AdapterSettings\ Enabled NetBIOS over TCP/IP
- Tried changing to static IP
- The new windows 10 Control Panel\ Network Reset
- Firewall is turned off
All of these were tried to no avail.
Answer
AT LAAST!! After 4 month, and seeing the error for the second time, I found the solution here:
https://support.microsoft.com/en-us/help/4046019
Turns out, if you type the ip in "Run", and only in "Run", a very specific error shows up that contains this message: "your organization's security policies blocks access..."
Searching that lead me to this solution:
Open "Local Group Policy Editor" by searching in Start Menu or going to Run and running gpedit.msc
, then go to Computer Configuration\Administrative Templates\network\Lanman Workstation
and:
"Enable insecure guest logons"
And that solved the problem.
No comments:
Post a Comment