August 16, 201213 yr Hi all. I have just had to reconfigure my network and I can no longer see my unraid tower. I have assigned 192.168.0.10 - .200 as my network range. My subnet mask is 255.255.254.0. Unraid is set to Dynamic DNS (yes) (I found this by mounting my usb stick on my Mac and looking in the network config file). I have tried assigning a static IP on my Airport Extreme for the tower (192.168.0.100) but it is not working. Logging in to unraid with ifconfig give me the following: inet addr: 192.168.45.7 Bcast:192.168.45.255 Mask: 255.255.255.0 It appears my subnet is all messed up but I have no idea what to do. Help.....
August 16, 201213 yr Hi all. I have just had to reconfigure my network and I can no longer see my unraid tower. I have assigned 192.168.0.10 - .200 as my network range. My subnet mask is 255.255.254.0. Unusual mask, but nothing wrong with it. Unraid is set to Dynamic DNS (yes) (I found this by mounting my usb stick on my Mac and looking in the network config file). Are you sure about that? I don't recognise "Dynamic DNS" as being an unRAID option. I have tried assigning a static IP on my Airport Extreme for the tower (192.168.0.100) but it is not working. You don't give details and, in any case, I'm not familiar with the Airport Extreme, so I cannot comment on whether your 'tried' should have suceeded. Logging in to unraid with ifconfig give me the following: inet addr: 192.168.45.7 Bcast:192.168.45.255 Mask: 255.255.255.0 It appears my subnet is all messed up but I have no idea what to do. Help..... If that is the address which has been provided by your dhcp server (with the settings you quote above) something is very wrong. I would suggest that you try setting the address statically on the unRAID server itself.
August 17, 201213 yr He means dynamic host configuration protocol (dhcp). From one of your other pc's, can you ping the IP address that unraid is reporting (192.168.45.7)?
August 17, 201213 yr I have assigned 192.168.0.10 - .200 as my network range. My subnet mask is 255.255.254.0. inet addr: 192.168.45.7 Bcast:192.168.45.255 Mask: 255.255.255.0 As mentioned, you have to tackle this first. 192.168.0.0/23 (192.168.0.1-192.168.1.254) is not the range of 192.168.47.7/24 (192.168.47.1-192.168.47.254) that you just posted. Those two can not talk, unless you've setup routing (which I'm guessing you haven't based on the question). Something is configured drastically wrong, or you have two devices on your network giving out two different ranges of IP addresses assuming everything is set to DHCP. /boot/config/network.cfg USE_DHCP=yes IPADDR= NETMASK= GATEWAY=
August 18, 201213 yr Author I have set up my box as follows: /boot/config/network.cfg USE_DHCP=no IPADDR= 192.168.0.100 NETMASK= 254.255.254.0 GATEWAY=192.168.0.1 - my airport extreme base ip I now get an ip as above with ifconfig but tower no longer shows up in my finder and I can not connect to the server via my browser (although it did connect once only). When I try to connect to the server at smb://192.168.0.100 I'm told it can not be found. Everything was working great for months until my iso replaced my modem. @#$%%
August 18, 201213 yr Author MORE NEWS: It appears that my server is dropping the connection. I am able to connect about once every 50 or so log on attempts. It is time to start panicking?
August 18, 201213 yr I have set up my box as follows: /boot/config/network.cfg USE_DHCP=no IPADDR= 192.168.0.100 NETMASK= 254.255.254.0 GATEWAY=192.168.0.1 - my airport extreme base ip I now get an ip as above with ifconfig but tower no longer shows up in my finder and I can not connect to the server via my browser (although it did connect once only). When I try to connect to the server at smb://192.168.0.100 I'm told it can not be found. Everything was working great for months until my iso replaced my modem. @#$%% can you confirm the netmask? 254.255.254 or 255.255.254? also, what is the IP Address on the computer you are trying to connect with?
August 18, 201213 yr I would guess that your new modem is configured as a DHCP server, so it is handing out IP addresses as well as your router. You are going to have to turn one of the DHCP servers off. I fixed this on a friend's system when his ISP sent him a new modem that had DHCP turned on. It screwed his whole system up intermittently.
August 18, 201213 yr I agree with PTMurphy. I had the same issue when I upgraded speed on a Brighthouse/roadrunner system. The modem as they installed it had a built in router. The modems router was feeding my router (which I had to keep as it has VoIP built in). One simple phone call and the ISP support staff turned off the modems internal router and everything was well again. When it is all straightened out I suggest you set up your devices so the subnet mask on the network is 255.255.255.000. That is the standard used in most homes in the USA.
August 21, 201213 yr I agree with PTMurphy. I had the same issue when I upgraded speed on a Brighthouse/roadrunner system. The modem as they installed it had a built in router. The modems router was feeding my router (which I had to keep as it has VoIP built in). One simple phone call and the ISP support staff turned off the modems internal router and everything was well again. If you're calling into your ISP ask them to put your modem into bridge mode.
Archived
This topic is now archived and is closed to further replies.