Windows 10: one lan machine can see a new win 10 workstation, another can't

A network has, inter alia, an old win 10 workstation and a win 7 workstation. They are set up to share files and folders via ethernet (one intermediates backups, the other serves media files, wifi would be too slow for either).

A third workstation running win7 died. It's been replaced with a win 10 workstation ...

- the old win 7 workstation can read & write files & folders on the new win 10 workstation, and vice versa.

- The older win 10 workstation is connected to the same network, can ping the new workstation, but access to files & folders on the new win 10 machine from the old win 10 machine fails with system error 53 in DOS, and with error 0x80070035 in File Explorer.

Please, how to fix this?

:)

 

Good LAN party games?

Most of my suggestions have already been listed.

However, I found Swat4 to actually be a pretty fun LAN game, especially at smaller LAN parties.

 

Windows 10 LAN Setup


I have a small business with a data server and 7 workstations. Till now I have avoided the upgrade as xp has worked so problem free but a recent decision to upgrade server meant I could not avoid it any longer.

We have purchased the new workstations and now looking at the network side of things but have hit a bit of a snag.

Looking online I see most of the windows 10 networking steps relate to windows 7 and the general suggestion from what I can see is to use homegroup. In xp we were using workgroup and things were very easily set up and maintained but it seems the win 10 is not so easy to set up or maybe I am just not up to speed.

Any suggestions on a small business win 10 network setup and links to walkthrough's would be highly appreciated.

Thanks in advance

 

win 10 laptops do not recognise linux lan wokstation by name

We have two Win 10 laptops on a lan (in a windows workgroup) with other windows PCs and laptops running win 7 and linux.
One win10 laptop is held at build 1607 to avoid the many intrusive, time-consuming problems caused by continuous Win 10 updates. The other allows updates, and is current.
Win 7 can connect to the Ubuntu 16.04 fine by name. Windows 10 laptops cannot connect to it by name, but can connect to it via IP address.
On the Win 10 laptops, the command NET VIEW lists neither Windows lan workstations for which there are mapped network drives, nor the Ubuntu 16.04 machine.
On Win 10 SMBv1.0 is enabled.
Is there a fix for these inadequacies, or is such functionality just gone from Win 10?