In LTT's Recent revisit to the Jellyfish Fryer:
They have the server connected to its client machines using a Direct-Attach configuration, with manual IP addressing.
I have a question Im hoping someone here, or maybe some LMG staff; Can help me with.
In my home Setup, i have a fairly built gaming tower, with minimal SSD storage, and a second box, somewhat of a home-lab focused system built with some older HEDT parts, and use it to expand the storage from my primary box with a few Mellanox Connect-x 3s and a direct-attach configuration. Both boxes are running windows 10 pro.
When i initially set up the direct attach link, I came across an issue where the PCs refused to talk to each other over the direct link.
I didn't find much info on doing this when i looked, and the only way i found to get them to talk to each other, was to set the adapters as "public" networks and disable the "public" firewall on both machines.
In the recent LTT video, Linus made no mention of any special firewall configuration on the client windows box to get both machines talking to each other, so i have to assume that one of the following is why:
1. They didn't have any issues because the client machine wasn't connected to a separate DHCP enabled network.
(windows seemed to only care about blocking traffic on a manually assigned network when also connected to a DHCP network on another NIC)
2. Windows firewall doesn't block a connection with a non-windows machine for some reason....
3. Updates to windows/windows firewall make this just "work" now.
4. they did need to do additional firewall configuration and just didn't mention it.
I am planning on migrating the home-lab box to a new tower i am currently putting together (which i have loaded with Windows 10 Pro for Workstations), and I want to maintain the direct attach configuration.
But hopefully this time do it without disabling any firewalls.
What other ways can I accomplish this?
Thanks.