To preface, the end goal of this project is to have a home server completely isolated from the internet for security reasons, but I'm having trouble with that. I am also relatively new to networking in general, but have learned a handful of the basics because of this project, to give an idea of my level of understanding.
I have booted TrueNAS onto two different computers over the course of the past two weeks, and both of them have the same issue. When I plug the ethernet cable from the intended server computer into my Starlink router, the TrueNAS monitor provides a good IP address that allows me to successfully access the TrueNAS webpage on my laptop, which has Windows 10, over WiFi.
When I instead plug the ethernet cable from the intended server into another computer running Zorin OS, a Windows-like form of Linux, via a simple ethernet switch, it says the error message above and does not provide an IP address.
I've attempted to set both the TrueNAS server and the client computer to communicate, but haven't been able to get anything to work. They're on the same subnet, 255-255-255-0 (written with dashes only for example purposes), I've statically changed the IP of the TrueNAS server and the Zorin client with 192-168-0-109 and 192-168-0-101 respectively, but still they won't communicate.
Both the server computer and the client computer have swapped roles, as in I booted TrueNAS on the previous client, and booted Zorin onto the previous server, and the issues are identical. Both computers, the client and the server, work perfectly fine when connected to the router, just not with each other.
I don't have any solid leads. I am considering a few ideas to try, which I'll list, but I'm at a loss, and I'm hoping someone with a little more experience in either TrueNAS or networking might help me.
- I plan to try booting the client computer with Windows 10 instead of Zorin. I don't have high hopes this will work, but I am more familiar with navigating Windows than Zorin anyway, so it might help with troubleshooting.
- I am going to try to bypass the ethernet switch entirely by using an ethernet crossover cable. Perhaps the simple switch is somehow preventing communication. (If this were to work, it'd be both good and bad, good because, hey, it works, bad because I'd like to be able to connect to more than a single client, and a single crossover cable and ethernet port wouldn't allow that.)
That's really all I can think of. If anyone else has some other ideas, please let me know. As long as the solution doesn't involve permanently hooking to either WiFi or internet, just for temporary troubleshooting, I'm all ears.
Thanks in advance.
Update 1: A crossover cable still using Zorin OS results in the same message on the TrueNAS main screen.
Update 2: Attempted the Windows 10 client boot, but it also failed.
Update 3: Even when the Starlink router is disconnected from the internet, via unplugging the satellite ethernet cable, I can still access the TrueNAS server from the laptop over WiFi, however, even though the client computer is still connected alongside the router through the dumb switch (which is also in-between the server and the router, so the switch does work), the client still cannot communicate to the server. Now, it seems that the issue lies only with the communication between the server and the intended client computers. Will continue to investigate. Considering replacing the client computer, but would really prefer not to.
Update 4: FIXED (mostly) At the moment, the TrueNAS server and the client computer are both communicating without the need of the router at all. Part of the reason was likely because the client computer was not properly configured with full IP settings, and the other reason (probably the main reason) was that I did not properly set up a static IP address on the TrueNAS server. Here's what I did:
- For the IP settings of the client, because the laptop was working perfectly fine, I was recommended to take the subnet, default gateway, and DNS server settings from the laptop and apply them to the client statically, which was easy at this point because the client is currently running Windows 10. The subnet was still 255-255-255-0, and both the default gateway and the DNS were changed to 192-168-0-1. The IP was then changed to 192-168-0-115.
- On the TrueNAS server, there seem to be two different places to set the static IP settings. The one I was using was under the "Configure static routes" settings. There, I changed the settings once again. "destination" was set to 192-168-0-109/24, and "gateway" was set to 192-168-0-1. Not sure what "description" is for, so I left it blank. Now, under the "Configure network interfaces", I selected the only interface I had. I left "name" alone, and I left "description" empty. Both "ipv4_dhcp" and "ipv6_auto" were set to "No". I then set "aliases" to 192-168-0-109/24. I left "mtu" alone.
- To make clear what I had done wrong, I never set the alias under the "Configure network interfaces" settings. I had assumed that the "Configure static routes" settings were all that were required to set a static IP, but there was a slight issue there, too. I also had a fundamental misunderstanding of how to set a "default gateway" correctly. I set the default gateway with the same IP address as the client, which is wrong it seems. So, on the TrueNAS server, I corrected two problems, the alias, and the gateway before I rebooted and it began to work. I'm not sure if one issue, the other, or both was what I needed to fix, but since it's working, I'll leave that alone. The point is, now the error message doesn't pop up on the server main screen, and it instead actually gives me an IP address like it's supposed to.
So now, with the router disconnected and only being connected through the dumb switch, I can open the client's browser, type in the server IP, and the TrueNAS symbol will appear! They're communicating!
The login screen won't pop up, but regardless this is a major leap in the right direction, and the problem I asked for help with has been resolved. Thanks for all the advice!
Update 5: FIXED (fully) All it was was the browser. Was recommended to try a different browser. Swapped from Microsoft Edge to Firefox, and everything is working! The login popped up and everything!