Set static IP, Xbox changes IP right back. Thus preventing me from connecting.

Keweico · Sep 9, 2014

What Country/State/Province do you live in? Germany

Modem brand & model number: Fritz Box 3170 ( Router included )

Wired or wireless: Both

Things you have tried: All ports are opened, dmz is active

Is UPnP Enabled? Yes/no/Unknown: Yes

Do you have a NAT error? If so, what is your NAT type? No

Any Error Codes you encounter: Can't acces from DHCP Server/ No IP Adress

Hello.

Last weekend my xbox started to make some trouble connecting to xbox live. I set a static IP and everything was fine, I had an open NAT and all.

Today I wanted to connect to live and it said "Connection to services not available".

I tried to set a static IP again ( my router's ip is 192.168.178.1 so I set my Xbox's IP to 192.168.178.30, just like I did last time ).

However, everytime I change it manually, it goes straight to the network overview and changes my Xbox's IP to 169.254.219.47....which makes no sense to me, since this has nothing to do with my network. I also set the xbox to automatic IP address, but every
freaking time it changes to this 169 address...

Anyone know of this issue?

Thanks !

:)

Jamesx82x · Sep 9, 2014

Problems Streaming My Xbox One to my W10 PC

The 1 time I tried that I set my Xbox up with a static IP and had no trouble. If your using whatever your router gives out it could change depending on the order each of your wireless devices connected. I know your entering whats listed in the Xbox but you should probably try a static ip fewer issues.

Pist0n Br0ke · Sep 9, 2014

Static IP address

I have set my xbox up with a static IP address eg 10.1.1.15 however every few weeks it changes IP address automatically and i need to reset it.

What could casue the static IP address to change?

Keweico · Sep 9, 2014

To add to this: When I connect through one of our wall socket wlan connectors by TP Link, it works fine. But since it is pretty far away it's not the best solution, I'd rather go through my router directly via LAN.

taidara · Sep 9, 2014

The 169.254.x.x range of an IP address is also known as a link-local address, or APIPA (Automatic Private IP Addressing). This address is a self assigned address that host machine uses when communication can't be resolved between a host machine and the DHCP
server.

If you haven't alrady, change the Ethernet cable you use between your console and the Fritz box.

I would also suggest that you disable Port Forwarding and DMZ (if these features are still active).

Make sure UPnP (Universal Plug and Play) is ticked enable.

Make sure to save your changes and reboot your gateway afterwards.

Go to Xbox Network settings and select Alternate MAC address and select Clear.

Reboot your console and let us know if your console can obtain IP configuration from the DHCP server and not the 169.254.x.x range of an address.

BobMcFly247 · Oct 31, 2018

Additional information:

DMZ is called "exposed host" in the Fritz Box.

BobMcFly247

Additional information:

DMZ is called "exposed host" in the Fritz Box.

Keweico

To add to this: When I connect through one of our wall socket wlan connectors by TP Link, it works fine. But since it is pretty far away it's not the best solution, I'd rather go through my router directly via LAN.

taidara

The 169.254.x.x range of an IP address is also known as a link-local address, or APIPA (Automatic Private IP Addressing). This address is a self assigned address that host machine uses when communication can't be resolved between a host machine and the DHCP
server.

If you haven't alrady, change the Ethernet cable you use between your console and the Fritz box.

I would also suggest that you disable Port Forwarding and DMZ (if these features are still active).

Make sure UPnP (Universal Plug and Play) is ticked enable.

Make sure to save your changes and reboot your gateway afterwards.

Go to Xbox Network settings and select Alternate MAC address and select Clear.

Reboot your console and let us know if your console can obtain IP configuration from the DHCP server and not the 169.254.x.x range of an address.

Wyldhorse1996

Still having problems when only 1 device is connected. I reset my router back to factory, and downloaded the newest firmware again, made my Xbox a static ip, forwarded the ports and got it to work a little longer than usual, but this time instead of being
kicked from the game, I was kicked from Xbox live and it didn't even recognize that I had a cable connected.

After an Xbox restart it saw the cable but wouldn't connect using my ip settings even though I hadn't changed anything.

I went back and changed the static ip I made to the ip assigned which I made static. And changed the port forward settings to the new static ip. After finally getting it to connect with these settings I'm back playing. I was initially disconnected from live
but it connected again and now I'm testing it out again.

Any idea why it had issues maintaining connection with my created ips? I may turn it off tonight and turn it back on tomorrow to find it won't connect once again.

kyle_m4496

Hi JordanPettitt. My name is Kyle and I'm an independent advisor.

This message can appear if another device on the network is using the IP address your Xbox is trying to use. Your hub may not support a public static IP (5G broadband doesn't in most cases), but it should support static IP addresses for local devices. If you can reserve a static IP address, then set the Xbox to that address, it should solve the issue. Usually, this is done in the hub settings, I suggest contacting Three for help with this.

> As when I then change the IP to auto I can see the IP address increasing eery second, it sort of flickers and changes. Is this an Xbox issue, or an issue with my ISP?

Sounds like there's a communication issue between your hub and the console. Setting up a static IP for your Xbox should prevent this from happening.

Please reach back if you have further questions.

Thanks,
Kyle

Set static IP, Xbox changes IP right back. Thus preventing me from connecting.