Router issues IP but laptop does not accept?
I was having issues with my older Linksys wireless router and decided to upgrade to a Linksys E3000. However, after upgrading, I still have the same issues.
What happens is that I will be connected on my laptop (via wireless) and suddenly my connection will be dropped. Nothing I do seems to allow me to connect. My wife's laptop does the same thing. Wired connections have no issue, and if I give the laptops static IPs I have no issue.
I looked at the log in the web interface and get the following lines repeated when I try to connect:
Sun, 10 Oct 2010 16:18:08 received DISCOVER from 00:21:00:3B:D7:70
Sun, 10 Oct 2010 16:18:09 sending OFFER to 255.255.255.255 with 192.168.1.136
It looks like the router is trying to offer my laptop an IP, but the laptop does not take it. I verified that this is the MAC address of my laptop. I also do not understand why the IP that it is trying to assign is so high. My IP range is from 192.168.1.100 - 150 and I only have a a few devices connected.
I ran a capture using wireshark, but I don't really know what to look for.
wireless-networking dhcp
edited Jan 29 at 18:56
Hennes
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
add a comment |
I was having issues with my older Linksys wireless router and decided to upgrade to a Linksys E3000. However, after upgrading, I still have the same issues.
What happens is that I will be connected on my laptop (via wireless) and suddenly my connection will be dropped. Nothing I do seems to allow me to connect. My wife's laptop does the same thing. Wired connections have no issue, and if I give the laptops static IPs I have no issue.
I looked at the log in the web interface and get the following lines repeated when I try to connect:
Sun, 10 Oct 2010 16:18:08 received DISCOVER from 00:21:00:3B:D7:70
Sun, 10 Oct 2010 16:18:09 sending OFFER to 255.255.255.255 with 192.168.1.136
It looks like the router is trying to offer my laptop an IP, but the laptop does not take it. I verified that this is the MAC address of my laptop. I also do not understand why the IP that it is trying to assign is so high. My IP range is from 192.168.1.100 - 150 and I only have a a few devices connected.
I ran a capture using wireshark, but I don't really know what to look for.
wireless-networking dhcp
edited Jan 29 at 18:56
Hennes
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
add a comment |
I was having issues with my older Linksys wireless router and decided to upgrade to a Linksys E3000. However, after upgrading, I still have the same issues.
What happens is that I will be connected on my laptop (via wireless) and suddenly my connection will be dropped. Nothing I do seems to allow me to connect. My wife's laptop does the same thing. Wired connections have no issue, and if I give the laptops static IPs I have no issue.
I looked at the log in the web interface and get the following lines repeated when I try to connect:
Sun, 10 Oct 2010 16:18:08 received DISCOVER from 00:21:00:3B:D7:70
Sun, 10 Oct 2010 16:18:09 sending OFFER to 255.255.255.255 with 192.168.1.136
It looks like the router is trying to offer my laptop an IP, but the laptop does not take it. I verified that this is the MAC address of my laptop. I also do not understand why the IP that it is trying to assign is so high. My IP range is from 192.168.1.100 - 150 and I only have a a few devices connected.
I ran a capture using wireshark, but I don't really know what to look for.
wireless-networking dhcp
edited Jan 29 at 18:56
Hennes
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
I was having issues with my older Linksys wireless router and decided to upgrade to a Linksys E3000. However, after upgrading, I still have the same issues.
What happens is that I will be connected on my laptop (via wireless) and suddenly my connection will be dropped. Nothing I do seems to allow me to connect. My wife's laptop does the same thing. Wired connections have no issue, and if I give the laptops static IPs I have no issue.
I looked at the log in the web interface and get the following lines repeated when I try to connect:
Sun, 10 Oct 2010 16:18:08 received DISCOVER from 00:21:00:3B:D7:70
Sun, 10 Oct 2010 16:18:09 sending OFFER to 255.255.255.255 with 192.168.1.136
It looks like the router is trying to offer my laptop an IP, but the laptop does not take it. I verified that this is the MAC address of my laptop. I also do not understand why the IP that it is trying to assign is so high. My IP range is from 192.168.1.100 - 150 and I only have a a few devices connected.
I ran a capture using wireshark, but I don't really know what to look for.
wireless-networking dhcp
wireless-networking dhcp
edited Jan 29 at 18:56
Hennes
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
edited Jan 29 at 18:56
Hennes
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
edited Jan 29 at 18:56
Hennes
59.2k792142
edited Jan 29 at 18:56
Hennes
59.2k792142
edited Jan 29 at 18:56
Hennes
59.2k792142
59.2k792142
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
asked Oct 10 '10 at 15:25
JamesArmesJamesArmes
1111
1111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
We always use static IPs at home for the wireless. Consumer grade WAPs (and some business-class ones) just have really crappy DHCP. For whatever reason (I hate to say 'it should be easy!', but it really seems like it should). Whenever we get a new router, we figure we'll try its DHCP, and eventually we go back to static because it's just not worth the aggrivation.
At work, if there are too many devices out there to bother with static, the solution when it starts getting flaky is to just power cycle the WAP, and things connect ok for a few more days or weeks (or just buy a sturdier router). Part of me thinks they do it intentionally to upsell.
Since the number of IPs at home is typically less than 10, static IPs are just the path of least resistance in this case.
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
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%2f197916%2frouter-issues-ip-but-laptop-does-not-accept%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
We always use static IPs at home for the wireless. Consumer grade WAPs (and some business-class ones) just have really crappy DHCP. For whatever reason (I hate to say 'it should be easy!', but it really seems like it should). Whenever we get a new router, we figure we'll try its DHCP, and eventually we go back to static because it's just not worth the aggrivation.
At work, if there are too many devices out there to bother with static, the solution when it starts getting flaky is to just power cycle the WAP, and things connect ok for a few more days or weeks (or just buy a sturdier router). Part of me thinks they do it intentionally to upsell.
Since the number of IPs at home is typically less than 10, static IPs are just the path of least resistance in this case.
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
add a comment |
We always use static IPs at home for the wireless. Consumer grade WAPs (and some business-class ones) just have really crappy DHCP. For whatever reason (I hate to say 'it should be easy!', but it really seems like it should). Whenever we get a new router, we figure we'll try its DHCP, and eventually we go back to static because it's just not worth the aggrivation.
At work, if there are too many devices out there to bother with static, the solution when it starts getting flaky is to just power cycle the WAP, and things connect ok for a few more days or weeks (or just buy a sturdier router). Part of me thinks they do it intentionally to upsell.
Since the number of IPs at home is typically less than 10, static IPs are just the path of least resistance in this case.
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
add a comment |
We always use static IPs at home for the wireless. Consumer grade WAPs (and some business-class ones) just have really crappy DHCP. For whatever reason (I hate to say 'it should be easy!', but it really seems like it should). Whenever we get a new router, we figure we'll try its DHCP, and eventually we go back to static because it's just not worth the aggrivation.
At work, if there are too many devices out there to bother with static, the solution when it starts getting flaky is to just power cycle the WAP, and things connect ok for a few more days or weeks (or just buy a sturdier router). Part of me thinks they do it intentionally to upsell.
Since the number of IPs at home is typically less than 10, static IPs are just the path of least resistance in this case.
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
We always use static IPs at home for the wireless. Consumer grade WAPs (and some business-class ones) just have really crappy DHCP. For whatever reason (I hate to say 'it should be easy!', but it really seems like it should). Whenever we get a new router, we figure we'll try its DHCP, and eventually we go back to static because it's just not worth the aggrivation.
At work, if there are too many devices out there to bother with static, the solution when it starts getting flaky is to just power cycle the WAP, and things connect ok for a few more days or weeks (or just buy a sturdier router). Part of me thinks they do it intentionally to upsell.
Since the number of IPs at home is typically less than 10, static IPs are just the path of least resistance in this case.
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
answered Oct 11 '10 at 0:54
Kara MarfiaKara Marfia
1,8301221
1,8301221
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
add a comment |
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
I have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working fI have seen this before with other Linksys routers. Rebooting the router does the trick for my clients (22 users working from home).
– steve.lippert
Oct 11 '10 at 3:23
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
This is my first issue with any Linksys wireless router. And the old router worked fine until we moved. I thought it was interference at first because there is much more wireless activity where we moved to (devices in other houses and near by businesses). But the DHCP logs make me think that's not the issue. Static IPs is not a huge deal until somebody comes over and wants to use the wireless. Linux makes it easy to setup different IP settings for different wireless connections, Windows does not.
– JamesArmes
Oct 11 '10 at 13:02
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
Our DHCP seems to work find for the random friend connecting occasionally. It's reliable day-to-day use that never seems to pan out for me.
– Kara Marfia
Oct 12 '10 at 22:08
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%2f197916%2frouter-issues-ip-but-laptop-does-not-accept%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
