NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R9000 not respecting Static IP's for Devices
I have the R9000 and am using it with a server. The R9000 is working as my DHCP server since Microsoft royally screwed up windows and over the last year, DHCP just wont work on Windows Server. The pr...
antinode wrote:Firmware version? Connected to what?
When you say "Connected to what?", i'm confused, i was pretty clear on what was connecting to it. The internet port is connected with a Cat 5E cable going straight to the ethernet port on the wall, its fiber. Port 1 on the router goes to a switch that connects to a server and several computers. The server has multiple VM's on it, and several devices and VM's on the network need static IP address.
antinode wrote:Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address.To correct you:
Static IP's are IP address that do not changed. They are usually permanently assigned by the DHCP server (and configured there too) and handed out based on the connecting devices MAC address, as long as that mac address is assigned to a reserved IP address on the DHCP server.
Static IP addresses can be configured on both the client and the server, however, the server may not accept your request for the specified IP address if setup on the client only, in that case, the server would assign something different which then the client can deny (most OS's and devices deny it) and as you said, you'd get a self-assigned IP address (169.254.#.#).
Dynamic IP addresses are IP addresses that are handed out by DHCP servers (typically on a server or through routers), they are the most common type of IP address and they will change after your DHCP lease on that IP address expires. This router has a maximum of 24 hours on a lease and thats what i have it set to, so if i dont login on a device for over 24 hours, then the next time i login i'll have a different IP address. Or if i reboot the router because that for some reason seems to clear leases on devices that dont immediately reconnect... sometimes...
I need static IP addresses configured so that when I visit my webmail, connect to my NAS devices, configure my network printer, or others, port forwarding will route to the proper VM or device on my network. Without static IP address, the IP's could change and i'll have to do some updates that can be time consuming. If i'm not home, this can cause some significant problems if i'm unable to connect remotely (or am unaware of the issue).
I typically run my DHCP Server on Windows Server 2019, but something is wrong with my server and for the past year, my entire network suffers from random disconnects that force me to reboot the server each time, taking down all my devices, services, and internet for the entire network (its much more complicated than a typical home network). Microsoft has no clue what it is and as a final suggestion, they've told me to reinstall windows, which i cannot do.
I did resolve the issue myself using the method i mentioned above, it didnt work at first but after a few tries I did end up getting it to work. I blocked the IP addresses taken by the other devices in Security > Access Control, then I turned off the conflicting device, followed by allowing it again (since its off, it wont renew the IP lease). Once i tried reconnecting with my static IP configured, it worked. If i did not disable other devices trying to reconnect to that same IP address, then the server would assign an IP address itself (169.254.#.#). After connecting with the proper IP, i turned on those other devices again to let them connect. I did sometimes have some issues and even though nothing had the IP i wanted to assign, it still self-assigned an IP. So i tried again and after a few times it worked.
Ok, so now let me help you out antinode. Some of your comments are quite rude and condescending.
antinode wrote:Connected to what?
I understand that you were confused, but if you put the conversation into context, it should be quite easy to understand what i was talking about. I was pretty clear and used examples when i couldnt be.
antinode wrote:> I found an older thread [...]
Thanks for the helpful link.
What you should have said was "Could you please provide the link to that thread?" and i would have responded with it. Instead you decided to respond with a smartass comment as though i did something wrong that i should have corrected. I originally included the key elements of that entire thread so nobody had to go read through it. There's no other helpful information on that thread.
antinode wrote:> [...] I usually get shouted at when I suggest things like that, [...]
Perhaps the (invisible) details of your suggestions would explain any
such objections. For example, assigning static addresses which are
still in the DHCP address pool would justify a loud objection.This was the response by michaelkenward who actually provided a response with significant value over yours. The invisible details that you somehow missed were embeded in the context of the entire response. Reading comprehension is important. Those invisible details are simple, he's saying to configure the Static IP addresses on the devices themselves rather than on the router. This was actually a part of my solution so thank you Michael!
antinode wrote:> [...] it just works for me.
_Which_ "it"? Properly done, using static addresses should work for
anyone. I use them on many of my devices, especially older ones where
DHCP is not supported. But, as usual, there are right ways and wrong
ways to do things, and some people have trouble telling them apart.Again, thats michaelkenward's response, but seriously.... Context... Up your reading comprehension skills and you'll understand what he said. When he said "it" he's talking about his solution, his solutoin works for him when he does it.
At the very least, i thank you for at least typing that up. It wasnt useful in this particular situation, but i really believe you need to pay attention to context, and try to be a bit nicer. If you cant do that, you probably shouldnt respond to any thread. Your demeaner came off very negative, as though you were mocking me and acting superior to me, as if i was stupid and had no clue what im doing. Based on your response, i'm quite confident i have more knowledge on this subject than you do, but i cannot conclude that because i dont know you or your mental condition or capacity at the time you wrote that message so i will not judge any deeper.
Thank you for your responses!
> R9000 [...]
Firmware version? Connected to what?
> [...] not respecting Static IP's for Devices
Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address. Either one should fix the address of a
device, but some implications are different.
> [...] The problem is when i assign a Static IP (Advanced tab > Setup >
> LAN Setup), [...]
As explained above, Address Reservation applies to _dynamic_
addresses, not "Static IP [addresses]".
The most common reason for a device not getting the address which is
reserved for it in the (DHCP server in the) router is the presence of
another DHCP server on the LAN. Firmware defects in Netgear routers are
common enough, but problems like this are seldom caused by the router.
> [...] I think its not giving me those IP's because each one i look at
> is already taken by another device. [...]
If that's true, then it would certainly be foolish (and disruptive)
for any DHCP server to grant a particular address to some new device
when it's already in use by some other device. DHCP is _dynamic_, but
it's not _whimsical_. (I have never seen a WHCP server.)
> [...] it gives me IP's like 169.254.167.213, [...]
Addresses in that "169.254.*.*" addresses are self-assigned, normally
when no DHCP server response is received; _no_ DHCP server grants them,
but you might also get one if you specify a static address which
conflicts with an address which is currently in use.
> I found an older thread [...]
Thanks for the helpful link.
> [...] I cant find any way to actually cancel a lease and just remove
> it.
Restarting the client device should do it. Restarting all your
client devices and your router might be a good idea after you change any
existing address reservations, too. ("Dynamic", not "whimsical".)
> [...] I usually get shouted at when I suggest things like that, [...]
Perhaps the (invisible) details of your suggestions would explain any
such objections. For example, assigning static addresses which are
still in the DHCP address pool would justify a loud objection.
> [...] it just works for me.
_Which_ "it"? Properly done, using static addresses should work for
anyone. I use them on many of my devices, especially older ones where
DHCP is not supported. But, as usual, there are right ways and wrong
ways to do things, and some people have trouble telling them apart.
antinode wrote:Firmware version? Connected to what?
When you say "Connected to what?", i'm confused, i was pretty clear on what was connecting to it. The internet port is connected with a Cat 5E cable going straight to the ethernet port on the wall, its fiber. Port 1 on the router goes to a switch that connects to a server and several computers. The server has multiple VM's on it, and several devices and VM's on the network need static IP address.
antinode wrote:Terminology: A "static" address is configured on the device itself.
What you configure on a (DHCP server on a) router is a reserved dynamic
address, not a static address.
To correct you:
Static IP's are IP address that do not changed. They are usually permanently assigned by the DHCP server (and configured there too) and handed out based on the connecting devices MAC address, as long as that mac address is assigned to a reserved IP address on the DHCP server.
Static IP addresses can be configured on both the client and the server, however, the server may not accept your request for the specified IP address if setup on the client only, in that case, the server would assign something different which then the client can deny (most OS's and devices deny it) and as you said, you'd get a self-assigned IP address (169.254.#.#).
Dynamic IP addresses are IP addresses that are handed out by DHCP servers (typically on a server or through routers), they are the most common type of IP address and they will change after your DHCP lease on that IP address expires. This router has a maximum of 24 hours on a lease and thats what i have it set to, so if i dont login on a device for over 24 hours, then the next time i login i'll have a different IP address. Or if i reboot the router because that for some reason seems to clear leases on devices that dont immediately reconnect... sometimes...
I need static IP addresses configured so that when I visit my webmail, connect to my NAS devices, configure my network printer, or others, port forwarding will route to the proper VM or device on my network. Without static IP address, the IP's could change and i'll have to do some updates that can be time consuming. If i'm not home, this can cause some significant problems if i'm unable to connect remotely (or am unaware of the issue).
I typically run my DHCP Server on Windows Server 2019, but something is wrong with my server and for the past year, my entire network suffers from random disconnects that force me to reboot the server each time, taking down all my devices, services, and internet for the entire network (its much more complicated than a typical home network). Microsoft has no clue what it is and as a final suggestion, they've told me to reinstall windows, which i cannot do.
I did resolve the issue myself using the method i mentioned above, it didnt work at first but after a few tries I did end up getting it to work. I blocked the IP addresses taken by the other devices in Security > Access Control, then I turned off the conflicting device, followed by allowing it again (since its off, it wont renew the IP lease). Once i tried reconnecting with my static IP configured, it worked. If i did not disable other devices trying to reconnect to that same IP address, then the server would assign an IP address itself (169.254.#.#). After connecting with the proper IP, i turned on those other devices again to let them connect. I did sometimes have some issues and even though nothing had the IP i wanted to assign, it still self-assigned an IP. So i tried again and after a few times it worked.
Ok, so now let me help you out antinode. Some of your comments are quite rude and condescending.
antinode wrote:Connected to what?
I understand that you were confused, but if you put the conversation into context, it should be quite easy to understand what i was talking about. I was pretty clear and used examples when i couldnt be.
antinode wrote:> I found an older thread [...]
Thanks for the helpful link.
What you should have said was "Could you please provide the link to that thread?" and i would have responded with it. Instead you decided to respond with a smartass comment as though i did something wrong that i should have corrected. I originally included the key elements of that entire thread so nobody had to go read through it. There's no other helpful information on that thread.
antinode wrote:> [...] I usually get shouted at when I suggest things like that, [...]
Perhaps the (invisible) details of your suggestions would explain any
such objections. For example, assigning static addresses which are
still in the DHCP address pool would justify a loud objection.
This was the response by michaelkenward who actually provided a response with significant value over yours. The invisible details that you somehow missed were embeded in the context of the entire response. Reading comprehension is important. Those invisible details are simple, he's saying to configure the Static IP addresses on the devices themselves rather than on the router. This was actually a part of my solution so thank you Michael!
antinode wrote:> [...] it just works for me.
_Which_ "it"? Properly done, using static addresses should work for
anyone. I use them on many of my devices, especially older ones where
DHCP is not supported. But, as usual, there are right ways and wrong
ways to do things, and some people have trouble telling them apart.
Again, thats michaelkenward's response, but seriously.... Context... Up your reading comprehension skills and you'll understand what he said. When he said "it" he's talking about his solution, his solutoin works for him when he does it.
At the very least, i thank you for at least typing that up. It wasnt useful in this particular situation, but i really believe you need to pay attention to context, and try to be a bit nicer. If you cant do that, you probably shouldnt respond to any thread. Your demeaner came off very negative, as though you were mocking me and acting superior to me, as if i was stupid and had no clue what im doing. Based on your response, i'm quite confident i have more knowledge on this subject than you do, but i cannot conclude that because i dont know you or your mental condition or capacity at the time you wrote that message so i will not judge any deeper.
Thank you for your responses!
> To correct you:
> Static IP's are IP address that do not changed. They are usually
> permanently assigned by the DHCP server [...]Thanks for the "correction", but if you want to use "static" to
describe what comes from a DHCP server ("D" for "Dynamic"), then we have
insufficient common ground for a productive discussion. If "static" and
"dynamic" are not disjoint concepts in this context, then we've passed
through the looking glass.Just because the word "Dynamic" is in the name, it doesnt mean it only assigns dynamic IP addresses. The word "Ham" is in the name "Hamburger" but that doesnt mean there's ham in it. That simply means that the protocol (of assigning IP addresses) is dynamic, which means that its continuous, automatic, its constantly working. It doesnt just assign one IP address and quit, it keeps going, it keeps working, thats what makes it Dynamic.
If you paid attention, you'll notice in my other post that i said Dynamic IP's are typically whats assigned by DHCP. Its the most common type of IP address that's out there, but it CAN do Static IP's too (IP's that dont change).
Definitions:
Static IP (source):
"A static Internet Protocol (IP) address (static IP address) is a permanent number assigned to a computer by an Internet service provider (ISP).
A static IP address is also known as a fixed IP address or dedicated IP address, and is the opposite of a dynamic IP address.
A computer with an assigned static IP address uses the same IP address when connecting to the Internet.
Static IP addresses are useful for gaming, website hosting or Voice over Internet Protocol (VoIP) services.
Speed and reliability are key advantages. Because a static address is constant, systems with static IP addresses are vulnerable to data mining and increased security risks."
Dynamic IP (source):
"A dynamic Internet Protocol address (dynamic IP address) is a temporary IP address that is assigned to a computing device or node when it’s connected to a network. A dynamic IP address is an automatically configured IP address assigned by a DHCP server to every new network node."
~
"Unlike static IP addresses, dynamic IP addresses are not permanent. A dynamic IP is assigned to a node until it’s connected to the network; therefore, the same node may have a different IP address every time it reconnects with the network."
Dont trust Techopedia? How about the FTC (source):
"Most devices’ IP addresses are dynamic, meaning they change over time. Dynamic IP addresses are assigned by an Internet Service Provider’s (ISP’s) server or a network’s router when devices connect to them, and they can sometimes even change at a moment’s notice.
Static IP addresses (also known as fixed or dedicated IP addresses), on the other hand, do not change. Once a device has been assigned a static IP address, that number typically remains with the device as its internet identifier until the device is decommissioned or the network architecture is modified. In most cases, devices that are given static IP addresses tend to be servers and other important equipment and the static IP address makes them easier to find and communicate with."
Got a problem with the FTC and dont trust them? How about AT&T (source):
Static IP:
"A static IP address is an IP Address associated with your account that never changes and can be assigned to a specific device. Every time that you connect to the AT&T network the static IP address routes traffic to the computer or device that can be assigned an IP (such as a router or firewall)."
Their definition of dynamic isnt clear enough so i wont post that. So what about how its assigned? The simplest way to put it is this. If you have a static IP and your network has a DHCP server, that DHCP server needs to know that the IP you are using is a static IP that's reserved so that it does not assign another device that IP address. This is where you add that reservation to your DHCP server, and it will track when that device is on or off and everything else as it does with dynamic IP addresses.
With an ISP, you tend to have to configure your static IP address on the client, but they do have your reservation configured in their DHCP server. This is software at work. Without this configuration, you could change the last number of your IP and still connect, making it extremely insecure, thus one of the very necessary reasons you have to still configure that reservation with the DHCP server. With Windows Server, you only have to configure the DHCP server reservations. Once the device connects, it'll match up the MAC address with what you have in the reservations and if one matches, it will dynamically assign you a static IP. I've had a few routers in the past that worked this way too, but like i said, this is all software based so it can go either way, depending on the manufacturer. Regardless, if you dont have reservation information on your DHCP server for static IP's, then you dont really have a static IP. I dont know if this router still requires you to configure your static on the client machine, but I have mine configured on both ends and it works fine. Maybe one day i'll remove the static IP config from one of the client systems and leave it on the reservation list on the router and see if I can get it to give me a dynamic IP instead of my reserved IP. That would answer that.
Go do some research if you think i'm wrong. I've provided irrefutable evidence, you have no chance at being correct unless you change your position. I've been in this industry for probably longer than you've been alive, i'm not wrong.
pmad99 wrote:
antinode wrote:
Firmware version? Connected to what?
When you say "Connected to what?", i'm confused, i was pretty clear on what was connecting to it. The internet port is connected with a Cat 5E cable going straight to the ethernet port on the wall, its fiber. Port 1 on the router goes to a switch that connects to a server and several computers. The server has multiple VM's on it, and several devices and VM's on the network need static IP address.
It may have been "pretty clear" to you, but your earlier messages made no mention of that rat's nest of connected devices.
The "Connected to what?" question is there to cover 99%, possibly more, of the people who turn up here and say nothing useful about the front end of their networks.That's why it can come across as boiler plate questioning. (It usually is in my case because I get tired of typing the same question every time.)
One of the biggest sources of local addressing issue is when someone fails to mention that they have a modem/router sitting ion front of a router. That can mess around with fixes and static addresses along with just about anything that happens on a local networks.
Your first message told us nothing useful about your network topography, which is unlike anything I have seen described here before.
> [...] i'm not wrong.
Of course not. As I wrote:
> [...] if you want to use "static" to describe what comes from a DHCP
> server ("D" for "Dynamic"), then we have insufficient common ground for
> a productive discussion. [...]But, for the benefit of any other poor souls who might arive here
and get snowed by the blizzard of blather...> Just because the word "Dynamic" is in the name, it doesnt mean it only
> assigns dynamic IP addresses. [...]That's _exactly_ what it means. That's why it's not called a "Static
and Dynamic Host Configuration Protocol server". When static IP
parameters are used, there is no need for for any Host Configuration
Protocol, because there is no need for for any communication with any
kind of Host Configuration Protocol server.
> [...] The word "Ham" is in the name "Hamburger" but that doesnt mean
> there's ham in it.If you look closely, you might notice that I was not using two
different words, but the same word, "Dynamic". You seem to be getting
your technical facts from sources like the following (which seems to be
in the right genre):https://www.hachettebookgroup.com/titles/kim-zachman/theres-no-ham-in-hamburgers/9780762498086/
> That simply means [...]
No, that's not what it means. At least not to the rational among us.
https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
> [...] but it CAN do Static IP's too (IP's that dont change).
Not using a reasonable and useful definition of "static IP address".
Which was my original point.By the way:
https://en.wikipedia.org/wiki/Internet_Protocol
https://en.wikipedia.org/wiki/IP_address> A static IP address is also known as a fixed IP address or dedicated
> IP address, and is the opposite of a dynamic IP address.That's approximately true, and it's why static IP parameters do not
come from a DHCP server. "fixed" is also widely used to describe a
reserved dynamic address, where a device always gets the same address
(dynamically) from a DHCP server. Which part of "opposite" did you find
confusing?> Go do some research if you think i'm wrong. [...]
Read your own citations?> [...] I've provided irrefutable evidence, [...]
Of what? That you haven't read and understood your own citations?
> [...] you have no chance at being correct unless you change your
> position. [...]As I wrote, "insufficient common ground for a productive discussion."
> [...] I've been in this industry for probably longer than you've
> been alive, [...]Your time and probability estimates are not worth much, either.
https://www.logicallyfallacious.com/logicalfallacies/Appeal-to-AuthorityAn appeal to authority is even less effective when its author cites
himself as the authority (_and_ fails to make sense).
I'm a little amazed that anyone has trouble seeing the difference
between a device which could say, "I already know my IP parameters."
(static) and a device which _asks_, "What should I use as my IP
parameters?" (dynamic). It's not a subtle difference. The critical
difference is in the asking of the question; it's not in the
repeatability of the answer.If a device knows its IP parameters without asking anyone, then
they're static. If a device gets its IP parameters by negotiating with
a DHCP server, then they're dynamic. It's not complicated.You can choose to remain in the Dumpty school of thought, and claim
that there's some overlap between "dynamic" and "static" (or even that
one is a proper subset of the other). While being opposites. My mind
is not flexible enough to do it. Nor would I do it if I could, because
such goofy definitions are simply less useful than more consistent and
rational ones.
