Unable to access any Microsoft sites....

[#1]

Hi @bobpullen,

The same issue here and I'm in the same IP range.

in haste I created a new post.

(https://community.plus.net/t5/Fibre-Broadband/No-access-to-ceratain-websites-ie-microsoft-com-or-duc...)

Thanks help,

[#2]

Hi superrvirgo,

You could try restarting the router and see if you can pickup a new IP. I don't know if bobpullen made any changes to mine to force a IP change.

Probably make sense to get onto plusnet support and see if the can force a ip address change.

It looks like something wrong with the routing rules. It seems to when we go through 172.16.14.211 there are issues.

Hope you get it sorted.

[#3]

Is the clock on your computer set correctly?

[#4]

I guess it is the same issue reported in this post:

https://community.plus.net/t5/Fibre-Broadband/Unable-to-access-any-Microsoft-sites/td-p/1771295

Plusnet / BT either have a routing issue or Microsoft are blocking the IP range.

@bobpullen Is there a internal ticket raised on this issue?

Regards

Richard

[#5]

Moderators Note

Topics merged.

[#6]

---

@RichardB wrote:

@bobpullen Is there a internal ticket raised on this issue?

---

I've flagged it (ref: IMT-6561).

[#7]

Hi @bidbad,

I have restarted my router. I kept it off for about an hour.

After the restart I'm in 213.31. range, all seems ok now. I've got connectivity with Microsoft and the other sites.

However when looking on my gateway it is still 172.16.14.211

BR,

[#8]

Hi @notmyname,

Yes, clock is ok. No issues here.

BR,

[#9]

I have the same issue, first thing this morning. Tried rebooting router, resets, unplugging and waited for over 1 hour but still no joy in accessing Microsoft sites. Finally got through to Plusnet support and lines tested ok, plugged into test socket OK and left funplugged for over 65 min but still no joy! Ticket was raised then closed blaming microsoft!. Rang again and the ticket is reopened. I have posted the link of this community page on the ticket info. Awaiting a reply! Wasted a whole day!

my gateway it is still 172.16.14.238 even after carrying out all the above.

[#10]

@BobD - what's your IP address? It looks to be different to the others that have reported problems.

[#11]

Hi Bobpullen

C:\>tracert microsoft.com

Tracing route to microsoft.com [104.215.148.63]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms dsldevice.lan [192.168.1.254]
2 7 ms 6 ms 6 ms 172.16.14.238
3 * 8 ms 8 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 9 ms 9 ms * 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 9 ms 9 ms 10 ms 195.99.125.138
6 9 ms 9 ms 9 ms 194.72.16.98
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * dsldevice.lan [192.168.1.254] reports: Destination net unreachable.

Trace complete.

[#12]

No RDNS records.

From a quick lookup, the traffic is not leaving the UK from what I can see.

[#13]

Hi Alex also just tried Microsoft.co.uk

C:\>tracert microsoft.co.uk

Tracing route to microsoft.co.uk [13.77.161.179]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms dsldevice.lan [192.168.1.254]
2 6 ms 6 ms 12 ms 172.16.14.238
3 8 ms 8 ms 8 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 8 ms 8 ms 8 ms 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 9 ms 10 ms 10 ms 195.99.125.138
6 10 ms 11 ms 9 ms 194.72.16.192
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[#14]

---

@BobD wrote:

Hi Bobpullen

C:\>tracert microsoft.com

Tracing route to microsoft.com [104.215.148.63]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms dsldevice.lan [192.168.1.254]
2 7 ms 6 ms 6 ms 172.16.14.238
3 * 8 ms 8 ms 141.hiper04.sheff.dial.plus.net.uk [195.166.143.141]
4 9 ms 9 ms * 140.hiper04.sheff.dial.plus.net.uk [195.166.143.140]
5 9 ms 9 ms 10 ms 195.99.125.138
6 9 ms 9 ms 9 ms 194.72.16.98
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * dsldevice.lan [192.168.1.254] reports: Destination net unreachable.

Trace complete.

---

This doesn't tell me your IP address. You can get that from here. I'd suggest only posting the first two octets though (everything before the second dot).

I suspect it starts 195.213... in which case it's different to what has been reported by others up until now.

[#15]

Hi Bobpullen

Yes IP is 

195.213

Your Hostname:
60.229.213.195.dyn.plus.net

Laptop, Desktop and mobile phones cannot access Microsoft sites when connected to router but Mobile is fine when connected via mobile network 4G