Cannot connect to network computer via WiFi

I have two computers: a desktop with no WiFi (Ethernet only) and a laptop (Ethernet and WiFi).

Using Ethernet on both computers I am able to see and share files both ways and all works perfectly. Using WiFi on the laptop I can connect with the desktop machine but not the other way around.

The diagnostics on the desktop computer report "One or more network protocols are missing on this computer. Windows Sockets registry entries required for network connectivity are missing." I've tried all the standard methods to resolve this issue but nothing works. In any case, surely if this were the problem I wouldn't be able to use the Ethernet connection and the laptop wouldn't see my desktop machine?

Disabling the Kaspersky antivirus/firewall makes no difference.

At wit's end! Can anybody help?

Here is another thread that deals with this, see if it helps you.
Solved Network Protocols - Windows 10 Forums

CADesertRat said:

Here is another thread that deals with this, see if it helps you.
Solved Network Protocols - Windows 10 Forums

Thank you for pointing me to this. However, the query on this thread relates to accessing the internet. Both my computers can get online with no problems. The laptop can do so using either Ethernet or WiFi. The problem is with my desktop computer, which can't access the laptop when the latter connects to the network via WiFi (there's no WiFi on my desktop computer). I guessed this was a permissions issue but became confused by Windows producing the error message about missing network protocols.

Do tell me if I'm misunderstanding networking. It has always seemed to be a black art, one I've never mastered!

Problem solved. Sorry to have troubled this forum. It was nothing to do with Windows 10. Kaspersky on the laptop was treating the WiFi network connection as a public network and was blocking it. What my experience does show is that the Windows report "One or more network protocols are missing on this computer" can be an erroneous error.

Glad you found the problem and re-posted so that it may help others.