Windows 10: Can't connect to laptop on network but laptop can connect to all other

Checked:-
All updates downloaded and applied on all machines.
Laptop File & Printer sharing is turned on.
Both HDs on the laptop are set up for sharing on the network with Everyone having all permissions.

Teamviewer 12 can access the laptop from my desktop with no problems and vice-versa!

Attempts to list the disks and files of the laptop from the desktop using Windows Explorer throw up a cannot connect error and the 'Diagnose' option fails to give any useful information.

Unfortunately, the only answers I've been able to find are way out of date - anyone with recent experience please?

Welcome to the forum. You say the drive is shared the whole drive? That is a disaster waiting to happen it ideal for an Ransomes are malware etc you only share folders needed. You set permission for everyone on the share but that's only part of it as then NTFS permission kicks in and if you don't have rights on NTFS you get nowhere

Samuria said:

Welcome to the forum. You say the drive is shared the whole drive? That is a disaster waiting to happen it ideal for an Ransomes are malware etc you only share folders needed. You set permission for everyone on the share but that's only part of it as then NTFS permission kicks in and if you don't have rights on NTFS you get nowhere

Thanks for your comments which, unfortunately, do not address the problem.

I have, BTW, been in the business since before IBM even coined the phrase "Personal Computer".

oldcelt said:

Thanks for your comments which, unfortunately, do not address the problem.

I have, BTW, been in the business since before IBM even coined the phrase "Personal Computer".

Me too........... punch cards come to mind........... ?

Your problem.............

I had an old 32bit P4 upgrade last night when I wasn't looking !

It's a test/ spare machine, seldom used, but part of my home network.... workgroup really....

It wasn't showing shares on my main machine.

Spent too much time trying to find a fix.... finally mounted the ISO for ver. 1603 and ran setup for an over the top install. The install went without a hitch and I had ver 1603 instead of the new ver 1707 but still no shares on my main machine showing..........

More pondering, and pounding, until I spotted an item on the menu on This PC page..........
"Add a Network location"
a box opens... give us the location
I typed in Win1064
box says we need share ??
I added Win1064 /users......
all shares on Win1064 popped up under Network....... Win1064

That's my story and I'm sticking to it !!

I had used that item on the menu before and wound up with a shortcut in brackets on the root, C: and not in Network folder where it belonged ????

Cuffy said:

Me too........... punch cards come to mind........... ?
Your problem.............
I had an old 32bit P4 upgrade last night when I wasn't looking !
It's a test/ spare machine, seldom used, but part of my home network.... workgroup really....
It wasn't showing shares on my main machine.
Spent too much time trying to find a fix.... finally mounted the ISO for ver. 1603 and ran setup for an over the top install. The install went without a hitch and I had ver 1603 instead of the new ver 1707 but still no shares on my main machine showing..........
More pondering, and pounding, until I spotted an item on the menu on This PC page..........
"Add a Network location"
a box opens... give us the location
I typed in Win1064
box says we need share ??
I added Win1064 /users......
all shares on Win1064 popped up under Network....... Win1064

That's my story and I'm sticking to it !!
I had used that item on the menu before and wound up with a shortcut in brackets on the root, C: and not in Network folder where it belonged ????

Thanks for your suggestion - I'll look into the possibility - strange things happen in W10 from time to time!

rinconmike said:

On CPU1, I went to the network adapter properties, unchecked the file and print sharing. Close it. and then went back in and rechecked it, and now I can access CPU1 shares from CPU2

That's worth a try - will report later. TVM.