Online computer not responding to pings
I was doing a bit of scanning on my network lately, knew all the hostnames to each computer connected. But whilst pinging one of them ping
returned Request timed out.
. This is strange as I know the computer is online and that the computer responds correctly to pinging on a different (enterprise) network. Is there something on the computer, my network, or my computer that is bugging with this? - That's just a sub-question, I don't expect this to be the main answer.
The real question: Why does this happen? Why does pinging the IP4 address not work?
EDIT :
Pinging the Hostname used to default to the IP4 address, but now it defaults to the IP6 address. Why does this happen? But now that it pings using IP6, how come it all of a sudden works?
> ping -6 THE_COMPUTER
Pinging THE_COMPUTER [lengthy IP6 address] with 32 bytes of data:
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Ping stats: Sent = 4, Recieved = 4, Lost = 0 (0% loss)
But when this is done using IP4 it doesn't work. So there are now two questions:
- How come IP6 works and not IP4?
- Why does IP4 not work?
windows-7 networking wireless-networking ping
add a comment |
I was doing a bit of scanning on my network lately, knew all the hostnames to each computer connected. But whilst pinging one of them ping
returned Request timed out.
. This is strange as I know the computer is online and that the computer responds correctly to pinging on a different (enterprise) network. Is there something on the computer, my network, or my computer that is bugging with this? - That's just a sub-question, I don't expect this to be the main answer.
The real question: Why does this happen? Why does pinging the IP4 address not work?
EDIT :
Pinging the Hostname used to default to the IP4 address, but now it defaults to the IP6 address. Why does this happen? But now that it pings using IP6, how come it all of a sudden works?
> ping -6 THE_COMPUTER
Pinging THE_COMPUTER [lengthy IP6 address] with 32 bytes of data:
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Ping stats: Sent = 4, Recieved = 4, Lost = 0 (0% loss)
But when this is done using IP4 it doesn't work. So there are now two questions:
- How come IP6 works and not IP4?
- Why does IP4 not work?
windows-7 networking wireless-networking ping
1
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Tryping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...
– TheBrenny
Jun 9 '14 at 9:22
2
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46
add a comment |
I was doing a bit of scanning on my network lately, knew all the hostnames to each computer connected. But whilst pinging one of them ping
returned Request timed out.
. This is strange as I know the computer is online and that the computer responds correctly to pinging on a different (enterprise) network. Is there something on the computer, my network, or my computer that is bugging with this? - That's just a sub-question, I don't expect this to be the main answer.
The real question: Why does this happen? Why does pinging the IP4 address not work?
EDIT :
Pinging the Hostname used to default to the IP4 address, but now it defaults to the IP6 address. Why does this happen? But now that it pings using IP6, how come it all of a sudden works?
> ping -6 THE_COMPUTER
Pinging THE_COMPUTER [lengthy IP6 address] with 32 bytes of data:
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Ping stats: Sent = 4, Recieved = 4, Lost = 0 (0% loss)
But when this is done using IP4 it doesn't work. So there are now two questions:
- How come IP6 works and not IP4?
- Why does IP4 not work?
windows-7 networking wireless-networking ping
I was doing a bit of scanning on my network lately, knew all the hostnames to each computer connected. But whilst pinging one of them ping
returned Request timed out.
. This is strange as I know the computer is online and that the computer responds correctly to pinging on a different (enterprise) network. Is there something on the computer, my network, or my computer that is bugging with this? - That's just a sub-question, I don't expect this to be the main answer.
The real question: Why does this happen? Why does pinging the IP4 address not work?
EDIT :
Pinging the Hostname used to default to the IP4 address, but now it defaults to the IP6 address. Why does this happen? But now that it pings using IP6, how come it all of a sudden works?
> ping -6 THE_COMPUTER
Pinging THE_COMPUTER [lengthy IP6 address] with 32 bytes of data:
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Reply from [lengthy IP6 address]: time=1ms
Ping stats: Sent = 4, Recieved = 4, Lost = 0 (0% loss)
But when this is done using IP4 it doesn't work. So there are now two questions:
- How come IP6 works and not IP4?
- Why does IP4 not work?
windows-7 networking wireless-networking ping
windows-7 networking wireless-networking ping
edited Jun 9 '14 at 9:08
asked Jun 9 '14 at 9:01
TheBrenny
106116
106116
1
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Tryping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...
– TheBrenny
Jun 9 '14 at 9:22
2
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46
add a comment |
1
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Tryping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...
– TheBrenny
Jun 9 '14 at 9:22
2
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46
1
1
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Try
ping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Try
ping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...– TheBrenny
Jun 9 '14 at 9:22
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...– TheBrenny
Jun 9 '14 at 9:22
2
2
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46
add a comment |
1 Answer
1
active
oldest
votes
there are a few things I would recommend you try to see if you can fix this:
1)Disable windows firewall if you have not done so already. It is a fairly well documented "feature" of windows firewall that it randomly blocks packets even if an exception is made. Look on Technet and you will see what I am on about!
2)Disable IPv6 on your NIC. If you are not using it, it will only cause problems! Especially in situations where both PCs speak ipv6 and the router/switch between them doesn't.
4)Reinstall your network adapter drivers. Intermittent connectivity cal often be caused by faultering/failing driver installs. Even if it doesn't fix the problem, it definitely won't hurt!
I have often found that the main reson this happens is one of the above... hopefully this will help set you on your way.
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
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%2f766404%2fonline-computer-not-responding-to-pings%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
there are a few things I would recommend you try to see if you can fix this:
1)Disable windows firewall if you have not done so already. It is a fairly well documented "feature" of windows firewall that it randomly blocks packets even if an exception is made. Look on Technet and you will see what I am on about!
2)Disable IPv6 on your NIC. If you are not using it, it will only cause problems! Especially in situations where both PCs speak ipv6 and the router/switch between them doesn't.
4)Reinstall your network adapter drivers. Intermittent connectivity cal often be caused by faultering/failing driver installs. Even if it doesn't fix the problem, it definitely won't hurt!
I have often found that the main reson this happens is one of the above... hopefully this will help set you on your way.
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
add a comment |
there are a few things I would recommend you try to see if you can fix this:
1)Disable windows firewall if you have not done so already. It is a fairly well documented "feature" of windows firewall that it randomly blocks packets even if an exception is made. Look on Technet and you will see what I am on about!
2)Disable IPv6 on your NIC. If you are not using it, it will only cause problems! Especially in situations where both PCs speak ipv6 and the router/switch between them doesn't.
4)Reinstall your network adapter drivers. Intermittent connectivity cal often be caused by faultering/failing driver installs. Even if it doesn't fix the problem, it definitely won't hurt!
I have often found that the main reson this happens is one of the above... hopefully this will help set you on your way.
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
add a comment |
there are a few things I would recommend you try to see if you can fix this:
1)Disable windows firewall if you have not done so already. It is a fairly well documented "feature" of windows firewall that it randomly blocks packets even if an exception is made. Look on Technet and you will see what I am on about!
2)Disable IPv6 on your NIC. If you are not using it, it will only cause problems! Especially in situations where both PCs speak ipv6 and the router/switch between them doesn't.
4)Reinstall your network adapter drivers. Intermittent connectivity cal often be caused by faultering/failing driver installs. Even if it doesn't fix the problem, it definitely won't hurt!
I have often found that the main reson this happens is one of the above... hopefully this will help set you on your way.
there are a few things I would recommend you try to see if you can fix this:
1)Disable windows firewall if you have not done so already. It is a fairly well documented "feature" of windows firewall that it randomly blocks packets even if an exception is made. Look on Technet and you will see what I am on about!
2)Disable IPv6 on your NIC. If you are not using it, it will only cause problems! Especially in situations where both PCs speak ipv6 and the router/switch between them doesn't.
4)Reinstall your network adapter drivers. Intermittent connectivity cal often be caused by faultering/failing driver installs. Even if it doesn't fix the problem, it definitely won't hurt!
I have often found that the main reson this happens is one of the above... hopefully this will help set you on your way.
answered Jun 9 '14 at 9:55
Fazer87
10.2k12539
10.2k12539
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
add a comment |
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point2. There were a lot of broken implementations out in the field even a decade after IPv6 got introduced. But these days it should no longer be relevant.
– Hennes
Apr 27 '16 at 11:50
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
I am not sure about point 1 either. Do you have a reference link?
– grawity
May 14 '17 at 11:37
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f766404%2fonline-computer-not-responding-to-pings%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
1
Check your firewall settings as different networks have different firewall profiles. E.g. your home network is going to be more relaxed than your enterprise profile (probably pushed by Group Policy) - not sure why a ping would fail, however. Try
ping - 4 <the_remote_IP>
– Kinnectus
Jun 9 '14 at 9:18
ping -4 <IP_instead_of_hostname>
also fails. And now IP6 is starting to be on and off. It seems really strange...– TheBrenny
Jun 9 '14 at 9:22
2
Try disabling IPv6 from your network adapter and see if you get better results. We have an issue at my work place, with SOME devices on wireless, where IPv6 is the cause of connectivity issues but our network team are unsure of the fix. Most devices work perfectly, the odd few simply won't connect if IPv6 is enabled.
– Kinnectus
Jun 9 '14 at 9:31
Strangely, it works. But still only sometimes. I'm getting a better response rate ping IP6 over IP4. Is this just a strange anomaly that has no fix? Does it happen because of a law similar to Faraday's?
– TheBrenny
Jun 9 '14 at 9:39
It should work ALL the time. Maybe you have a power setting on either YOUR network adapter, or the remote computer, putting the device to sleep as no network activity? - Most likely the remote machine...
– Kinnectus
Jun 9 '14 at 9:46