Location:
State:
Carrier
Country
Status

Networking Win10pro and Win7pro


Both are members of the same Workgroup. Everything enabled but networking between the two is now a no go.

The thing seemed to work most of the time when I was running Win8.1 but since the upgrade it's a no go. Network discovery, etc all turned on - both machines. Password protection turned off - both machines. Sharing is set to Everyone, Administrator, Administrators - full control.

Have tried everything to no avail and believe the homegroup between Win10 and 7 is now apparently no go.

Any thoughts anyone as I've run out of ideas here.

An update - forgot to mention the Win10 machine can see the Win7 machine on the network but cannot access the files - 'Windows cannot access \xxxxxx. Error code 0x80070035 - The network path was not found

The Win7 machine cannot see the Win10 machine.

Hi there

I made a number of posts on this

First though can you say if the W10 machine is using a LOCAL or an MS account.

I notice that network connections aren't particularly stable -- they drop out after a while if you haven't used the machines for some time. Right mouse clicking in the network area (File explorer --network) and selecting refresh a few times seems to bring it back.

Cheers
jimbo

Thanks for responding. I use a MS account but in trying to sort I did revert to a Local Account - no go. So now back with the MS account.

When the laptop was running 8.1, no general problems although it did seem to drop off from time to time so definitely not 100% reliable. Also, the shared laser printer running from a USB cable worked fine via the Win7 machine.

Have just noticed that I can see my wife's laptop and shared files - she's using Win7 Pro. So the wi-fi element between my laptop and her laptop seems to be working okay but my main PC running Win7 via an ethernet cable to the router is a no go.

Edit: sorry forgot to add that my main PC running Win7 can also access the shared files on my wife's laptop. Certainly something weird here but probably very basic as well.

In order to use Homegroup, IPv6 needs to be enabled on both machines. Majority of the time, it is some third party Internet security software someone is using, that is the culprit.

IPv6 enabled on both machines. Have disabled Avast on the main Win7 PC.

Will swap the router and report back - maybe a setting I'm missing in that.

IPv6 enabled on both machines. Have disabled Avast on the main Win7 PC.

Will swap the router and report back - maybe a setting I'm missing in that.
Hi there

I'll almost bet you a million dollars to a bucket of Horse S--te that whatever the problem is it won't be the router.

For the Ms account to Local you need in the POPUP as username COMPUTERNAMEUsername then your password

The username is the user on your local machine. Computername is your local machine name.

For Local to Ms account you need the username you set the Ms account with ignoring the email bit - or if you switched from local to ms account see what the names are in the USERS folder on the C drive.

Ensure of course you have enabled sharing on the relevant W10 machine. I'd also delete any Windows credentials on the W10 machine and re-boot.

The drop out is quite annoying -- after a few Network refreshes in File explorer-->network it works --don't know why this problem is on W10 --it was fine on earlier releases.

I think also IPV6 is installed by default anyway.

You might if sharing with XP machines have to switch off 128 bit encryption in the network settings and drop back to 40 I think it is.

Cheers
jimbo

Spot on jimbo - changing the router, disabling firewall made no difference. Have just fired up an old Samsung laptop also upgraded to Win10 and it found the main Win7 PC first time and shared files. Also the main Win7 PC found the old Samsung laptop shared files. Have made sure that both laptops are identically configured but still no go with the Lenovo - the one that's giving me all the grief. The old Samsung is also able to read the shared files on the Lenovo and vice-versa.

So it must be the Lenovo that's giving all the problems.

In the Lenovo Device Manager there are 3 Other devices - drivers required. Two are marked as Unknown device and one is PCI Data Acquisition and Signal Processing Controller. Windows is unable to find the drivers for these so I guess it's off to Lenovo support as there were zero Other devices being shown when running Win8.1.

A further update - all Lenovo drivers updated from the Lenovo website to Win10. Still got a a couple of Unknown devices in Device Manager.

Hooked up an ethernet cable via the router and hey presto - everything worked as it should. So the conclusion is that it must be down to the Broadcom 802.11ac wi-fi Network Adapter in the Lenovo but totally out of my league as to what settings to change.

Networking Win10pro and Win7pro