Windows 10: XP being able to discover W10 computers on my private network

I'm just lucky I guess.

 

So, NetBIOS over TCP/IP is enabled.
You can ping by netBIOS name (Like in PING XPCOMP, *NOT* \\XPCOMP or 10.0.0.x). Right?
You can map the other computer' shared folder using UNC (\\computername\sharedfolder). Right?
You cannot see other computers.
Nothing is really consistent with the issue you're having.

On the XP, run IPCONFIG /ALL
What do you see after
Primary Dns Suffix . . . . . . . : Could be empty
Node Type . . . . . . . . . . . . : must NOT be Peer-peer

Check that NetBIOS over TCP/IP is effectively enabled for the Ethernet adapter Local Area Connection
NetBIOS over Tcpip. . . . . . . . : Enabled

If everything looks OK, let's check for a master browser issue.
On the XP disable the computer browser service. Don't worry, stopping the computer browser service only prevents the machine from becoming a master browser. And you don't want your XP to become one anyway.
While you're at it, disable IPV6 for your adapter since XP was never very good with it.
Restart and wait a few minutes for the devices to register on the network.

Then test again....

 

XP machine name: SILVER
(It is a silver-gray laptop)
W10 machine name PUMBAA
(I used to watch a lot of Timon & Pumbaa)

Yes, NetBIOS over TCP/IP has been enabled, XP machine restarted, Enabled then verified again
From the XP machine I can type PING PUMBAA and have proper results
From the W10 machine I can type PING SILVER and have proper results
From the XP computer I can map the W10 computer C: drive (\\Pumbaa\C).
From the XP computer I can not browse past the name of the WorkGroup (Buffy).

Going to post everything from the ipconfig command on the XP machine:


Windows IP Configuration
Host Name . . . . . . . . . . . . : Silver
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.co.comcast.net

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hsd1.co.comcast.net
Description . . . . . . . . . . . : Broadcom 440x 10/100 Integrated Controller
Physical Address. . . . . . . . . : 00-15-C5-B6-39-D1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.140
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 75.75.75.75

75.75.76.76

Lease Obtained. . . . . . . . . . : Wednesday, April 19, 2017 8:09:10 AM
Lease Expires . . . . . . . . . . : Wednesday, April 26, 2017 8:09:10 AM

Ethernet adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 802.11 Multiband Network Adapter
Physical Address. . . . . . . . . : 00-16-CF-4D-6B-3A


XP Machine Master Browser Service disabled. (Notification came up stating Windows Firewall was blocking some of the features of the Microsoft Management Console and asked if I wanted them "unblocked", I unblocked them).
Not seeing any implementation of IPV6 in the Local Area Connection Properties, just good old "Internet Protocol (TCP/IP)"

Restarting...

uhg.

Maybe I'm confused, and if so, I am even more so now. In XP, in the left pane of File Explorer, I should be able to open My Network Places, then open Entire Network then click on Microsoft Windows Network and I see Buffy (the WorkGroup name) in the right pane, and when I click on that I should be able to see my networked computers in the workgroup Buffy, right???

When I click on Buffy, I get that statement as before telling me that Buffy is not accessible, but going along with your prior observation on inconsistencies, if I right click on My Network Places and select Search for Computers... then in the resultant search window type Pumbaa, that dang thing finds Pumbaa and tells me it is in the "folder" Buffy. Not only that, but I then can dbl click Pumbaa in the right hand pane, open it up and navigate to any directory i wish.

 

At least we are making progress *Smile
Could you post a screenshot of the DNS tab of the XP adapter Advanced TCP/IP Settings?

 

Hope this works...

 

Worked fine but doesn't bring any joy.

Are you using the same credentials (UserName + Password) on both machines?

 

For this to go away you need to go, on your XP machine, in network card properties. Then install, service, Service Advertising Protocol. With this i can see all XP computers in my workgroup, i.e. discovered service involved.

Trying to understand why XP can't see OS major than itself in that window. I mean, from XP i can ping, map, explore(everywhere but not there) etc. all my computers.

Have 4 computers:

1,2) Windows 10 CU. (They can do whatever they want).
3) XP SP3/Vista SP2 (XP can only see its "brother" in that window, but other features are ok.Vista can't see XP computers in network places, other features ok. Network map it works thanks to LLDP component in XP).
4) Windows XP SP3. (Same situation of #3).

Studying components differences among OS involded.

 

FYI, I never needed the Microsoft Service Advertising Protocol. The only time I installed a SAP was on Novell networks.
I'm still operating a network with 8 machines running Win10 (Enterprise, Pro and Home), Win7 (Ultimate and Pro), XP Pro, Win98 and even a (unnamed). The OP's issue is not unknown to me, but has always been resolved in the past.

@brucemc777: Meanwhile, you have an easy workaround. On the XP, map the Win10 drives (or folders) you need using FQDN (\\PUMBAA\...) if it's not already done.
When you'll be willing to run more tests, just tell me.

 

Indeed it's useless that window. He can map a drive, add a network resource or explore manually when he needs etc.

 

Much agreed. With a viable workaround I certainly do not wish to abuse you good folks! I'll just write off this puppy as solved.

Many thanks to all who tried to figure out what switch MS threw to mess up what once worked fine...