It is simple as a flail design (I assume no ill will and combining [someone] at the hardware / driver level) I would check in turn:
1) ping after loopback in the console [cmd] you enter ping 127.0.0.1 and look if there are answers (4 should be)
If you don't get anything here - another error is in the windows themselves (in the TCP stack, most likely)
2) in the console [cmd] enter ipconfig / all and you look at your network interfaces and how they are addressed there should be at least one LAN type (Local Area Connection) with assigned IPv4 address to it
If you have no address (only with the physical address of the card only) - it means that DHCP gives the body (for some reasons - see below) and you need to check the router configuration first (maybe you have, for example, set a limit on the number of clients, although in standard configurations I have not seen it anywhere) Or are you not blocked any physical addresses of the cards? Or maybe you have turned on the option to block the assignment of IP addresses to cards not included in the list? . The second option - on an Ethernet cable - e.g. one-way communication - that is, physical damage to one of the veins. Check - by moving and connecting this cable to another - "up to date" computer. Another possibility is - errors during auto-negotiation of the connection mode (full duplex / halfduplex and speed) - then you have to experiment with setting them in the network adapter driver.
3) If you have the IP address of your network on the card (in the case of the screen it is class C with the address 192.168.xx and if everything is OK, now try in the [cmd] console to ping the router (default gateway address), e.g. ping 192.168.xx (where xx is the end of your computer's IPv4 address) (in your case it may be an address from the class 10.0.0.x but you will see it on the printout as pasted above - in the default gateway field) You should also get 4 correct answers (with some times