I just put together a little Truenas build, and I’m wanting to connect it directly to my laptop via ethernet because I’m living in a situation where I can’t have permanent ethernet cables run to the router.
As it stands, the server is up and running and I can access the web GUI from my laptop when I plug the NAS into the router. When I connect the laptop and NAS directly, however, I cannot ping the NAS’ static IP, nor can I access the GUI.
As other forum responses suggested, I have set static IPs for both the laptop and the server. That info is as follows:
The static IP for the laptop is configured on the ‘wifi’ network connection in network and sharing centre.
They’re on the same subnet, which I gather is also important.
One final thing to mention is that when I connect the NAS to the laptop via ethernet, networking and sharing centre reflects that it detects something, telling me ‘unidentified network’ under the ethernet.
WiFi and Wired connections are two separate things with two separate IP addresses. You’ve probably set the WiFi address when you should have set the Wired address
If you’re wiring the laptop directly to the server then you need to turn your laptop WiFi off to stop any confusion then manually set the IP address of your laptop Wired connection whilst it’s plugged into the server.
Make sure the lights on the socket show it’s hooked up.
From your command prompt (DOS box) you should be able to ping some things;
Your laptop
I would just add you should pay attention to setup your static IPs so they land outside of your router DHCP range, you don’t want to end up with duplicate IP adresses on the network.
If you only connect your NAS to the laptop via cable and use WiFi for internet access you could configure it on a different private network.
For example:
Leave router with 192.168.0.1, and presumably 255.255.255.0 subnet
Leave laptop WiFi on DHCP so it works for Internet automatically and with any other router
Set NAS to another IP, for example 192.168.69.251 and 255.255.255.0 subnet
Set laptop Ethernet IP to 192.168.69.250 and 255.255.255.0 subnet
I’ve just picked a private range that is unlikely to be default on any router you connect to via WiFi.
IDK, that just sounds like over complicating things.
Just use a different network range for NAS and laptop Ethernet, leave WiFi alone? Sounds much less complicated than adding another router just for DHCP and reconfiguring multiple routers and devices, and potentially adding more unwanted cabling.