>>>>If there is no firewall blocking access, and you have NetBIOS over TCP/IP enabled then the NET USE command listed above should work. Its advantage is it works in the event that NetBIOS network browsing is not working or not up-to-date.
>>>
>>>As I mentioned to Tracy, I did create a trusted zone in my Comodo in the range of the Linksys router IPs. But I have not rebooted the PC, yet. I will do it now.
>>>
>>>And Tracy confirmed that she also uses AVAST but it does not stop network from working.
>>
>>Can you try COMPLETELY DISABLING Comodo? That will tell us if it's what is blocking access.
>
>All of a sudden, I see all 3 computers on my network. It could be that the effect of Comodo Exit took a few moments. I will try to open Comodo and see if I lose the networking.

The ability to "see" other machines depends on Network Browsing. On a peer-to-peer network one of the machines is the Master Browser, which contains the list of resources available on the network. On a peer-to-peer network it can be hard to predict which one is the Master Browser. If it gets rebooted one of the others must become the Master Browser and it can take a little while for the list to get re-synced amongst all the machines. This sort of activity appears in your System Event Log as "Browser Election" events.

Likewise if you turn off a firewall it may take a little while for the new resources to be "visible" on all computers.

For test purposes, the most reliable way to try to connect to remote shares is via NET USE with an IP address e.g.

REM In the command below use the IP address of the W2K machine
NET USE Z: \\192.168.0.101\D

Note that in the above the /persistent switch is explicitly not used. This is because your machines are using DHCP, so the next time the W2K machine is booted it'll likely get a different IP address. That's why it's preferable to use the NetBIOS computer name - or set the W2K box to use a static IP instead.