Windows 10: Peer networking issue - invisible PC

There are 6 PCs on the network, a mix of W10 pro, W10 home, and W7 pro, and a mix of WiFi and cabled

One PC is set up as a "server" (file, print, RDP) and all the rest are user PCs

All but one of the clients is able to access the server, connecting to a shared printer and Remote Desktop on the default port 3389

Here's the problem pair: -

Server:
- Windows Defender firewall ON (with obvs the automatic holes opened when you set up file & print sharing & allow RDP)
- Windows 10 Pro 1809 (17763.503)
- SMB 1.0 / CIFS file sharing support ON (all 3 sub-options)
- Network discovery & automatic setup of connected devices ON
Client:
- Bitdefender firewall ON (but it makes no difference if I switch off ALL Bitdefender protection)
- Windows same version: 10 Pro 1809 (17763.503)
- Same SMB settings: SMB 1.0 / CIFS file sharing support ON (all 3 sub-options)
- Same Network discovery & automatic setup of connected devices ON
...in fact I can find *NO* differences in any settings, except as noted above for firewall - nothing that should make any difference, and nothing that shouldn't.

Both obtain IP by DHCP from the SOHO router, with the server's fixed (reserved) while all clients are random. There is nothing in the router's DHCP to differentiate between configs of static and dynamic allocations.

Yet 4 of the clients are able to access Remote Desktop and print to the server; the 5th one just won't connect: -
(a) RDP connection attempt: Connecting to: {servername} - Initiating remote connection... ...times out with "Remote Desktop can't connect to the remote computer for one of these reasons..." {etc etc}
(b) Attempting to add remote printer: (Select a shared printer by name) - I type in \\{servername}\{printername} and [Next]...Connecting to {printername} on {servername}...
... times out with "Windows couldn't connect to the printer. Check the name {etc etc etc}"
(c) Attempting to connect to server file share: (browsing the network sees other PCs, and itself, but not the server). Enter \\{servername}\ in address bar
...times out with "Windows cannot access \\{servername}\ - check the spelling {etc etc etc}"
(d) Attempting ping from server to client by NETBIOS name: Pinging {pcname}.local [IPV6 address]: destination host unreachable
(e) Attempting to ping from server to client by IP 4 address: destination host unreachable
(f) Attempting to ping from client to server by name: Pinging {servername}.local [IPv6 address]: Request timed out
(g) Attempting to ping from client to server by IPv4 address: request timed out
(h) (at night, only three live devices on the network): Using "fing" network discovery tool from server: detects only itself and the router
(i) (at night, only three live devices on the network): Using "fing" network discovery tool from client: detects itself, the router, and the server (by name).

It looks like something on the client is blocking any traffic from the server, but what? I may have tried some other stuff I have forgotten to mention - I've been at this for two days now with no change in results. But I've run out of ideas and would welcome any input.

Thanks
Chris

:)

 

Unable to access computers connected in Peer-to-peer connection, asking for network credentials to enter on Windows 10

Hi Roger,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

As you are unable to access the connected computer on Peer-to Peer connection, we will help you with this issue.

Step 1: Make sure that Password Protected Sharing is turned off
on your computer and check if it helps.

Steps to follow:

• 
  OpenControl Panel window
  
• 
  Select Network and Sharing Center
  
• 
  Select Advanced sharing settings
  
• 
  Under Password Protected Sharing, check mark
  Turn off Password Protected Sharing
  

Step 2: I suggest you to disable firewall and anti-virus installed on your computer and check if it helps.

Hope it helps. Reply to the post with an updated status of this issue, we will be happy to help you further.

 

Can not Create Homegroup and error 1068 - Windows could not start the Peer Networking Grouping on Local Computer and

Hi Ken,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

As per your concern is to create a HomeGroup, do let us know if you are facing the same issue with same error code?

If so, I suggest you to start the services for Peer Networking and check if it helps.

Three particular Windows services manage peer-to-peer networking, and all computers in you are trying to connect should have the same settings in order to reduce error messages and connection problems.

Step 1: Stop the services.

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol service, right click on it and click on
  Stop.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Restart the computer.

Step 2: Start the service and set it to automatic:

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol
  service, right click on it and click on
  Properties.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Start the service, set
  Startup type to Automatic.

Hope it helps. Reply to the post with an updated status of this issue for further assistance.

 

Peer to Peer Connection in home network.


Make sure to allow the golf program in Windows firewall settings.

Add or Remove Allowed Apps through Windows Firewall in Windows 10 | Tutorials

Also look at the help pages for the golf game and see which ports it needs opened. Is your network connection listed as Private? That probably needs to be checked as well: