Hi,
Over the last couple of days, my connection to my corporate Webex server has been flaky. This is a real problem because all of my meetings are via Webex.
When it stops working, I am unable to join Webex meetings on either my Mac or my phone when they are connected to the network via my Virgin Media hub (wired or Wifi). If I turn off Wifi on my phone, I am able to join meetings using my mobile data. So this appears to be an issue with connecting to my corporate Webex server via Virgin Media.
I appear to be able to ping the server:
$ ping ibm.webex.com
PING ibm.webex.com (81.99.162.48): 56 data bytes
64 bytes from 81.99.162.48: icmp_seq=0 ttl=248 time=21.665 ms
64 bytes from 81.99.162.48: icmp_seq=1 ttl=248 time=18.717 ms
64 bytes from 81.99.162.48: icmp_seq=2 ttl=248 time=23.653 ms
64 bytes from 81.99.162.48: icmp_seq=3 ttl=248 time=19.278 ms
But traceroute has trouble finding a route to the server:
$ traceroute ibm.webex.com
traceroute to ibm.webex.com (81.99.162.48), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 5.051 ms 3.161 ms 3.020 ms
2 * * *
3 sotn-core-2b-xe-821-0.network.virginmedia.net (62.255.72.45) 23.783 ms 19.753 ms 18.646 ms
4 * * *
5 lang-dclcore-1b-port-channel1.network.virginmedia.net (62.254.85.6) 19.409 ms 22.301 ms 21.424 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
When attempting to join a meeting using Webex on my Mac, I see the following error:
All of my other applications are not experiencing any networking issues... so there is no problem with the network connection.
I do not appear to be able to contact anyone from Virgin Media about this directly for technical assistance.
Is anyone on the community able to help?
Your DNS lookup is wrong because 81.99.162.48 belongs to Virgin Media. This is what you should get.
C:\>tracert ibm.webex.com
Tracing route to global-nebulaie.webex.com [66.114.168.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 11 ms 11 ms haye-core-2a-ae36-0.network.virginmedia.net [80.3.178.217]
4 * * * Request timed out.
5 12 ms 11 ms 19 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
6 * * * Request timed out.
7 81 ms 84 ms 81 ms us-nyc01b-rd2-ae-9-0.aorta.net [84.116.140.170]
8 94 ms 94 ms 86 ms us-was03a-ri1-ae-10-0.aorta.net [84.116.130.174]
9 99 ms 99 ms 108 ms 4.68.39.141
10 * * * Request timed out.
11 102 ms 99 ms 113 ms 4.14.99.10
12 * * * Request timed out.
13 89 ms 89 ms 88 ms iad02-wxbb-crt01-bu60.webex.com [64.68.116.28]
14 130 ms 137 ms 127 ms dfw10-wxbb-crt01-be103.webex.com [64.68.117.217]
15 153 ms 151 ms 152 ms lax10-wxbb-crt02-be102.webex.com [64.68.118.166]
16 145 ms 147 ms 144 ms lax10-wxbb-crt01-be10.webex.com [64.68.118.200]
17 169 ms 170 ms 167 ms 62.109.195.112
18 152 ms 153 ms 150 ms sjc02-wxbb-pe02-bu22.webex.com [64.68.117.125]
19 159 ms * * sjc02-wxp00-gw02-po522-100.webex.com [209.197.223.167]
20 * * * Request timed out.
21 151 ms 151 ms 149 ms global-nebulaie.webex.com [66.114.168.199]
Trace complete.
This is what's reported by VM's DNS.
C:\>nslookup ibm.webex.com 194.168.4.100
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Non-authoritative answer:
Name: global-nebulaie.webex.com
Address: 66.114.168.199
Aliases: ibm.webex.com
nebulaie.webex.comHi Jonny,
Thanks for the hint.
It turns out it was the web safe settings... specifically, the Chat setting.
Disabling it fixed the problem.
