PCs on LAN can ping each othr but can't share files

**Ranger** · 08-27-17, 10:15 AM

I have a LAN with 2 PCs and the situation is weird: PCs on same workgroup can see each other, but they can't see the shared files/folders- because these don't show up in Network (Windows Explorer).

One computer is the main one (Windows 10, set as Master Browser), the other one is XP.
Name of the workgroup is WORKGROUP.

- On W10, the samba v1, v2, v3 are enabled (see screenshot)
https://prnt.sc/gdju3s

- I can ping from any of the PCs the other one successfuly.

- The result of the command "net view" on w10 PC is:
"System error 53 has occurred. The network path was not found."

- The result of the command "nslookup hostname" on w10 PC is:
"Server: ap8857ee75cefe
Address: 192.168.11.1
*** ap8857ee75cefe can't find hostname: Non-existent domain"

- The result of the command "nbtstat -A 192.168.11.3" on w10 PC (where the IP is XP's) is:
NetBIOS Remote Machine Name Table
Name Type Status
---------------------------------------------------------
HOME-PC <00> UNIQUE Registered
HOME-PC <20> UNIQUE Registered
WORKGROUP <00> GROUP Registered
WORKGROUP <1E> GROUP Registered

Even when XP computer is not connected to LAN, the result of "net view" on w10 PC is the same: "System error 53 has occurred. The network path was not found."

Adapter's settings -> Properties -> IPv4 -> Properties -> Advanced -> WINS : NetBIOS Setting is set to "Enable NetBIOS over TCP/IP"

Just in case, I also flushed the DNS server.

Don't understand why this happens, I'd appreciate any help.

**Philip** · 08-28-17, 02:56 PM

System error 53 simply means your Windows 10 machine can't find the specified network path.

I would try the following:
1. Verify that NetBIOS is turned on on the XP machine
2. Turn off the Windows firewall temporarily on both machines to rule out that possible issue.
3. Make sure both machines are in the same workgroup (usually "workgroup", or "MS HOME")
4. In Control Panel > Network and Sharing Center > Advanced Sharing Settings > check "Enable file and print sharing for devices that use 40 or 56-bit encryption".
5. Does \\192.168.11.3 see the remote machine ? Does the reverse work, from the XP machine to Windows 10?

**Ranger** · 08-31-17, 09:10 AM

Thanks for coming up with many possible solutions.

What I did is I tried accessing with command //computername/sharedfolder and it worked. I can see the shared folders on the other computer from any of the PCs.
I posted a screenshot from the XP PC here:
https://prnt.sc/gfdnum
The XP's name is Goodguy-pc; the W10 PC's name is Home-pc

Now I have the following questions:
1. After accessing the location with the above command, the shared folder (music) showed under "Web Client Network".
But shouldn't it be displayed under Workgroup..?

2. Until I specifically accessed location //computername/sharedfolder , the shared folder on the other PC was not visible in Entire Network.
I think this behavior is not normal... why doesnn't it show there from the beginning...?

**Philip** · 08-31-17, 12:15 PM

There is some caching going on, and different versions of WINS/NetBIOS have their own quirks. That is typical mixed Windows network environment, I wouldn't worry about it much unless the machine disappears.

What is more worrysome is that it does not show under workgroup. The "Web Client Network" uses a different protocol: WebDAV (HTTP)..
On the other hand, all the machines under "Microsoft Windows Network" use the SMB/CIFS protocol.

**RenesisXI** · 10-16-17, 10:10 AM

I had my fair share (excuse the pun) of sharing issues in Windows, after all the trouble i went the DC++ route, made a local DC++ hub and shared the files.

No more stress, if both windows are the same XP-XP 10-10 then there is no sharing issue but old and new there is sometimes a problem.