Why has one PC suddenly become unable to see one one particular website?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
0
The website is bitbucket.org. I only noticed when a push timeout out. The issue is only on one PC (Win10). Chrome, Firefox and Edge all have the issue. All other PCs' on the network, and an iPad, Android phones, have no issues with that or any other websites. Here's the ping and nslookup output from the offending machine:
ping bitbucket.org -n 1 -w 10000 -l 1
Pinging bitbucket.org [104.192.143.3] with 1 bytes of data:
^
--------------------------
Request timed out.
Ping statistics for 104.192.143.3:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:PROJECTSTOOLSRC>nslookup bitbucket.org
Server: fritz.box
Address: fd00::3a10:d5ff:fea7:80b2
Non-authoritative answer:
Name: bitbucket.org
Addresses: 2406:da00:ff00::6b17:d1f5
2406:da00:ff00::22c0:3470
2406:da00:ff00::22c5:2ef4
18.205.93.0
18.205.93.1
18.205.93.2
^
--------------------------
C:PROJECTSTOOLSRC>tracert bitbucket.org
Tracing route to bitbucket.org [104.192.143.3]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
2 4 ms 2 ms 2 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
3 * * * Request timed out.
4 130 ms 129 ms 128 ms TWO-DEGREES.ear1.LosAngeles6.Level3.net [4.26.2.82]
5 127 ms 129 ms 130 ms 7-1-10.ear1.LosAngeles6.Level3.net [4.26.2.81]
6 134 ms 134 ms 134 ms ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.146]
7 * * * Request timed out.
....
30 * * * Request timed out.
Trace complete.
and ipconfig output:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : fritz.box
IPv6 Address. . . . . . . . . . . : 2406:e007:6457:7101:94ea:ae4d:deb0:63c2
Temporary IPv6 Address. . . . . . : 2406:e007:6457:7101:e845:1ef6:a791:c69d
Link-local IPv6 Address . . . . . : fe80::94ea:ae4d:deb0:63c2%10
IPv4 Address. . . . . . . . . . . : 192.168.178.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::3a10:d5ff:fea7:80b2%10
192.168.178.1
Now, I imagine the fact that ping is talking to a different IP address to what nslookup returns is possible significant.
What should my next step be?
dns ping nslookup
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
|
show 2 more comments
0
The website is bitbucket.org. I only noticed when a push timeout out. The issue is only on one PC (Win10). Chrome, Firefox and Edge all have the issue. All other PCs' on the network, and an iPad, Android phones, have no issues with that or any other websites. Here's the ping and nslookup output from the offending machine:
ping bitbucket.org -n 1 -w 10000 -l 1
Pinging bitbucket.org [104.192.143.3] with 1 bytes of data:
^
--------------------------
Request timed out.
Ping statistics for 104.192.143.3:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:PROJECTSTOOLSRC>nslookup bitbucket.org
Server: fritz.box
Address: fd00::3a10:d5ff:fea7:80b2
Non-authoritative answer:
Name: bitbucket.org
Addresses: 2406:da00:ff00::6b17:d1f5
2406:da00:ff00::22c0:3470
2406:da00:ff00::22c5:2ef4
18.205.93.0
18.205.93.1
18.205.93.2
^
--------------------------
C:PROJECTSTOOLSRC>tracert bitbucket.org
Tracing route to bitbucket.org [104.192.143.3]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
2 4 ms 2 ms 2 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
3 * * * Request timed out.
4 130 ms 129 ms 128 ms TWO-DEGREES.ear1.LosAngeles6.Level3.net [4.26.2.82]
5 127 ms 129 ms 130 ms 7-1-10.ear1.LosAngeles6.Level3.net [4.26.2.81]
6 134 ms 134 ms 134 ms ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.146]
7 * * * Request timed out.
....
30 * * * Request timed out.
Trace complete.
and ipconfig output:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : fritz.box
IPv6 Address. . . . . . . . . . . : 2406:e007:6457:7101:94ea:ae4d:deb0:63c2
Temporary IPv6 Address. . . . . . : 2406:e007:6457:7101:e845:1ef6:a791:c69d
Link-local IPv6 Address . . . . . : fe80::94ea:ae4d:deb0:63c2%10
IPv4 Address. . . . . . . . . . . : 192.168.178.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::3a10:d5ff:fea7:80b2%10
192.168.178.1
Now, I imagine the fact that ping is talking to a different IP address to what nslookup returns is possible significant.
What should my next step be?
dns ping nslookup
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
1
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
tried the/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine givesPinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others:Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.
– rossmcm
Feb 4 at 21:03
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Neither had any effect.
– rossmcm
Feb 4 at 21:59
|
show 2 more comments
0
0
0
The website is bitbucket.org. I only noticed when a push timeout out. The issue is only on one PC (Win10). Chrome, Firefox and Edge all have the issue. All other PCs' on the network, and an iPad, Android phones, have no issues with that or any other websites. Here's the ping and nslookup output from the offending machine:
ping bitbucket.org -n 1 -w 10000 -l 1
Pinging bitbucket.org [104.192.143.3] with 1 bytes of data:
^
--------------------------
Request timed out.
Ping statistics for 104.192.143.3:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:PROJECTSTOOLSRC>nslookup bitbucket.org
Server: fritz.box
Address: fd00::3a10:d5ff:fea7:80b2
Non-authoritative answer:
Name: bitbucket.org
Addresses: 2406:da00:ff00::6b17:d1f5
2406:da00:ff00::22c0:3470
2406:da00:ff00::22c5:2ef4
18.205.93.0
18.205.93.1
18.205.93.2
^
--------------------------
C:PROJECTSTOOLSRC>tracert bitbucket.org
Tracing route to bitbucket.org [104.192.143.3]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
2 4 ms 2 ms 2 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
3 * * * Request timed out.
4 130 ms 129 ms 128 ms TWO-DEGREES.ear1.LosAngeles6.Level3.net [4.26.2.82]
5 127 ms 129 ms 130 ms 7-1-10.ear1.LosAngeles6.Level3.net [4.26.2.81]
6 134 ms 134 ms 134 ms ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.146]
7 * * * Request timed out.
....
30 * * * Request timed out.
Trace complete.
and ipconfig output:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : fritz.box
IPv6 Address. . . . . . . . . . . : 2406:e007:6457:7101:94ea:ae4d:deb0:63c2
Temporary IPv6 Address. . . . . . : 2406:e007:6457:7101:e845:1ef6:a791:c69d
Link-local IPv6 Address . . . . . : fe80::94ea:ae4d:deb0:63c2%10
IPv4 Address. . . . . . . . . . . : 192.168.178.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::3a10:d5ff:fea7:80b2%10
192.168.178.1
Now, I imagine the fact that ping is talking to a different IP address to what nslookup returns is possible significant.
What should my next step be?
dns ping nslookup
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
The website is bitbucket.org. I only noticed when a push timeout out. The issue is only on one PC (Win10). Chrome, Firefox and Edge all have the issue. All other PCs' on the network, and an iPad, Android phones, have no issues with that or any other websites. Here's the ping and nslookup output from the offending machine:
ping bitbucket.org -n 1 -w 10000 -l 1
Pinging bitbucket.org [104.192.143.3] with 1 bytes of data:
^
--------------------------
Request timed out.
Ping statistics for 104.192.143.3:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
C:PROJECTSTOOLSRC>nslookup bitbucket.org
Server: fritz.box
Address: fd00::3a10:d5ff:fea7:80b2
Non-authoritative answer:
Name: bitbucket.org
Addresses: 2406:da00:ff00::6b17:d1f5
2406:da00:ff00::22c0:3470
2406:da00:ff00::22c5:2ef4
18.205.93.0
18.205.93.1
18.205.93.2
^
--------------------------
C:PROJECTSTOOLSRC>tracert bitbucket.org
Tracing route to bitbucket.org [104.192.143.3]
over a maximum of 30 hops:
1 2 ms 2 ms 3 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
2 4 ms 2 ms 2 ms 155.32.69.111.static.snap.net.nz [111.69.32.155]
3 * * * Request timed out.
4 130 ms 129 ms 128 ms TWO-DEGREES.ear1.LosAngeles6.Level3.net [4.26.2.82]
5 127 ms 129 ms 130 ms 7-1-10.ear1.LosAngeles6.Level3.net [4.26.2.81]
6 134 ms 134 ms 134 ms ae-0-11.bar2.SanFrancisco1.Level3.net [4.69.140.146]
7 * * * Request timed out.
....
30 * * * Request timed out.
Trace complete.
and ipconfig output:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : fritz.box
IPv6 Address. . . . . . . . . . . : 2406:e007:6457:7101:94ea:ae4d:deb0:63c2
Temporary IPv6 Address. . . . . . : 2406:e007:6457:7101:e845:1ef6:a791:c69d
Link-local IPv6 Address . . . . . : fe80::94ea:ae4d:deb0:63c2%10
IPv4 Address. . . . . . . . . . . : 192.168.178.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::3a10:d5ff:fea7:80b2%10
192.168.178.1
Now, I imagine the fact that ping is talking to a different IP address to what nslookup returns is possible significant.
What should my next step be?
dns ping nslookup
dns ping nslookup
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
asked Feb 4 at 20:41
rossmcmrossmcm
74931946
74931946
1
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
tried the/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine givesPinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others:Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.
– rossmcm
Feb 4 at 21:03
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Neither had any effect.
– rossmcm
Feb 4 at 21:59
|
show 2 more comments
1
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
tried the/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine givesPinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others:Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.
– rossmcm
Feb 4 at 21:03
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Neither had any effect.
– rossmcm
Feb 4 at 21:59
1
1
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
tried the
/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine gives Pinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others: Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.– rossmcm
Feb 4 at 21:03
tried the
/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine gives Pinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others: Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.– rossmcm
Feb 4 at 21:03
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Neither had any effect.
– rossmcm
Feb 4 at 21:59
Neither had any effect.
– rossmcm
Feb 4 at 21:59
|
show 2 more comments
0
active
oldest
votes
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
});
}
});
draft saved
draft discarded
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%2f1401994%2fwhy-has-one-pc-suddenly-become-unable-to-see-one-one-particular-website%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f1401994%2fwhy-has-one-pc-suddenly-become-unable-to-see-one-one-particular-website%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
I suggest opening an elevator cmd prompt and running 'ipconfig /flushdns' , then trying the ping again. It may be that the specific server at 104.192.143.3 is down at this time.
– Christopher Hostage
Feb 4 at 20:46
I also get no pings back, so it may be that those hosts have ping-response turned off. I note that the website is still up. bitbucket.status.atlassian.com shows all operational.
– Christopher Hostage
Feb 4 at 20:49
tried the
/flushdns. Tried restarting PC and router. I agree with you about the ping. The other PC's fail the ping test but they can open the web page. But the offending machine givesPinging bitbucket.org [104.192.143.3] with 32 bytes of data:', but the others:Pinging bitbucket.org [18.205.93.1] with 32 bytes of data:'. The IP addresses should be the same, right? Incidentally, I can access the status page on the offending PC.– rossmcm
Feb 4 at 21:03
Have you tried accessing the website in incognito mode on the affected computer/browser, or have you tried clearing the browser cache?
– DrZoo
Feb 4 at 21:49
Neither had any effect.
– rossmcm
Feb 4 at 21:59