September 24, 20178 yr https://pastebin.com/1ytm436r ifconfig, route -n, /boot/config/network.cfg Turned off server, moved it, turned it back on, and it can connect to the network fine, and i can access it from all computers on the network, but it can't access the internet at all. https://pastebin.com/nPJ3SyyT pinging a local pc, then 8.8.4.4 Nothing has changed at all apart from being turned off and moved. Probably a different network cable, but it would have been a network cable that worked before. Edited September 24, 20178 yr by carnifex
September 24, 20178 yr Author Oh, another thing i tried was changing DHCP to yes, and /etc/rc.d/rc.inet1 restart, but it just assigned me an ip way out of the range you'd expect (ie, not 192.168.1.*), and ping instantly failed with "connect: network not reachable"
September 24, 20178 yr Author omg disregard this my friend's phone connected to wifi before i plugged the server in, and stole the static ip.
September 24, 20178 yr Community Expert The DHCP server on most routers allows you to reserve an IP for a specific MAC address (e.g. the one for the unRAID server). Doing so stops it ever being allocated to a different client and thus stops such collisions from happening. Alternatively set the static IP for unRAID to be outride the range allocated by the DHCP server.
September 24, 20178 yr Generally, you can assign a DHCP range on the router, too. I've got mine set to 100-255 and reserve 0-99 for static IPs. Oh, and it's generally only after you've made a public fool of yourself that you realize the very simple mistake. It's happened to all of us... Edited September 24, 20178 yr by FreeMan
Archived
This topic is now archived and is closed to further replies.