Win10 connections on local network - only partial visibility

I'm starting a new thread for this, because it is a somewhat different issue than my previous thread.

We have two machines; my machine is Win10 Pro, my wife's is Win10 Home.
I have followed the instructions in:
Share Files and Folders Over a Network in Windows 10

The only difference between the two, is that the SMP settings differ slightly since hers is Win10 Home.

So, after logout/login, on *her* machine, both of our machines are visible on the network, and all shared folders are accessible.

However, on *my* machine, only my machine is visible and accessible, her machine does not show up.
I *do* have network discovery enabled, on both machines.
Interestingly, I can type \\her_IP_address on the Explorer address bar, and then her machine pops up, and all shared folders are accessible - my machine just can't find her on the network search, for some reason.

Does anyone know what this means??
It's actually not a major issue, since presumably her IP address won't change very often.
But it *is* curious, and if I can fix it easily, I'm just as happy to do so...

Windows doesnt look for a pc it asks the master browser for a list your pc is likley the MB once a pc goes off line it can take 20+ mins to be discovered by MB but you can use the IP in the mean time it was designed for work were most pcs are on 24/7

Samuria said:

Windows doesnt look for a pc it asks the master browser for a list your pc is likley the MB once a pc goes off line it can take 20+ mins to be discovered by MB but you can use the IP in the mean time it was designed for work were most pcs are on 24/7

Well, even after 2 hours after reboot, her machine is not showing up on my network list, though I can still connect via the IP address. ITM, my machine remains visible to hers... I don't know what the difference is between the two machines, that she can see me but I cannot see her!!

The drawback to the IP address, is that when I close that copy of Explorer, the connection disappears... I *was* able to create a link to her IP address while the machine was connected, and that will suffice, but the visibility of her machine *is* a mystery...

ummm... one thing that I changed recently, is that I dropped Avira antivirus, which I'd been using for years, and she is still using... I switched to Kaspersky Security Cloud. Maybe it is blocking the search in some way?? Although if that was the case, I would think it would block the IP address as well...

You can connect and map a drive from a cmd prompt and save it as a .cmd file to run when you want to connect

net use s: \\192.168.1.24\sharename /user:HTG password

s is the drive letter you want to use
ip set to hers and share namae
htg is a username on her pc and the password on that pc

run it from a cmd prompt when it work enter txt in notepad and save as map.cmd then clcik that to connect.

You can run this tool and see if it sees the pc it will often kick it into life make sure netbios is running as that what is used to resolve the name
NetBScanner - NetBIOS scanner

Samuria said:

You can run this tool and see if it sees the pc it will often kick it into life make sure netbios is running as that what is used to resolve the name
NetBScanner - NetBIOS scanner

YES!! Another NirSoft tool!!! He is so cool...

and in fact, NetBScanner easily finds my wife's machine...
and it also says "Master Browser" == YES...
so how come Windows network scanner does not find it??

MisterEd said:

As a fallback I keep a folder on my desktop called "My Network" with network shortcuts to each computer.
If a computer doesn't show up in the network I use the link in that folder to access it.
I realize that doesn't solve my or anybody else's problem but it easier than driving myself crazy over this.

So are you saying that you are also experiencing this issue?? That Windows 10 is not wanting to connect to other Windows 10 machines on a local network??

Yes, I also have created a link on my desktop, which will connect me to milady's machine... that works fine...
but it's just strange... why would Microsoft be discouraging people from connecting their machines on a local network?? This seems like normal behavior to me...

The two siblings, Windows 10 Pro and Windows 10 Home, quite often do not play very well together and often argue. They have been known not to talk to each other on many occasions.

idgat said:

The two siblings, Windows 10 Pro and Windows 10 Home, quite often do not play very well together and often argue. They have been known not to talk to each other on many occasions.

Wow... good thing they forced me off of Windows 7 ... which *just worked* ...
I can see why they wouldn't want that condition to persist...