Visitor
•
4 Messages
Xfinity issue connecting to my work VPN
I'm having problems connecting to gpcloud.connect.boeing.com and gpcloud.connect.boeing.com.
I called my work IT and they say Xfinity is blocking their URLs. It is working when I use the hotspot on my phone, so the problem is in Xfinity side.
I run through the steps mentioned here: https://forums.xfinity.com/conversations/your-home-network/unable-to-connect-to-internet-with-my-work-laptop/697e54a8bef17951d874fce6?commentId=697e570fbef17951d87543bb and it is not solving the problem.
As a note, this was working on Thursday 02/12 and has been working for the past weeks. I noticed the problem Friday 02/13 in the Morning.
See ping/traceroutes below to the two endpoints, showing it is not reaching out destination but it is pass the home internet gateway.
I need a solution to this, otherwise I cannot work, if I cannot work this internet connection is useless to me.
Also, the xfinity assistant/chat is completely useless and frustrating for this. How can I open an actual ticket/complain or talk to a human?
% traceroute gpcloud.connect.boeing.com
traceroute to tbc.fed.prismaaccess.com (3.221.142.193), 64 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 12.219 ms 4.635 ms 5.392 ms
2 10.60.129.43 (10.60.129.43) 14.670 ms
10.60.129.42 (10.60.129.42) 39.557 ms 103.862 ms
3 po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25) 15.975 ms
po-60-rur301.bellevue.wa.seattle.comcast.net (96.217.132.21) 18.033 ms
po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25) 14.409 ms
4 po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118) 15.963 ms
po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157) 31.732 ms
po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118) 17.781 ms
5 be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89) 16.384 ms 19.938 ms
po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157) 15.395 ms
6 be-36141-cs04.seattle.wa.ibone.comcast.net (68.86.93.13) 39.409 ms
be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89) 19.495 ms
be-36121-cs02.seattle.wa.ibone.comcast.net (68.86.93.5) 18.249 ms
7 be-36131-cs03.seattle.wa.ibone.comcast.net (68.86.93.9) 36.111 ms
be-2401-pe01.seattle.wa.ibone.comcast.net (96.110.39.230) 14.262 ms
be-36131-cs03.seattle.wa.ibone.comcast.net (68.86.93.9) 14.488 ms
8 * be-2201-pe01.seattle.wa.ibone.comcast.net (96.110.39.206) 26.799 ms *
9 * * *
10 * * *
% ping -c 5 gpcloud.connect.boeing.com
PING tbc.fed.prismaaccess.com (3.221.142.193): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- tbc.fed.prismaaccess.com ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
---
% traceroute gp.connect.boeing.com
traceroute to gp-connect.lb.boeing.com (130.76.179.240), 64 hops max, 40 byte packets
1 10.0.0.1 (10.0.0.1) 6.014 ms 3.421 ms 3.997 ms
2 10.60.129.43 (10.60.129.43) 13.379 ms
10.60.129.42 (10.60.129.42) 15.912 ms 13.909 ms
3 po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25) 13.337 ms
po-60-rur301.bellevue.wa.seattle.comcast.net (96.217.132.21) 17.216 ms
po-60-rur302.bellevue.wa.seattle.comcast.net (96.217.132.25) 106.948 ms
4 po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118) 16.137 ms
po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157) 18.224 ms
po-2-rur302.bellevue.wa.seattle.comcast.net (69.139.161.118) 18.509 ms
5 be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89) 15.468 ms 13.324 ms
po-300-xar02.bellevue.wa.seattle.comcast.net (68.86.96.157) 16.415 ms
6 ae13.edge6.sea1.sp.lumen.tech (4.68.37.129) 11.674 ms
be-300-arsc1.seattle.wa.seattle.comcast.net (24.124.128.89) 17.466 ms
ae13.edge6.sea1.sp.lumen.tech (4.68.37.129) 18.117 ms
7 ae13.edge6.sea1.sp.lumen.tech (4.68.37.129) 16.888 ms
ae1.3618.ear1.lasvegas1.net.lumen.tech (4.69.209.50) 47.810 ms
ae13.edge6.sea1.sp.lumen.tech (4.68.37.129) 18.108 ms
8 the-boeing.ear1.lasvegas1.level3.net (4.25.9.138) 51.313 ms
ae1.3618.ear1.lasvegas1.net.lumen.tech (4.69.209.50) 46.611 ms
the-boeing.ear1.lasvegas1.level3.net (4.25.9.138) 52.531 ms
9 the-boeing.ear1.lasvegas1.level3.net (4.25.9.138) 46.807 ms * 58.219 ms
10 * * *
11 * * *
12 * * *
% ping -c 5 gp.connect.boeing.com
PING gp-connect.lb.boeing.com (130.76.150.17): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
--- gp-connect.lb.boeing.com ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
Hudabac
Regular Visitor
•
5 Messages
12 hours ago
I am having the same problem which I first noticed on Friday, 2/13. I deactivated Xfinity Advanced Security and I will re-test tomorrow but that may fail as it did for you. It worked for me on Wednesday 2/11 of last week.
I saw instructions about adjusting the firewall to "Low Security" but this has not been possible for a while since all modem changes are done with the Xfinity smartphone app. I called the Help Desk. The tech remoted to my PC and did the same ping tests that I did. It's not a problem with Boeing servers.
Below are my network tests:
C:\>ping gp.connect.boeing.com
Pinging gp-connect.lb.boeing.com [130.76.179.224] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 130.76.179.224:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>tracert gp.connect.boeing.com
Tracing route to gp-connect.lb.boeing.com [130.76.179.224]
over a maximum of 30 hops:
1 9 ms 4 ms 5 ms 192.168.1.1
2 24 ms 18 ms 18 ms 10.22.104.195
3 23 ms 24 ms 18 ms po-322-358-rur402.bellevue.wa.seattle.comcast.net [68.85.145.117]
4 21 ms 12 ms 14 ms po-400-xar02.bellevue.wa.seattle.comcast.net [96.216.61.61]
5 19 ms 20 ms 26 ms be-300-arsc1.seattle.wa.seattle.comcast.net [24.124.128.89]
6 32 ms 13 ms 14 ms ae13.edge6.sea1.sp.lumen.tech [4.68.37.129]
7 48 ms 45 ms 50 ms ae1.3618.ear1.LasVegas1.net.lumen.tech [4.69.209.50]
8 91 ms 67 ms 68 ms THE-BOEING.ear1.LasVegas1.Level3.net [4.25.9.138]
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.
C:\>ping gpcloud.connect.boeing.com
Pinging tbc.fed.prismaaccess.com [3.221.142.193] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 3.221.142.193:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>tracert gpcloud.connect.boeing.com
Tracing route to tbc.fed.prismaaccess.com [3.221.142.193]
over a maximum of 30 hops:
1 9 ms 5 ms 5 ms 192.168.1.1
2 20 ms 20 ms 13 ms 10.22.104.195
3 21 ms 14 ms 16 ms po-322-358-rur402.bellevue.wa.seattle.comcast.net [68.85.145.117]
4 71 ms 39 ms 16 ms po-400-xar02.bellevue.wa.seattle.comcast.net [96.216.61.61]
5 17 ms 19 ms 25 ms be-300-arsc1.seattle.wa.seattle.comcast.net [24.124.128.89]
6 * * 15 ms be-36111-cs01.seattle.wa.ibone.comcast.net [68.86.93.1]
7 22 ms 19 ms 18 ms be-2101-pe01.seattle.wa.ibone.comcast.net [96.110.39.202]
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.
C:\>ping token.gp.connect.boeing.com
Pinging token-gp-connect.lb.boeing.com [130.76.7.50] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 130.76.7.50:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\>tracert token.gp.connect.boeing.com
Tracing route to token-gp-connect.lb.boeing.com [130.76.7.50]
over a maximum of 30 hops:
1 9 ms 3 ms 5 ms 192.168.1.1
2 21 ms 18 ms 16 ms 10.22.104.195
3 31 ms 24 ms 26 ms po-322-358-rur402.bellevue.wa.seattle.comcast.net [68.85.145.117]
4 20 ms 15 ms 16 ms po-400-xar02.bellevue.wa.seattle.comcast.net [96.216.61.61]
5 20 ms 18 ms 16 ms be-300-arsc1.seattle.wa.seattle.comcast.net [24.124.128.89]
6 23 ms 16 ms 16 ms ae13.edge6.sea1.sp.lumen.tech [4.68.37.129]
7 19 ms 23 ms 20 ms s0.gna.bbnplanet.net [4.25.13.94]
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.
1
0