Windows 10: Windows 10 networking woes once again...

For the past few days or so I've been trying to troubleshoot a problem with LAN connectivity between two PCs: my laptop (ThinkPad T450s) and my self-built desktop. Both computers are running Windows 10 Pro 64-bit, build 10586.

Initially my problem was the infamous "one or more network protocols ae missing ...", but I managed to overcome that problem and managed to get my laptop and desktop to communicate once again.

However, that didn't last long as I have just recently moved my desktop into another room, the previous location was temporary and there I had the desktop connected to my LAN via an 802.11ac wireless NIC. Now My desktop is connected through the wired gigabit NIC instead of wireless, and I've lost connectivity again. *Sad

Basically if I try to ping my desktop from my laptop, the hostname will resolve to te correct IP addres but I won't actually get a response. This is true even with the Windows Firewall service disabled on my desktop.

And yet if I do the reverse by pinging my laptop from my desktop, I actually do get a response. What gives?

:)

 

Lost Homegroup

A post Windows 10 Anniversary update woe:

After updating, Homegroup on Dell desktop cannot locate others on the home network but others can see Dell.

On Dell under Network, I see all others

Any ideas?

Maybe I should get rid of Homegroup and start again

 

Location Woes Again

I can confirm this...it has not been able to locate my phone for at least 3

weeks now. GPS is turned on, and I've made no changes to the phone.

Bob

 

Some more obvious stuff to check:
Make sure the network is set to "private network" on both machines. If either one is public, all kinds of interesting things can happen. Here's how you can tell what's going on: open the network and sharing center on each PC and see what's showing there:



If both are set to private, good! You might then think about setting up a homegroup and making sure both machines join in.
HTH,
--Ed--

 

I did check to see if the connection was private, and it already was for both computers. I also ensured all computers are within the same workgroup.

In the end I ended up reinstalling Windows (through "reset this PC"), after that I set up shares with the same appropriate permissions and it seems to be working again.