There could be a number of reasons for your problems, and it's hard to say which. My advice when setting something like this up would be:
Don't bridge. That is principally for paralleled connections to the same LAN.
Use a cheap switch/hub instead of an X-over cable, which is not always reliable.
Buy an Ethernet wireless access point and connect this to a third hub socket. (or get a combined hub/AP) Configure it as a client of the WiFi network.
When wired, turn off the WiFi on the Win8 Computer. It will also get its Internet connenction via the hub/AP.
Share a folder on the serving computer, and if necessary create a user account to access it with, and assign share and filesystem permissions.
To avoid IP changes, either give the serving computer a static IP, or else give it a secured lease on the Internet router's DHCP.
Ensure that port 445 is open to LAN destinations on the serving computer's firewall.
On the client, create a batch file containing net use h: \192.168.1.23\sharename /user:username password
(where the ip is that of the serving computer) Run this batch file to connect to the share. Drive H: should then become the share on the client.
HTH.
Basically there are many ways to do these things, but experience shows that some work reliably, others less so. Often it's the old ways that work reliably ;)
Best Answer
I have seen the exact same problem. All the Linux computers on the subnet can ping each other, but the Windows 10 computer can only ping the gateway, not any of the hosts on the subnet.
i.e.
I have Windows 10 computer attached by Ethernet to a switch/router. The router is subnet
192.168.123.0/255.255.255.0and DHCP assigns the address192.168.123.241to the Windows 10 computer.The Windows 10 computer can ping and ARP from
192.168.123.1(the gateway of the router). But it cannot ping and ARP hosts on192.168.123.6and192.168.123.7.Hosts
192.168.123.6and192.168.123.7can see and ping each other, but they cannot ping192.168.123.241.All hosts have the same MAC address for ARP entry
192.168.123.1(the gateway).The Cause
I'd upgraded my router software, and in doing so the built-in Ethernet switch was no longer forwarding between ports. My other two hosts were on a different switch and could communicate with each other, and they could communicate with the router because the router's switch was delivering packets to the destination but not forwarding between Ethernet ports.
The solution was to reconfigure OpenWRT/LEDE to set all switch ports to the same VLAN so that traffic would be forwarded between ports.