Setting up a DHCP server with a unique approach requires guidance.
Setting up a DHCP server with a unique approach requires guidance.
So far I've been working on this and still can't figure it out. In my mind it sounds straightforward, but in practice it's really tricky. I have a server with a 10GbE network card (Asus PEB-10G/57840-2T) that has two ports. My goal is to link both my second server and my PC to this card so all three can share folders. I believe this is the main idea, though it might be a bit tricky to implement. My server is running Windows Server 2016, and I've tried setting up a DHCP server which gave IP addresses but only allowed communication from the server to others, not between them. I attempted to bridge the two ports on the card, but that broke the DHCP functionality. I installed Routing and Remote Services, but it didn't work at all. I also put Pfsense in a VM, but setting up DHCP for each connection failed and they couldn't talk to each other. I can't create a network that connects all three PCs either. I'm not sure what else to try, so I'm hoping someone can help or just let me know it's impossible. PS – don't suggest buying a switch; 10GbE switches are pricey at the moment.
In my understanding, the DHCP server isn't a router, which means it can't connect two machines together. But there could be an alternative solution. It might not be ideal, but it's possible. You could start a virtual machine, install Pfsense, and configure DHCP exchange so Pfsense acts as the Windows server. This would let you use a 10G connection. Another option is running Pfsense in a WAN with DHCP enabled, then treat the server as a central point for communication. If needed, a switch or router supporting 10G would be necessary. I don't guarantee this will work or that it's recommended.
I wanted to make sure everything works as intended. DHCP isn’t essential; I installed it just to check if it could handle what I needed. If there’s another method to achieve this without it, please let me know. Ultimately, my goal is for the three machines to connect and share their folders without relying on any internet connection or additional services.
Connect the interfaces so they share the same network. You can then set up static addresses or use a DHCP server. Avoid placing a default gateway on the DHCP leases to prevent internet loss. Without bridging, each interface behaves as if it's isolated in its own network. Ensure the IP range differs from your regular network.
Used DHCP but received no IP addresses on both devices. Attempted static configuration and found the two external systems can connect to the server, but not to each other. This setup isn’t working as expected.
It will be simpler to connect directly using the 10Gb links rather than relying on the internal 1Gb NICs. Setting up is straightforward, and I can handle routing or similar tasks. Using two NICs makes it more convenient, and you don’t need DHCP for the 10Gb ports—static configuration works fine.
hmmm k i feel like i should explain things a bit more clearer then. I do NOT want or need access to the internet or any other network with the 10Gbit NICs. I already have that setup through the onboard NICs in the systems. This is a separate network that i want between the 3 systems. So i guess i named the topic completely wrong. Should just be "creating a separate network, with a twist", in that case then. Also, if it wasn't clear already, i am by no means a networking expert. So a comment like "layer 8 issue", although funny, doesn't help cuz i already knew i was the problem, it's why i came here for help. So thx for letting me know i am the problem, but what is the solution? Because i am literally doing what both of you suggested and it's not working...
All three machines come equipped with identical dual-port 10Gb cards. If the other two only have single-port connections and you need high-speed connectivity between them beyond just linking to the main server, the setup becomes more complex. I’ll focus first on the computers with dual ports, as that’s the simplest configuration. Server 1 and Server 2 both have dual NICs, and each can connect directly to the other without relying on routing or static IPs. It’s crucial these links use different subnets to avoid conflicts, and they must stay separate from your primary 1Gb network. In a scenario where only single-port 10Gb ports exist in the other two machines, you’d need routing solutions—though the routing and remote access role you mentioned may help—but there’s additional configuration required to make it function properly.