I have two Windows 8.1 desktop towers at home, and they each have their own wireless NIC to connect to my router. From there, they get internet access.
The two computers however, are physically right next to each other. Backups (and LAN games) between the two could use a wired network, if I could configure it properly. The goal is to get fast backups between the two computers, and fast gaming (LAN games over my wireless connection are VERY problematic), *and* to have each computer still have an internet connection if the other computer is turned off.
I am using a 2nd router (not the same one used to connect to the internet) to connect the two computers with cat5 cables. This 2nd router *can* have an internet connection via wireless bridge.
I want to somehow tell the windows 8.1 computers to pass all traffic destined for each other SOLELY over the wired network, and all traffic destined for the internet (or destined for the main router) over their *own* wireless NICs.
First approach:
Configure the 2nd router as a wireless bridge, and disable the wireless NICs on the two towers. I.e. the towers each only have one active NIC, and one IP address. Simple, effective... or so it seemed at first. The problem is the wireless bridge keeps going down after inactivity. In other words, it doesn't "just work". I'm willing to pay for a good wireless network bridge, but the negative reviews of the top models say things like "works for a day or two, but then the wireless connection drops out and it's difficult to reconnect". So I'm wary of paying for hardware to do it. So now I've focused on tricky network configuration solutions...
Second approach:
For LAN gaming, use the IP addresses associated with the wired NICs. Set the network metrics so that wireless NICs are preferred. Works for LAN gaming, but not for backup. My backup solution is CrashPlan, and network configuration-wise, it's a black box. It seems dead set on ignoring the wired routes between the computers. I also tried taking down the wireless NICs so crashplan would recognize the other computers via the wired connections, but was not successful in this endeavor.
Third approach:
Create network bridges (on both machines) that bridge the wired and wireless NICs, using only a single IP address on each machine.
Seemed to work at first, but turned out to be spotty, because each computer preferred to use the wired connection, and if they *both* prefer that, they will *both* turn off their own wireless network, and then neither of the machines has internet.
Fourth approach:
Create the network bridge on only one of the two computers. Backups from the computer with the single IP (using a network bridge) to the computer with two IPs (no bridge) worked using the wired network, but backups the other direction used wireless.
So, I've tried many different things and can't seem to come to a solution...
The two computers however, are physically right next to each other. Backups (and LAN games) between the two could use a wired network, if I could configure it properly. The goal is to get fast backups between the two computers, and fast gaming (LAN games over my wireless connection are VERY problematic), *and* to have each computer still have an internet connection if the other computer is turned off.
I am using a 2nd router (not the same one used to connect to the internet) to connect the two computers with cat5 cables. This 2nd router *can* have an internet connection via wireless bridge.
I want to somehow tell the windows 8.1 computers to pass all traffic destined for each other SOLELY over the wired network, and all traffic destined for the internet (or destined for the main router) over their *own* wireless NICs.
First approach:
Configure the 2nd router as a wireless bridge, and disable the wireless NICs on the two towers. I.e. the towers each only have one active NIC, and one IP address. Simple, effective... or so it seemed at first. The problem is the wireless bridge keeps going down after inactivity. In other words, it doesn't "just work". I'm willing to pay for a good wireless network bridge, but the negative reviews of the top models say things like "works for a day or two, but then the wireless connection drops out and it's difficult to reconnect". So I'm wary of paying for hardware to do it. So now I've focused on tricky network configuration solutions...
Second approach:
For LAN gaming, use the IP addresses associated with the wired NICs. Set the network metrics so that wireless NICs are preferred. Works for LAN gaming, but not for backup. My backup solution is CrashPlan, and network configuration-wise, it's a black box. It seems dead set on ignoring the wired routes between the computers. I also tried taking down the wireless NICs so crashplan would recognize the other computers via the wired connections, but was not successful in this endeavor.
Third approach:
Create network bridges (on both machines) that bridge the wired and wireless NICs, using only a single IP address on each machine.
Seemed to work at first, but turned out to be spotty, because each computer preferred to use the wired connection, and if they *both* prefer that, they will *both* turn off their own wireless network, and then neither of the machines has internet.
Fourth approach:
Create the network bridge on only one of the two computers. Backups from the computer with the single IP (using a network bridge) to the computer with two IPs (no bridge) worked using the wired network, but backups the other direction used wireless.
So, I've tried many different things and can't seem to come to a solution...
