Windows 10: Network Share Inconsistency - Strange

I have a home workgroup with a cable modem, router, and two computers, call them A and B. A has a network share, which used to be visible on the network to computer B.

A few months ago that stopped working. I checked the network settings on both computers (tcp/ip protocols and other settings) are identical. Computer B can see computer A on the network, but when I click on it to view shares, or try to go directly to the share, I get "windows cannot access \\server\drive." Click Diagnose and get "the remote device or resource won't accept the connection."

What's really strange is, if I open windows explorer on computer A, it also can see itself on the network. But when I double click on computer A in Network, I get the same errors as above! Apparently, computer A cannot even see it's own shares.

I looked carefully and don't see any problems with the security settings.

Any advice on figuring this out would be appreciated!

:)

 

Network Discovery Error

After the latest update, Network Discovery is not consistent. Only two computers show in the work group for most of the Win 10 computers. However, one computer does show all six computers in the work group. They have identical network discovery and file
sharing turned on.

This inconsistent behavior prevents mapping network drives.

I've rebooted all affected computers.

No change.

 

N80 - keeps telling me my new 1GB Mini SD card is CORRUPT...;-(

This is very strange! The N80 seems pretty inconsistent. It works on two different revision of firmwares on my N80!

Have you try formatting it and see whether it will work?

 

Seldenm, (Not a Solution, yet)I have had the same strange things happening with my Network starting back around April 2017.
It has been very frustrating. I have 4 physical PCs on my network. I had then all connected with Workgroup folder shares. This is the same setup I have been using since I learned how to network 2 Windows computers many years ago. This has proved to be very stable until this year. Additionally I had it setup as a mixed OS network with Ubuntu/Linux Mint Virtual Machines with their own assigned network configurations. So basically Windows PCs could see each other and Linux PCs and Linux PCs could see each other and the Windows PCs. Everyone played nice. Then there was the Samba updates. Since Linux did it first, I lost connection to my windows shares from Linux. Next windows update and BINGO now Windows cant see Linux Samba shares or each other about 30% of the time. The Windows/LINUX shares have remained totally broken. The Windows to Windows shares work about 30% of the time and returning from either sleep or hibernation results in total share failure. And I too have the same issue that sometimes ...earlier in the day on the same boot, the networking was working but often at least 1 of the machines fails to see it's own shares as well as others., I have tried all types of refreshes and disabling and re-enabling the network adapters and physically unplugging the Network cable and even cycling the router. Nothing restores the workgroup shares unless I shutdown or reboot. These are all Windows 10 Pro with the latest updates. Note: my Router is a WRT-1900ac and my local FTP server connections to and from all PCs physical and Virtual work flawlessly with use of IP addresses. Strange things though, with NMAP I have been able to catalog my whole network just fine, consistently. All testing done with FIREWALLS OFF and as a side note, Windows HOMEGROUP dorked out about the same time. I will post here if I find a solution. I am surprised nobody has jumped on this besides me.

 

By accident, I discovered a work-around. On the computer that could not see it's own shares on the network, I enabled TCP/IPv6 and suddenly, the problem went away! Other computers on my network can now see the network shares on the first computer, and it can see its own shares.

I wonder by enabling the v6 protocol fixed the problem?*Smile

 

Homegroup needs ipv6 to work

 

v6 was disabled. Learned my lesson!

 

Now this is puzzling. The computer that could not see it's own shares was working after I turned on TCP/IPv6. It worked for a few days, and other computers on the network could see it and it's shares.

But that stopped working!

Now, I can see the computer on the network, plus the names of the shares. But if I try to connect to one of them, I get error code 0x80070035 - network path was not found.

Back to the drawing board. Any suggestions for troubleshooting would be appreciated!