You are not logged in.

#1 2016-09-17 19:31:40

eXpies
Member
Registered: 2016-09-17
Posts: 5

Can't reach Office365

Hello everyone,
I've got a strange issue and it seems that I will not figure that one out without help :-(.
I can not reach Office365 from my workstation. (4.7.2-1-ARCH)
Although, Office365 works fine from another Ubuntu (HTPC) over ethernet, Windows Laptop over WIFI.

Iptables has empty rules list and stopped.

Ping results:

[expies@archcore ~]$ ping office365.com
PING office365.com (23.99.229.108) 56(84) bytes of data.
^C
--- office365.com ping statistics ---
15 packets transmitted, 0 received, 100% packet loss, time 14008ms

Tracepath results:

[expies@archcore ~]$ tracepath office365.com
 1?: [LOCALHOST]                                         pmtu 1500
 1:  gateway                                               0.452ms 
 1:  gateway                                               0.427ms 
 2:  gateway                                               0.440ms pmtu 1492
 2:  lns2.nta.nv.net.il                                  132.370ms 
 3:  agr1-rb4-lns-lns1-nta.nv.net.il                     119.628ms 
 4:  gw1-nta-0-1-0-2-core1.nta.nv.net.il                 127.767ms 
 5:  gw1-fra-0-4-0-3-100-gw1.nta.nv.net.il               170.165ms asymm  7 
 6:  10.10.50.1                                          180.579ms asymm  7 
 7:  no reply
 8:  ae12-0.fra-96cbe-1b.ntwk.msn.net                    179.885ms asymm  9 
 9:  be-3-0.ibr02.ams.ntwk.msn.net                       313.976ms asymm 29 
10:  be-1-0.ibr01.ams.ntwk.msn.net                       294.611ms asymm 27 
11:  be-7-0.ibr01.amb.ntwk.msn.net                       300.081ms asymm 26 
12:  be-5-0.ibr01.lts.ntwk.msn.net                       311.272ms asymm 26 
13:  ae62-0.lts-96cbe-1b.ntwk.msn.net                    185.626ms asymm  8 
14:  ae22-0.lon04-96cbe-1b.ntwk.msn.net                  201.309ms asymm  9 
15:  be-8-0.ibr02.nyc04.ntwk.msn.net                     321.670ms asymm 23 
16:  be-8-0.ibr02.nyc04.ntwk.msn.net                     304.822ms asymm 23 
17:  be-1-0.ibr01.nyc04.ntwk.msn.net                     299.364ms asymm 21 
18:  be-4-0.ibr03.ch1.ntwk.msn.net                       302.570ms asymm 20 
19:  be-4-0.ibr03.ch1.ntwk.msn.net                       315.458ms asymm 20 
20:  be-5-0.ibr01.dm2.ntwk.msn.net                       275.028ms asymm 17 
21:  be-5-0.ibr01.dm2.ntwk.msn.net                       290.761ms asymm 17 
22:  no reply
23:  no reply
24:  no reply
25:  no reply
26:  no reply
27:  no reply
28:  no reply
29:  no reply
30:  no reply
     Too many hops: pmtu 1492
     Resume: pmtu 1492 

ifconfig:

enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::3da9:e3e3:6031:3940  prefixlen 64  scopeid 0x20<link>
        ether 30:5a:3a:e0:7a:99  txqueuelen 1000  (Ethernet)
        RX packets 493061  bytes 651426639 (621.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 281458  bytes 25142880 (23.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xdf100000-df120000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 205988  bytes 12375059 (11.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 205988  bytes 12375059 (11.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:b5:02:22  txqueuelen 1000  (Ethernet)
        RX packets 1129532  bytes 77469781 (73.8 MiB)
        RX errors 0  dropped 60  overruns 0  frame 0
        TX packets 145708  bytes 2989558547 (2.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:fe9d:5298  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:9d:52:98  txqueuelen 1000  (Ethernet)
        RX packets 20382  bytes 22057455 (21.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43084  bytes 4863710 (4.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::fc54:ff:feea:6975  prefixlen 64  scopeid 0x20<link>
        ether fe:54:00:ea:69:75  txqueuelen 1000  (Ethernet)
        RX packets 75576  bytes 23350121 (22.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 86557  bytes 93431198 (89.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I would really appreciate any help.

Offline

#2 2016-09-17 19:39:04

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: Can't reach Office365

I cannot ping it either but I can connect via https.  Can you?


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#3 2016-09-17 19:48:28

eXpies
Member
Registered: 2016-09-17
Posts: 5

Re: Can't reach Office365

Nope, I can not.

Just checked though a Windows Server 2012 R2 Virtual Machine.
You are right, there is no reply from the destination but the I can get to the web interface through that VM.

I have paid attention that I can not resolve "outlook.office365.com" from the arch itself but can from all the others...

Last edited by eXpies (2016-09-17 19:52:37)

Offline

#4 2016-09-17 19:50:54

eXpies
Member
Registered: 2016-09-17
Posts: 5

Re: Can't reach Office365

I have paid attention that I can not resolve "outlook.office365.com" from the arch itself but can from all the others...

Offline

#5 2016-09-17 22:18:15

R00KIE
Forum Fellow
From: Between a computer and a chair
Registered: 2008-09-14
Posts: 4,734

Re: Can't reach Office365

Maybe an IPv6 problem? Every once in a while having ipv6 active but not support somewhere along the network causes problems. Try disabling ipv6 and check if you can connect.


R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

Offline

#6 2016-09-18 06:10:47

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: Can't reach Office365

eXpies wrote:

Nope, I can not.

...

but the I can get to the web interface through that VM.

You're contradicting yourself. What is the problem that you think you have?

If it's a DNS problem, then the first obvious file to check is /etc/resolv.conf

Offline

#7 2016-09-18 20:17:26

eXpies
Member
Registered: 2016-09-17
Posts: 5

Re: Can't reach Office365

brebs, I could not properly resolve "outlook.office365.com" and could not reach it through IP.

ROOKIE, you were right.
Added "ipv6.disable=1" to grub and all start working like a charm.

Thank you guys!

Offline

Board footer

Powered by FluxBB