Community Forum

Connection issues to 69.x.x.x networks in SF

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

Frequent Visitor

Connection issues to 69.x.x.x networks in SF

having trouble connecting to any website on the 69.x.x.x network

 

C:\Users\owner>ping login.facebook.com

 

Pinging login.facebook.com [69.63.180.173] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

 

Ping statistics for 69.63.180.173:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

C:\Users\owner>ping www.yahoo.com

 

Pinging www-real.wa1.b.yahoo.com [209.131.36.158] with 32 bytes of data:

Reply from 209.131.36.158: bytes=32 time=23ms TTL=53

Reply from 209.131.36.158: bytes=32 time=21ms TTL=53

Reply from 209.131.36.158: bytes=32 time=51ms TTL=53

Reply from 209.131.36.158: bytes=32 time=18ms TTL=53

 

Ping statistics for 209.131.36.158:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 18ms, Maximum = 51ms, Average = 28ms

 

 

 

C:\Users\owner>tracert login.facebook.com

 

Tracing route to login.facebook.com [69.63.181.22]

over a maximum of 30 hops:

 

  1     2 ms     2 ms     3 ms  172.17.3.1

  2     4 ms     *       11 ms  172.17.1.1

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *     ^C

C:\Users\owner>

 

 

 

C:\Users\owner>tracert www.yahoo.com

 

Tracing route to www-real.wa1.b.yahoo.com [209.131.36.158]

over a maximum of 30 hops:

 

  1     2 ms     2 ms     2 ms  172.17.3.1

  2     5 ms     *        3 ms  172.17.1.1

  3     *        *        *     Request timed out.

  4    21 ms     *       17 ms  te-7-3-ur02.sf19th.ca.sfba.comcast.net [68.87.195.45]

  5    15 ms     *       13 ms  te-0-10-0-0-ar01.oakland.ca.sfba.comcast.net [68.85.154.34]

  6    14 ms     *       17 ms  pos-0-5-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.137]

  7    17 ms     *       16 ms  pos-0-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.181]

^C

C:\Users\owner>

 

 

This is just one example of a website going to the 69.x.x.x network.  Tried opening several tickets Comcast customer service and they keep closing the ticket.  Is anybody else having this issue in SF?  Thanks... 

 

 

Silver Problem Solver

Re: Connection issues to 69.x.x.x networks in SF

What's the IP and network mask of your router's WAN interface? Leave out the last number of the IP for privacy.
Frequent Visitor

Re: Connection issues to 69.x.x.x networks in SF

Destination LAN IPSubnet MaskGatewayInterface
0.0.0.0255.255.255.069.181.44.xWAN (Internet)
0.0.0.00.0.0.069.181.44.1WAN (Internet)
69.0.0.0255.0.0.069.181.44.xWAN (Internet)
69.181.44.0255.255.252.069.181.44.xWAN (Internet)
Expert

Re: Connection issues to 69.x.x.x networks in SF

Try it without the router being in the mix.


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Frequent Visitor

Re: Connection issues to 69.x.x.x networks in SF

The router is needed to convert the coax to an ethernet from Comcast.
Expert

Re: Connection issues to 69.x.x.x networks in SF

So you are using a combo router/modem gateway device ? If so that removes one element of troubleshooting.


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Frequent Visitor

Re: Connection issues to 69.x.x.x networks in SF

Yes, it is and I'm directly connected to the broadband router which converts coax to ethernet.
Problem Solver

Re: Connection issues to 69.x.x.x networks in SF


@richard94116 wrote:
... router which converts coax to ethernet.

I don't mean to be nit-picky, but isn't that really the modem?

Frequent Visitor

Re: Connection issues to 69.x.x.x networks in SF

yes, it's a combo broadband router/modem in one device that has a coax connection from Comcast and an ethernet connection for my computer.
Expert

Re: Connection issues to 69.x.x.x networks in SF

Try using this web proxy as a temporary work around:

 

https://proxify.com/

 

Does it work ? 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Silver Problem Solver

Re: Connection issues to 69.x.x.x networks in SF

The 69.0.0.0 route is the problem, I'm not sure where it's coming from. It should only have routes for 69.181.44.0 and 0.0.0.0. What model is the router?

 

It's possible there's something messed up on the DHCP server, I'll ask a Comcast moderator to check. 

Most Valued Poster

Re: Connection issues to 69.x.x.x networks in SF


@Barmar wrote:

The 69.0.0.0 route is the problem, I'm not sure where it's coming from. It should only have routes for 69.181.44.0 and 0.0.0.0. What model is the router?

 

It's possible there's something messed up on the DHCP server, I'll ask a Comcast moderator to check. 


It's possible that the route is causing some kind of issue, but it shouldn't be. It's worth trying to delete the routes because I'm unsure of how the cheap home-router firmware handles redundant routing entries. It's routing the 69.0.0.0/8 supernet out the WAN interface... which is what you would want to do.

 

Also, the only route really needed is:

0.0.0.0 0.0.0.0 69.181.44.1 WAN (Internet)

 The rest are redundant and possibly causing issues.

Frequent Visitor

Re: Connection issues to 69.x.x.x networks in SF

the issue is resolved now.  comcast finally fixed it on their end after numerous calls and opening new tickets every time i called.  i still have the same routing table on my end and things are working fine now so it is definitely something they fixed.  this is just poor customer service on their part.
Silver Problem Solver

Re: Connection issues to 69.x.x.x networks in SF

I just checked my router, and it doesn't have a similar 255.0.0.0 route, I wonder why yours does.

 

I suspect they resolved the problem by enabling proxy ARP on the head-end router.