So I've had a few times where my Xbox is unable to find an IP address; I'm suspecting because the one it was using has been assigned to another device recently turned on. The information I found online suggested setting up a static address on the router's gateway on the DHCP settings. I can't find this on the gateway on my PC, but suspect the list of connected devices is what is meant. Unfortunately when you go in to edit on this list there isn't any option to set a permanent IP address. Am I missing something? Pretty sure I've checked everywhere.
Re: RAx 80 setting a static IP address for my Xbox
> [...] I've had a few times where my Xbox is unable to find an IP > address; I'm suspecting because the one it was using has been assigned > to another device recently turned on. [...]
Much of that makes little sense to me, but let's continue.
> [...] The information I found online [...]
Thanks for the helpful links.
> [...] suggested setting up a static address on the router's gateway on > the DHCP settings. [...]
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.
Visit http://netgear.com/support , put in your model number, and look for Documentation. Get the User Manual (at least). Read. Look for "Manage reserved LAN IP addresses".
Re: RAx 80 setting a static IP address for my Xbox
You have posted your message in the section of this community given over to Nighthawk WiFi Routers. (This is easily done, given Netgear's complicated community structure.)
Many questions apply to different types of device, so you might get a useful responses here, but you might get more help, and find earlier questions and answers specific to your hardware, in the appropriate section for your device. That's probably here:
Re: RAx 80 setting a static IP address for my Xbox
I posted in here because my router is a Nighthawk RAX80 so it seemed like the right place. It probably doesn't need moving as I don't have an Orbi device, but thank you for looking.
Re: RAx 80 setting a static IP address for my Xbox
Sorry, I probably should have posted a link; the website I was following was https://turbospeedwifi.com/how-to-set-up-a-static-ip-address-on-xbox-series-x-dhcp-reservation-metho... which apparently is a better way of doing things as it avoids the router attempting to use that ip address for another device later. From what I can see on the manual there doesn't appear to be a way to set up a static ip address for one item on this router; I was hoping someone here might have a work around or have understood the manual differently from me.
I can't think of a nice way to say this, but perhaps you should consider being a little less snarky on your replies, or if you can't be less snarky then perhaps refrain from answering.
Re: RAx 80 setting a static IP address for my Xbox
> [...] which apparently is a better way of doing things [...]
"better" that _what_?
> [...] From what I can see on the manual there doesn't appear to be a > way to set up a static ip address for one item on this router; [...]
First, see "Terminology:", above. "Static" and "Dynamic" are different. A DHCP ("D" for "Dynamic") server does not deal with static addresses.
Second, the non-psychics in your audience might have no real idea at _what_ in _which_ "the manual" you're looking.
> [...] Look for "Manage reserved LAN IP addresses".
Did you? What, exactly, is the problem?
> [...] I was hoping someone here might have a work around or have > understood the manual differently from me. [...]
So far as I know, there's nothing to "work around"; Address Reservation should work. Exactly how you "understood the manual" is a mystery. As for "a way to set up a [reserved] address for one item on this router", I don't know what else you could do. I see no way to do more than one at a time.
> [...] perhaps you should consider [...]
Perhaps, before posting them, you should read your posts from the point of view of someone who can't see what you're doing, and can't guess what you're thinking. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
The reason for using the right place is that these things can be hardware dependent. From what I read here, AX stuff seem to have quirks that are beyond the usual Nighthawk kit. (I guess that's why Netgear has this baffling array of sections.) It also has its own cabal of experts who probably try to avoid the mainstream stuff.
With luck you will now get the help you need. If you haven't tried it already, a search of this section might prove profitable.
