Windows 10: Cannot access Win 10 shared drive from Win 7 PC - SOLVED.

I have been fighting with this problem for about a week, but finally fixed it and for what it is worth would like to share (no pun intended) with other members.

I have one Win 10 Laptop, one Win 7 Laptop and a Win 7 Desktop. My main machine is the Win 10 laptop which has two 500 GB drives installed. Drive 0 is for op sys, and drive 1 is for data files.

The Win 10 Laptop drive 1 was mapped from both the Win 7 Laptop and the Win 7 Desktop PC. I could access all of the folders and files on the mapped drive from the Win 7 Laptop but not from the Win 7 Desktop PC. I can see the Drive and open it but when I double click on my “User Name” folder I get an error message saying Z:\”User Name” is not accessible. Access is denied.

I can open all other folders and files and can create and delete folders and files on the mapped drive from both the Win 7 Desktop PC and the Win 7 Laptop.

I checked the “Share” status of the Win 10 Laptop Drive 1 and it shows “Shared.” I have also checked the permissions and the two users listed have Full Control, Change and Read checked.

On the Win 10 Laptop, I opened the Drive 1 folder, Right Clicked on my “User Name” folder and selected “Share With” which opened a window listing “Stop Sharing”, “Homegroup (view)”, “Homegroup (view & edit)” and “Specific Users.” Double clicking on “Homegroup (view & edit)” solved my share problem.*Biggrin

This share problem cropped up recently, cause unknown. I have never had reason in the past to get involved with “Homegroup” either. *Rolleyes

Peter B.

:)

 

Windows 10 Pro Domain computer cannot access network share from Windows 7 Pro

I have a couple of new workstations, freshly upgraded to Win 10 from factory Win 7. They have been configured for office use, MS Office and etc. They have been added to the domain. I have network mappings to (1) server running Server 2012,, no issues.
However, at satellite office there is a Win 7 Pro machine with shared drives. Non-Win 10 workstations can access and map with no issues. However, the Win 10 machines cannot. From Explorer, the Win 10 machines see the Shares, but when trying to Expand I
get "Windows cannot access \\blabla_server and the error code 0x80070035. I have disabled all Windows Firewalls, 3rd party Firewalls and AV, statically assigned IP's and about everything else on the web. From the Win 10 machine I can Ping and RDP to the
Win 7, just not map drives and access shares. From the Win 7 machine I can ping, RDP and even map drives to shares on the Win 10 machine,,, just not vice-versa!?!?! Both machines are current with Windows Updates. I have un-installed and re-installed NICs.
Can anyone help??

 

Windows 10 Cannot Reach Network Share

I have a situation where a Win 10 PRO PC cannot access file share on a Win 7 PC. Prior to upgrading to Win 10 PRO this PC was Win 8.1 and could access the share in question.

PC1: Win 7 Pro with shared drives A, C, not joined to a domain, homegroup OFF, WORKGROUP,

PC2 Win 7 Pro, joined to a work domain that is it not on, homegroup OFF,

PC3 Win 10 Pro, shared drive C, not joined to a domain, homegroup OFF, WORKGROUP. I did a clean upgrade from Win 8.1 to Win 10 - initially I could mount PC1 A as a drive, but now I get a disconnected error,

All PCs are connected by a simple Telco router. Please take careful note: PRO version of all OSs.

PC1 - can access the files on PC3

PC2 - can access the files on both PC1 and PC3

PC3 - cannot access the files on PC1 (P2 has no shared files/drives). I get the error - MS Windows Network: Logon failure: the use had not been granted the requested logon type at this computer.
I'm using the exact same credentials that I use on PC2 to gain access. One of the recent updates to Win 10 has created a logon problem. Prior to late December 2015 I could get see A,C on PC2 but there were intermittent problems.
Since the last week no access at all. MS has been pushing a lot of updates.

PC3 - If I go to This PC > Network I can still see the old mapped drive but everything is greyed out. It's like there is a cache or something that I can't get flushed.

Any ideas?