Setting static IP

[jdurham001]

   When we set the Buffalo's IP to static, do we also need to be sure that it's out of the range of the IP's being assigned by our DHCP server?

[JoshC]

No you have to have match the subnet.

 

Example:

If your IP address of your network is 192.168.11.1 then you would set your Nas to something like 192.168.11.7.

Message Edited by JoshC on 07-02-2009 09:43 PM

[jdurham001]

   What happens if my DHCP server tries to assign 192.168.11.7 to another host? Won't there be an IP conflict?

[JoshC]

Yes that was just an example:smileywink: make it something like that. You can try .10,.11,.12,.13.........

[PCPiranha]

Yes, you do want to make sure to assign it one outside of the DHCP pool or else you could end up getting an IP conflict.  This is something that you always want to take into account when assigning static IPs.

[daoswald]

   

Many routers with DHCP services allow you to specify either a list of, or a range of, or both a list and a range of IP's that won't be assigned by the DHCP server.  For example, my router's DHCP server is set to assign IP's within the range of 192.168.1.2 and 192.168.1.50.  However, I've excluded 192.168.1.3, making it unavailable to the DHCP server.

 

Another alternative would be to set the server to assign IP's from 192.168.1.10 through 192.168.1.60 (for example), and in so doing, automatically reserve 1.2 through 1.9 for static IP devices.

 

I do prefer using my Linkstation with a static IP.  It is just easier because I can map the network drives by IP address and forget about the NSNavigator software altogether.  Plus, I never have to look at NSNavigator or my router's tables to ascertain what IP the LinkStation is sitting on today; it's always 192.16.1.3 on my network.

[jdurham001]

   

I agree with the static IP preference. Somone had originally mapped our TeraStation with IP addresses, but not set the TeraStation to use a static IP. As such, the hosts that were mapped using the IP could not reconnect. However those that mapped the drive via hostname were able to connect thanks to NetBios.

 

I like the functionality provided my NetBios, but it took me awhile to figure out that our firewalls were configured to block it. Now that it works we haven't had any name resolution or connection problems.