Quick question about assigning the Thecus N2100 a hard-coded IP address vs. letting the N2100 grab one from the router?
I sometimes have to reset the router for lock ups..ect. The DHCP list gets blown away and IP's are reset. So I have to go in and modify the secure web and FTP ports all the time on the router...which is a PITA.
I am curious if I assign a hard coded IP to the Thecus, reboot it, evertything should be fine as the router will assign it that IP correct?
So in the event that I have to reboot my router, the IP for the Thecus should not change...so I should not have to change my router settings ?
If I understand you correctly you want to make an IP reservation on your router so that it will be assigned to your Thecus NAS device?
If that is the case, why not just enter an IP address in the NAS box itself?
The advantage you will get with the dhcp ip reservation is that you don't have to take care of the ip config on the nas box itself but configure it centrally. If you have a lot of device that us IP this would be an advantage.
Same concept but reversed. I want to go into my N2100 and set a static IP on it so that when I reboot my router the IP on it won't change (IT MESSES UP MY FTP AND SECURE LOGIN SETTINGS ON THE VIRTUAL SERVER SETTINGS).
So I wanted to know, or expand on what you wrote is the following, since I Don't know that much about how routers work:
If I put in a static IP in the Thecus and reboot it, WILL the router recognize the change and automatically see the N2100.
My reasons for wanting to do this is so I don't have to go in and reset all my settings for port forwarding...ect each time I have to reboot my router...which isn't very often but it is annoying none the less.
Most routers allow you to set a DHCP range and even those that don't usually have a default range they set that does not cover the whole subnet - so if e.g. your router is 192.168.1.1 mask 255.255.255.0 then you might have DHCP range set as 192.168.1.50 to 192.168.1.100 - that means the router will give out 51 addresses from 192.168.1.50 to first device asking for one up to 192.168.1.100 - that leaves the addresses 192.168.1.2 - 192.168.1.49 and 192.168.1.101 - 192.168.1.254 free to be used as "static" addresses - so you could e.g. give your Thecus address 192.168.1.2 and 192.168.1.3 both masked 255.255.255.0
I am using a similar setup to this and it works fine.
It is "traditional" to give you routers, servers etc addresses in the "low" range (small LAN last .xx = say .01 to .20)
Static addresses are best for routers, servers (like Thecus) etc so you always know what they will be - and then you can also add address into hosts file and lmhosts file (in c:\windows\system32\drivers\etc) so you can always get to them by a name. If you have a more sophisticated router you can let addresses for servers be assigned by DHSP and always let them get the same address by linking the MAC address of the server's CARD to the IP address you want it to get but most SOHO routers cannot do this (my Billion can though ... but I still go for static - means you can still access servers after reboot when the router is offline)
I have a PCI wireless AP at home, and its DHCP server lets you match a MAC address and an IP address in your DHCP range. So, you always get a same IP address when you connect to that router at home. This is a very convenient feature, because I will always know the IP address of my laptop, Xbox, N2100, even my Buffalo DMA at home, without setting up static IP address.
Excellent post N2100Owner...I am going to have to evaluate my situation and figure out what will work best for me...
In your given situation isn't about the same thing though? Please correct me if I am wrong but the MAC address never changes correct?
So if you map a MAC address to an IP address isn't it about the same thing as setting the IP for the device?
I guess now that I think about it, then for each device like your computer or or laptop you wouldn't have to modify the network settings and just allow the AP to determine that Device X has MAC xxx so it will be assigned the pre-determined IP, which would save you the hassle of having to set up each device seperately.
Instead of using the host file I would just register your N2100 host name with DNS. You can use one of the free domain services or get your own domain for a small cost, under $10. Then you can access your N2100 from anywhere with out editing the hosts file. You can use your router to only allow or deny services (ports) over the Internet.
smc - registering with DNS assumes you are exposing the N2100 to the internet. Of course if you have your own DNS server on the LAn that is not the case (but most N2100 will have small SOHO LANS with no servers other than their broadband router and the N2100 itself).
As for MAC mapping of DHCP vs static IP debate - both are useful and where I use DHCP on a small LAN I tend to use MAC address to IP mapping for things like notebooks and PCs so that (esp for notebook) you can take to another LAN without having to change the IP settings. But for things that have a totally non changing IP (Like N2100) I prefer static as this is assigned more quickly (no need for DHCP calls) and also is not reliant on the router - so if the router pops it's clogs the N2100 will still get correct IP address after a reboot.
I use DNS for both internal and external hosts. I currently use www.zoneedit.com/ for my internal addresses.
Although address from the following blocks are not addressable from the internet, they can be used with a DNS. Example my N2100 is assigned the ip address of 192.168.2.10 and is using zoneedit as it's dns so that I can get to it by using n2100.domain.com.