It can't just be me? (Ping with microsoft domains)
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
So they're finally on to you and have you black listed. ;P I've run into this before, though I'm not a network guy its been explained to me that just because the domain is available doesn't mean it can be pinged.
Failure is not an option; it's the default selection.
-
So they're finally on to you and have you black listed. ;P I've run into this before, though I'm not a network guy its been explained to me that just because the domain is available doesn't mean it can be pinged.
Failure is not an option; it's the default selection.
Mark Nischalke wrote:
just because the domain is available doesn't mean it can be pinged.
Of course not, it's a service... the server has to be configured to respond. Plus firewalls have to allow it.
-
Mark Nischalke wrote:
just because the domain is available doesn't mean it can be pinged.
Of course not, it's a service... the server has to be configured to respond. Plus firewalls have to allow it.
Exactly.. +5
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
It's not just you, Dave. I tried the same test, and received no replies. Your first hit must have broken the domain. Try tapping the keys more gently next time.
Will Rogers never met me.
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I just tried it... the MS domains don't appear to respond to pings. They may just not want people pinging their servers. Have we forgotten about the ping of death[^] already?
-
I just tried it... the MS domains don't appear to respond to pings. They may just not want people pinging their servers. Have we forgotten about the ping of death[^] already?
-
No I haven't forgotten, but I am sure the hardware used for handling the domains traffic should be more advanced than just simply blocking all pings.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Yeah, but sometimes the simplest solution is best.
-
No I haven't forgotten, but I am sure the hardware used for handling the domains traffic should be more advanced than just simply blocking all pings.
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
There's nothing to say that they're obligated to respond... that's what I mean, they probably chose not to as a company-wide policy. Look at how Windows determines internet connectivity (it does not involve pings): http://blog.superuser.com/2011/05/16/windows-7-network-awareness/[^]
-
Yeah, but sometimes the simplest solution is best.
Keep It Simple Stupid (KISS)? ...why not... :)
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Purely conjecture, but some sort of anti DDOS measure. First ping from an address gets through, repeats within a certain time span fail?
Henry Minute Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is. Cogito ergo thumb - Sucking my thumb helps me to think.
-
There's nothing to say that they're obligated to respond... that's what I mean, they probably chose not to as a company-wide policy. Look at how Windows determines internet connectivity (it does not involve pings): http://blog.superuser.com/2011/05/16/windows-7-network-awareness/[^]
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
After a bit of research:
Tracing route to microsoft.com [207.46.232.182]
over a maximum of 30 hops:
0 Roger-PC [xxx.xxx.xxx.xxx]
1 static-ww-xx-yy-zz.dsl1.kgm.az.frontiernet.net [zz.yy.xx.ww]
2 74-47-96-1.dr02.kgmn.az.frontiernet.net [74.47.96.1]
3 ge--1-0-0---0.car01.kgmn.az.frontiernet.net [74.42.150.5]
4 xe--0-1-0---0.cor02.slkc.ut.frontiernet.net [74.40.1.29]
5 ae0---0.cor01.slkc.ut.frontiernet.net [74.40.4.13]
6 ae1---0.cor02.plal.ca.frontiernet.net [74.40.5.61]
7 ae1---0.cbr01.plal.ca.frontiernet.net [74.40.3.170]
8 eli-pni-peering-msn-net.plal.eli.net [208.186.87.10]
9 209.240.198.227
10 xe-7-0-1-0.by2-96c-1a.ntwk.msn.net [207.46.40.62]
11 207.46.40.135
12 ten1-1.tuk-76c-1b.ntwk.msn.net [207.46.46.21]
13 po16.tuk-65ns-mcs-1b.ntwk.msn.net [207.46.35.142]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Roger-PC [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% static-ww-xx-yy-zz.dsl1.kgm.az.frontiernet.net [zz.yy.xx.ww]
0/ 100 = 0% |
2 139ms 0/ 100 = 0% 0/ 100 = 0% 74-47-96-1.dr02.kgmn.az.frontiernet.net [74.47.96.1]
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% ge--1-0-0---0.car01.kgmn.az.frontiernet.net [74.42.150.5]
0/ 100 = 0% |
4 27ms 0/ 100 = 0% 0/ 100 = 0% xe--0-1-0---0.cor02.slkc.ut.frontiernet.net [74.40.1.29]
0/ 100 = 0% |
5 29ms 0/ 100 = 0% 0/ 100 = 0% ae0---0.cor01.slkc.ut.frontiernet.net [74.40.4.13]
0/ 100 = 0% |
6 52ms 0/ 100 = 0% 0/ 100 = 0% ae1---0.cor02.plal.ca.frontiernet.net [74.40.5.61]
0/ 100 = 0% |
7 46ms 0/ 100 = 0% 0/ 100 = 0% ae1---0.cbr01.plal.ca.frontiernet.net [74.40.3.170]
0/ 100 = 0% |
8 60ms 0/ 100 = 0% 0/ 100 = 0% eli-pni-peering-msn-net.plal.eli.net [208.186.87.10]
0/ 100 = 0% |
9 44ms 0/ 100 = 0% 0/ 100 = 0% 209.240.198.227
100/ 100 =100% |
10 --- 100/ 100 =100% 0/ 100 = 0% xe-7-0-1-0.by2-96c-1a.ntwk.msn.net [207.46.40.62] -
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
-
There's nothing to say that they're obligated to respond... that's what I mean, they probably chose not to as a company-wide policy. Look at how Windows determines internet connectivity (it does not involve pings): http://blog.superuser.com/2011/05/16/windows-7-network-awareness/[^]
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
DaveAuld wrote:
Ping microsoft.com
1 reply ok, next 3 time out (207.46.197.32)The only unusual thing is that you actually got a replay from Microsoft's server since they filter ICMP reqests.
-
I have tried 1 computer and 1 laptop. (windows 7, 64bit and 32 bit) Open a command prompt; Ping microsoft.com 1 reply ok, next 3 time out (207.46.197.32) Ping google.com 4 reply ok (209.85.147.147) Is this behaviour the same for everyone else and MS has some sort of additional functionality on their domains as it also happens with msn.com, microsoft.co.uk, msn.co.uk?
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Hmm - spooky. I pinged Microsoft - all ok (205ms) I pinged Apple - no response I pinged Google - all ok (22ms) so, it could be saif of Google & Microsoft - "It was the best of times, it was the worst of times" How appropriate :)
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')