Network devices getting an IP address in the 169.254.x.x range?
I'm totally confused by what's happening to my wifi router, so seeking help here.
Configuration
I have a modem/wifi router (Netgear CG3000D—let's call it main) connected to cable and configured with 255.255.255.0 mask. The LAN works fine, I'm getting 192.168.0.xxx IP addresses.
Connected to the router via CAT5 there is another wifi-router, used as a switch and broadcasting another wifi network—255.255.255.0 IP addresses are seen on its LAN ports as well as on the Wi-Fi connections.
On the wifi from the main router I also used to have 192.168.0.xxx IPs via DHCP and everything was working perfectly.
Problem
But all of a sudden at some point my main router decided to switch wifi connections to 255.255.0.0 mask. So now devices connected to this network get IPs of 169.254.x.x and cannot communicate to other devices on the network.
Question
I am totally puzzled by why this happened and also where exactly these settings are. Nothing on the main router seem to be setting this. And I don't think the second switch should be affecting this, but mentioned it to give a fuller picture.
Any ideas where to look at?
wireless-networking ip dhcp
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
add a comment |
I'm totally confused by what's happening to my wifi router, so seeking help here.
Configuration
I have a modem/wifi router (Netgear CG3000D—let's call it main) connected to cable and configured with 255.255.255.0 mask. The LAN works fine, I'm getting 192.168.0.xxx IP addresses.
Connected to the router via CAT5 there is another wifi-router, used as a switch and broadcasting another wifi network—255.255.255.0 IP addresses are seen on its LAN ports as well as on the Wi-Fi connections.
On the wifi from the main router I also used to have 192.168.0.xxx IPs via DHCP and everything was working perfectly.
Problem
But all of a sudden at some point my main router decided to switch wifi connections to 255.255.0.0 mask. So now devices connected to this network get IPs of 169.254.x.x and cannot communicate to other devices on the network.
Question
I am totally puzzled by why this happened and also where exactly these settings are. Nothing on the main router seem to be setting this. And I don't think the second switch should be affecting this, but mentioned it to give a fuller picture.
Any ideas where to look at?
wireless-networking ip dhcp
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
2
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48
add a comment |
I'm totally confused by what's happening to my wifi router, so seeking help here.
Configuration
I have a modem/wifi router (Netgear CG3000D—let's call it main) connected to cable and configured with 255.255.255.0 mask. The LAN works fine, I'm getting 192.168.0.xxx IP addresses.
Connected to the router via CAT5 there is another wifi-router, used as a switch and broadcasting another wifi network—255.255.255.0 IP addresses are seen on its LAN ports as well as on the Wi-Fi connections.
On the wifi from the main router I also used to have 192.168.0.xxx IPs via DHCP and everything was working perfectly.
Problem
But all of a sudden at some point my main router decided to switch wifi connections to 255.255.0.0 mask. So now devices connected to this network get IPs of 169.254.x.x and cannot communicate to other devices on the network.
Question
I am totally puzzled by why this happened and also where exactly these settings are. Nothing on the main router seem to be setting this. And I don't think the second switch should be affecting this, but mentioned it to give a fuller picture.
Any ideas where to look at?
wireless-networking ip dhcp
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
I'm totally confused by what's happening to my wifi router, so seeking help here.
Configuration
I have a modem/wifi router (Netgear CG3000D—let's call it main) connected to cable and configured with 255.255.255.0 mask. The LAN works fine, I'm getting 192.168.0.xxx IP addresses.
Connected to the router via CAT5 there is another wifi-router, used as a switch and broadcasting another wifi network—255.255.255.0 IP addresses are seen on its LAN ports as well as on the Wi-Fi connections.
On the wifi from the main router I also used to have 192.168.0.xxx IPs via DHCP and everything was working perfectly.
Problem
But all of a sudden at some point my main router decided to switch wifi connections to 255.255.0.0 mask. So now devices connected to this network get IPs of 169.254.x.x and cannot communicate to other devices on the network.
Question
I am totally puzzled by why this happened and also where exactly these settings are. Nothing on the main router seem to be setting this. And I don't think the second switch should be affecting this, but mentioned it to give a fuller picture.
Any ideas where to look at?
wireless-networking ip dhcp
wireless-networking ip dhcp
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
edited Aug 4 '16 at 3:23
Pimp Juice IT
24.7k113974
24.7k113974
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
asked Jul 30 '16 at 22:17
Dennis KDennis K
17816
17816
2
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48
add a comment |
2
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48
2
2
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48
add a comment |
1 Answer
1
active
oldest
votes
Give this a shot . . .
power off the machines getting the 169.254.x.x addresses and keep them powered off.
Now, unplug the power from your wireless router and wait two minutes with the electrical power disconnected and then plug it back
in and let it power up.
Wait five minutes and now start up the machine with the issue.
Check the IP assignment on the device connected to the router now and
see if things are back to normal.
The 169.254.x.x Address
Because the 169.254.x.x IP address was the dynamically assigned IP address to this machine, we knew DHCP was having an issue giving it an IP address, and I've seen this many times when routers start acting up like this — and not necessarily just with Windows either.
Automatic Private IP Addressing (APIPA) is a DHCP failover mechanism
for local Internet Protocol version 4 (IPv4) networks supported by
Microsoft Windows. With APIPA, DHCP clients can obtain IP addresses
when DHCP servers are non-functional. APIPA exists in all modern
versions of Windows including Windows 10.
When the DHCP process fails, Windows automatically allocates an IP
addresses from the private range 169.254.0.1 to 169.254.255.254. Using
ARP, clients verify the chosen APIPA address is unique on the network
before deciding to use it. Clients then continue checking back with
the DHCP server at a periodic interval (usually 5 minutes) and update
their addresses automatically when the DHCP server is again able to
service requests.
source
Reasons
Routers are just like any other device with an OS and circuitry components running on electricity; sometimes they get fragmented memory, etc. and just need to be power cycled to refresh everything for all feature and functions to work properly again when such behavior exists.
Power cycling routers seems to work best while all devices are disconnected from them (wired and wireless); hence, powering them off.
Further Considerations
You could also look for a firmware update for your router make and model if you continue to have such issues—there could be a bug, memory leak, etc. that's been patched via a newer version of firmware if you continue to have ongoing experiences like this (even if you go days without it but then...).
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1106931%2fnetwork-devices-getting-an-ip-address-in-the-169-254-x-x-range%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Give this a shot . . .
power off the machines getting the 169.254.x.x addresses and keep them powered off.
Now, unplug the power from your wireless router and wait two minutes with the electrical power disconnected and then plug it back
in and let it power up.
Wait five minutes and now start up the machine with the issue.
Check the IP assignment on the device connected to the router now and
see if things are back to normal.
The 169.254.x.x Address
Because the 169.254.x.x IP address was the dynamically assigned IP address to this machine, we knew DHCP was having an issue giving it an IP address, and I've seen this many times when routers start acting up like this — and not necessarily just with Windows either.
Automatic Private IP Addressing (APIPA) is a DHCP failover mechanism
for local Internet Protocol version 4 (IPv4) networks supported by
Microsoft Windows. With APIPA, DHCP clients can obtain IP addresses
when DHCP servers are non-functional. APIPA exists in all modern
versions of Windows including Windows 10.
When the DHCP process fails, Windows automatically allocates an IP
addresses from the private range 169.254.0.1 to 169.254.255.254. Using
ARP, clients verify the chosen APIPA address is unique on the network
before deciding to use it. Clients then continue checking back with
the DHCP server at a periodic interval (usually 5 minutes) and update
their addresses automatically when the DHCP server is again able to
service requests.
source
Reasons
Routers are just like any other device with an OS and circuitry components running on electricity; sometimes they get fragmented memory, etc. and just need to be power cycled to refresh everything for all feature and functions to work properly again when such behavior exists.
Power cycling routers seems to work best while all devices are disconnected from them (wired and wireless); hence, powering them off.
Further Considerations
You could also look for a firmware update for your router make and model if you continue to have such issues—there could be a bug, memory leak, etc. that's been patched via a newer version of firmware if you continue to have ongoing experiences like this (even if you go days without it but then...).
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
add a comment |
Give this a shot . . .
power off the machines getting the 169.254.x.x addresses and keep them powered off.
Now, unplug the power from your wireless router and wait two minutes with the electrical power disconnected and then plug it back
in and let it power up.
Wait five minutes and now start up the machine with the issue.
Check the IP assignment on the device connected to the router now and
see if things are back to normal.
The 169.254.x.x Address
Because the 169.254.x.x IP address was the dynamically assigned IP address to this machine, we knew DHCP was having an issue giving it an IP address, and I've seen this many times when routers start acting up like this — and not necessarily just with Windows either.
Automatic Private IP Addressing (APIPA) is a DHCP failover mechanism
for local Internet Protocol version 4 (IPv4) networks supported by
Microsoft Windows. With APIPA, DHCP clients can obtain IP addresses
when DHCP servers are non-functional. APIPA exists in all modern
versions of Windows including Windows 10.
When the DHCP process fails, Windows automatically allocates an IP
addresses from the private range 169.254.0.1 to 169.254.255.254. Using
ARP, clients verify the chosen APIPA address is unique on the network
before deciding to use it. Clients then continue checking back with
the DHCP server at a periodic interval (usually 5 minutes) and update
their addresses automatically when the DHCP server is again able to
service requests.
source
Reasons
Routers are just like any other device with an OS and circuitry components running on electricity; sometimes they get fragmented memory, etc. and just need to be power cycled to refresh everything for all feature and functions to work properly again when such behavior exists.
Power cycling routers seems to work best while all devices are disconnected from them (wired and wireless); hence, powering them off.
Further Considerations
You could also look for a firmware update for your router make and model if you continue to have such issues—there could be a bug, memory leak, etc. that's been patched via a newer version of firmware if you continue to have ongoing experiences like this (even if you go days without it but then...).
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
add a comment |
Give this a shot . . .
power off the machines getting the 169.254.x.x addresses and keep them powered off.
Now, unplug the power from your wireless router and wait two minutes with the electrical power disconnected and then plug it back
in and let it power up.
Wait five minutes and now start up the machine with the issue.
Check the IP assignment on the device connected to the router now and
see if things are back to normal.
The 169.254.x.x Address
Because the 169.254.x.x IP address was the dynamically assigned IP address to this machine, we knew DHCP was having an issue giving it an IP address, and I've seen this many times when routers start acting up like this — and not necessarily just with Windows either.
Automatic Private IP Addressing (APIPA) is a DHCP failover mechanism
for local Internet Protocol version 4 (IPv4) networks supported by
Microsoft Windows. With APIPA, DHCP clients can obtain IP addresses
when DHCP servers are non-functional. APIPA exists in all modern
versions of Windows including Windows 10.
When the DHCP process fails, Windows automatically allocates an IP
addresses from the private range 169.254.0.1 to 169.254.255.254. Using
ARP, clients verify the chosen APIPA address is unique on the network
before deciding to use it. Clients then continue checking back with
the DHCP server at a periodic interval (usually 5 minutes) and update
their addresses automatically when the DHCP server is again able to
service requests.
source
Reasons
Routers are just like any other device with an OS and circuitry components running on electricity; sometimes they get fragmented memory, etc. and just need to be power cycled to refresh everything for all feature and functions to work properly again when such behavior exists.
Power cycling routers seems to work best while all devices are disconnected from them (wired and wireless); hence, powering them off.
Further Considerations
You could also look for a firmware update for your router make and model if you continue to have such issues—there could be a bug, memory leak, etc. that's been patched via a newer version of firmware if you continue to have ongoing experiences like this (even if you go days without it but then...).
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
Give this a shot . . .
power off the machines getting the 169.254.x.x addresses and keep them powered off.
Now, unplug the power from your wireless router and wait two minutes with the electrical power disconnected and then plug it back
in and let it power up.
Wait five minutes and now start up the machine with the issue.
Check the IP assignment on the device connected to the router now and
see if things are back to normal.
The 169.254.x.x Address
Because the 169.254.x.x IP address was the dynamically assigned IP address to this machine, we knew DHCP was having an issue giving it an IP address, and I've seen this many times when routers start acting up like this — and not necessarily just with Windows either.
Automatic Private IP Addressing (APIPA) is a DHCP failover mechanism
for local Internet Protocol version 4 (IPv4) networks supported by
Microsoft Windows. With APIPA, DHCP clients can obtain IP addresses
when DHCP servers are non-functional. APIPA exists in all modern
versions of Windows including Windows 10.
When the DHCP process fails, Windows automatically allocates an IP
addresses from the private range 169.254.0.1 to 169.254.255.254. Using
ARP, clients verify the chosen APIPA address is unique on the network
before deciding to use it. Clients then continue checking back with
the DHCP server at a periodic interval (usually 5 minutes) and update
their addresses automatically when the DHCP server is again able to
service requests.
source
Reasons
Routers are just like any other device with an OS and circuitry components running on electricity; sometimes they get fragmented memory, etc. and just need to be power cycled to refresh everything for all feature and functions to work properly again when such behavior exists.
Power cycling routers seems to work best while all devices are disconnected from them (wired and wireless); hence, powering them off.
Further Considerations
You could also look for a firmware update for your router make and model if you continue to have such issues—there could be a bug, memory leak, etc. that's been patched via a newer version of firmware if you continue to have ongoing experiences like this (even if you go days without it but then...).
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
edited Jul 31 '16 at 3:14
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
answered Jul 30 '16 at 23:55
Pimp Juice ITPimp Juice IT
24.7k113974
24.7k113974
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1106931%2fnetwork-devices-getting-an-ip-address-in-the-169-254-x-x-range%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
169.254.x.x is a "link-local" address and is the address that a machine will give itself if it cannot reach a DHCP server.
– Mokubai♦
Jul 30 '16 at 22:24
@PIMP_JUICE_IT yes, this procedure worked! I can print again! Thank you. Please do add the answer and I'll mark it as accepted.
– Dennis K
Jul 30 '16 at 23:18
It isn't clear how exactly the addresses your being assigned are weird
– Ramhound
Jul 31 '16 at 0:13
@Ramhound I guess what was weird is that IP address of a machine changed for no reason. Another weirdness is that nowhere on the router is 255.255.0.0 mask is specified, so basically I can't fix the issue via router's GUI. And also, this happened to a multitude of devices (windows PCs, Android phones, wi-fi printer, Amazon FireTV. PIMP_JUICE_IT seem to have a pretty good explanation for this.
– Dennis K
Jul 31 '16 at 6:48