Windows 10: Not Displaying Computer On Network

I just can't see it in Network Explorer from any other computers. It is invisible. But, I can view manually by typing \\[Computer Name].

 

You are looking at the network using CORE-I7-950. Right?

Which one is missing of:
\\CORE-I7-3930K
\\CORE-I7-950
\\SATELLITE-U840W

 

Yes. I can see it from the same computer, which means that I can see CORE-I7-950 from CORE-I7-950, but it cannot be seen from any other computer. But, all other computers can see all other computers except for CORE-I7-950.

 

You're not using the Homegroup. Right?

Are all 3 computers on the same workgroup (System Properties / Computer name tab)?

On each computer, open a command window and PING the other 2 using their NetBIOS name (no backslashes).

For example, on CORE-I7-950, you'll type:
PING CORE-I7-3930K and PING SATELLITE-U840W
and so on.

Tell me what's working or not.

 

PS C:\WINDOWS\system32> PING CORE-I7-3930K

Pinging Core-i7-3930K [fe80::b5f7:ad4:3be5:374%4] with 32 bytes of data:
Reply from fe80::b5f7:ad4:3be5:374%4: time<1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time<1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time<1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time=1ms

Ping statistics for fe80::b5f7:ad4:3be5:374%4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
PS C:\WINDOWS\system32>


PS C:\WINDOWS\system32> PING SATELLITE-U840W

Pinging Satellite-U840W [fe80::503a:63b3:726f:e375%4] with 32 bytes of data:
Reply from fe80::503a:63b3:726f:e375%4: time=1ms
Reply from fe80::503a:63b3:726f:e375%4: time=1ms
Reply from fe80::503a:63b3:726f:e375%4: time=5ms
Reply from fe80::503a:63b3:726f:e375%4: time=1ms

Ping statistics for fe80::503a:63b3:726f:e375%4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 5ms, Average = 2ms
PS C:\WINDOWS\system32>

-----------------------------

PS C:\WINDOWS\system32> Ping CORE-i7-950

Pinging Core-i7-950 [fe80::b57e:bbe9:bd9a:34c4%4] with 32 bytes of data:
Reply from fe80::b57e:bbe9:bd9a:34c4%4: time<1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%4: time=1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%4: time=1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%4: time=1ms

Ping statistics for fe80::b57e:bbe9:bd9a:34c4%4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
PS C:\WINDOWS\system32>


PS C:\WINDOWS\system32> Ping CORE-i7-3930k

Pinging Core-i7-3930K [fe80::b5f7:ad4:3be5:374%4] with 32 bytes of data:
Reply from fe80::b5f7:ad4:3be5:374%4: time<1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time=1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time=1ms
Reply from fe80::b5f7:ad4:3be5:374%4: time=1ms

Ping statistics for fe80::b5f7:ad4:3be5:374%4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
PS C:\WINDOWS\system32>

-----------------------------

PS C:\WINDOWS\system32> Ping Satellite-U840W

Pinging Satellite-U840W [fe80::503a:63b3:726f:e375%11] with 32 bytes of data:
Reply from fe80::503a:63b3:726f:e375%11: time=1ms
Reply from fe80::503a:63b3:726f:e375%11: time=1ms
Reply from fe80::503a:63b3:726f:e375%11: time=1ms
Reply from fe80::503a:63b3:726f:e375%11: time=1ms

Ping statistics for fe80::503a:63b3:726f:e375%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
PS C:\WINDOWS\system32>


PS C:\WINDOWS\system32> Ping CORE-i7-950

Pinging Core-i7-950 [fe80::b57e:bbe9:bd9a:34c4%11] with 32 bytes of data:
Reply from fe80::b57e:bbe9:bd9a:34c4%11: time<1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%11: time<1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%11: time<1ms
Reply from fe80::b57e:bbe9:bd9a:34c4%11: time<1ms

Ping statistics for fe80::b57e:bbe9:bd9a:34c4%11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\WINDOWS\system32>

 

Reading through this TechNet thread, it looks like it may be a Windows 10 Creator's Edition issue.

 

That's quite possible, since I see nothing wrong with your computer NetBIOS names. Service is running and each computer can ping each other using their names. Moreover, you can access your computers using FQDN.

Thanks again, M$ *Redcarded

Just for future use, can you tell us if all computers are on the same WorkGroup?

Although I'm personally not too fond of the feature, since IPV6 is running, you can always check if all computers can join the same HomeGroup. Start creating the group on CORE-I7-950.

 

Yeah, they are all on the same workgroup.

 

Thank you.

Did you try Homegroup?

 

No, I haven't tried Homegroup.
I have never felt the need for it.

I just create a share on all my computers.

 

Since you can access CORE-I7-950 using \\CORE-I7-950, you don't really need to see it under Network. You can create shortcuts (a.k.a. map network drives) to its shares (One shortcut per share).

Open This PC in Explorer
Computer / Map network drive button / Map network drive
Choose a drive letter and type \\CORE-I7-950\Full path to the share (like C:\Users\MyName\Documents).
Tick Reconnect at sign-in / Finish

You should see a new drive in Explorer under the letter you chose.

 

I found the problem on my offending computer. Below is how I fixed it. I hope this helps anyone else with the problem.
For some reason, my file sharing connections encryption setting was changed to "Enable file sharing for devices that use 40- or 56-bit encryption".


Go to the problem computer and do the following.

1. Open Network and Sharing Center
2. Click "Change advanced sharing settings"
3. Select "All Networks"
4. Under "File sharing connections", select "Use 128-bit encryption to help protect file sharing connections (recommended)"
5. Restart.

Your computer should now be visible again.
You may have to ensure that the same encryption setting is on all computers in your network.