Gr8B84706's profile

Visitor

 • 

7 Messages

Friday, January 7th, 2022 4:56 PM

Closed

My Domain/IP Keeps getting blocked BUT ONLY ON XFINITY!

I have my own domain, gr8britton.com, on which I host a webiste, email and OwnCloud for syncing files, contacts and calendar.  All works great for awhile.  All of a sudden, I will not be able to reach my domain ONLY WHEN ON MY HOME XFINITY Internet.  If I use my mobile carrier (TMO), Work (Cox) or even home with a VPN, it works fine.  I have spent HOURS on the phone with the ridiculous Xfinity support to no avail.  Even have one try to tell me that a pinched coax would cause this.  Seriously?!?! 

I always get, "we don't block IPs" but Xfinity is the ONLY carrier that keeps doing this.  Sometimes, it clears up after a few days, sometimes it is weeks.  Unfortunately, I have no other viable Internet options than Xfinity or I would change in a heartbeat.

Performing a traceroute gives me:

C:\Users\Gr8Br>tracert gr8britton.com

Tracing route to gr8britton.com [69.160.38.2]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  192.168.101.1
  2    10 ms     9 ms     9 ms  96.120.59.25
  3    45 ms    19 ms    11 ms  24.124.154.53
  4    16 ms    10 ms    12 ms  be-1-ar02.pimaco.az.pima.comcast.net [68.86.201.145]
  5    10 ms    13 ms    12 ms  68.87.172.13
  6    23 ms    22 ms    22 ms  be-36912-cs01.losangeles.ca.ibone.comcast.net [96.110.45.129]
  7    22 ms    27 ms    21 ms  be-1111-cr11.losangeles.ca.ibone.comcast.net [96.110.45.162]
  8    29 ms    30 ms    28 ms  be-302-cr11.9greatoaks.ca.ibone.comcast.net [96.110.38.94]
  9    38 ms    44 ms    30 ms  be-1211-cs02.9greatoaks.ca.ibone.comcast.net [68.86.166.141]
 10    28 ms    30 ms    33 ms  be-2204-pe04.9greatoaks.ca.ibone.comcast.net [96.110.36.182]
 11    31 ms    29 ms    29 ms  50.208.234.110
 12    39 ms    39 ms    43 ms  ae6-0.cr02.lsaj01-ca.us.windstream.net [40.138.83.186]
 13    36 ms    38 ms    38 ms  ae5-0.cr01.lsaj01-ca.us.windstream.net [40.138.83.188]
 14    51 ms    48 ms    50 ms  ae4-0.agr04.phnd01-az.us.windstream.net [74.124.244.21]
 15    47 ms    48 ms    48 ms  ae2-0.pe05.phnd01-az.us.windstream.net [169.130.169.33]
 16    40 ms    42 ms    40 ms  h205.218.133.40.static.ip.windstream.net [40.133.218.205]
 17    39 ms    40 ms    48 ms  eth.14.1.cr2.phx0.phoenixnap.com [108.170.0.29]
 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.

I understand the problem is happening when not at an Xfinity device (at least by its name I am assuming) but the path is due to a partnership with Xfinity.  (Proven by the fact that this ONLY happens when on Xfinity.)

How do we I get Xfinity to actually look into this?

For now, I'm using a VPN to route differently and that is working.  However, I would need to have a VPN for all of my connected devices that need to access my server.

Problem Solver

 • 

502 Messages

3 years ago

Hey @Gr8B84706 , thank you for coming to Xfinity Forums for assistance. I'm sorry to see that's been happening for you! I had my own website years ago and can see how frustrating this would be to deal with. Our team can definitely take a further look into this for you. Could you please send a direct message with your full name and full address?

To send a "Peer to peer" ("Private") message:
Click "Sign In" if necessary
• Click the "Peer to peer chat" icon
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line
• Type your message in the text area near the bottom of the window
• Press Enter to send it

Visitor

 • 

7 Messages

@XfinityCassandra

 I don't mean to be rude, but what good is it going to do me to contact support again?  Literally EVERYTIME I contact support, all they want to do is reboot the modem and say "we don't block."  I've done this on 8 different occasions with the same result.  They will NEVER look at the tracert and never pass on anything to engineers to fix what is going on.

 

Visitor

 • 

14 Messages

3 years ago

It sounds so much like the VPN issue that I had. I would replace the Comcast modem or factory reset it. Not sure how it works, but it solved my VPN issue twice. Please post back your solutions.

https://forums.xfinity.com/conversations/your-home-network/vpn-not-working/61894d32356f1c35c0b20a38

Visitor

 • 

7 Messages

3 years ago

Update: As usual, the offending router eventually quit blocking my IP and it is working....for now.  It WILL happen again as it always does.

Gold Problem Solver

 • 

26.3K Messages

3 years ago

 ... this ONLY happens when on Xfinity ...

The trace you posted shows Comcast passing the traffic on to Windstream, which then passes it on to PhoenixNAP/Secured Servers. What happens to your packets two networks beyond Comcast is completely beyond their control. 

What changes when you swap out your modem/router gateway or use a VPN is the public IP address, which is what the remote server "sees" as the source of your packets. If the server detects traffic from that IP that it is programed to block, it blocks it. Your trace does not show you being blocked by Comcast, it shows your public IP being (possibly) blocked by a device far downstream from them. I say "possibly" because it is not rare for a trace to fail as yours did, yet actual traffic gets through.

You need to work with the admins of the service hosting "gr8britton.com" to resolve this. Fun though it is to bust on Comcast, this one does not appear to be their fault.

FWIW I can reach the site using my Comcast connection with no problem. My trace looks like this:

C>tracert -4 gr8britton.com
Tracing route to gr8britton.com [69.160.38.2] over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  router1 [192.168.1.1]
  2     8 ms     7 ms     7 ms  96.120.9.181
  3     8 ms     8 ms     9 ms  24.124.216.181
  4     8 ms     8 ms     8 ms  96.110.24.214
  5    11 ms    19 ms     9 ms  96.110.25.65
  6    18 ms    17 ms    18 ms  69.139.168.141
  7     *        *       18 ms  96.110.42.173
  8    17 ms    17 ms    17 ms  be-1411-cr11.pittsburgh.pa.ibone.comcast.net [96.110.38.142]
  9    23 ms    23 ms    23 ms  be-302-cr12.ashburn.va.ibone.comcast.net [96.110.32.101]
 10    24 ms    24 ms    23 ms  be-1112-cs01.ashburn.va.ibone.comcast.net [96.110.32.201]
 11    23 ms    23 ms    22 ms  be-2107-pe07.ashburn.va.ibone.comcast.net [96.110.32.186]
 12    23 ms    22 ms    22 ms  50.208.234.90
 13     *        *        *     Request timed out.
 14    59 ms    58 ms    58 ms  ae18-0.cr02.dlls02-tx.us.windstream.net [40.128.10.135]
 15    81 ms    80 ms    81 ms  ae4-0.agr03.phnd01-az.us.windstream.net [169.130.193.231]
 16     *       91 ms    91 ms  ae1-0.pe05.phnd01-az.us.windstream.net [169.130.169.31]
 17    88 ms    87 ms    86 ms  h205.218.133.40.static.ip.windstream.net [40.133.218.205]
 18     *       86 ms    87 ms  eth.14.1.cr1.phx0.phoenixnap.com [108.170.0.9]
 19     *        *        *     Request timed out.
 20    86 ms    87 ms    86 ms  svr163.edns1.com [69.160.38.2]
Trace complete.

(edited)

Visitor

 • 

7 Messages

@BruceW 

The trace you posted shows Comcast passing the traffic on to Windstream, which then passes it on to PhoenixNAP/Secured Servers. What happens to your packets two networks beyond Comcast is completely beyond their control. 

I stated this in my initial post.  And, no, it is NOT completely beyond their control.  Comcast partners with many different backbone providers and these are only hit when using Comcast.  When I used a VPN or another Internet provider, it routes completely different and never goes through Windstream.net or Phoenixnap.com.  So, Comcast CAN rectify this by contacting those companies through which they are routing.

What changes when you swap out your modem/router gateway or use a VPN is the public IP address, which is what the remote server "sees" as the source of your packets. If the server detects traffic from that IP that it is programed to block, it blocks it. Your trace does not show you being blocked by Comcast, it shows your public IP being (possibly) blocked by a device far downstream from them. I say "possibly" because it is not rare for a trace to fail as yours did, yet actual traffic gets through.

I have already stated what is different.

You need to work with the admins of the service hosting "gr8britton.com" to resolve this. Fun though it is to bust on Comcast, this one does not appear to be their fault.

The problem was not at gr8britton.com.  Like I said, ISPs like Comcast use many different partners.  In a case this like, when Comcast is the only ISP routing through those routers and the only ones having the problem, it is VERY high probability that it is there partner, with whom they can communicate the issue if they would only do their job.

FWIW I can reach the site using my Comcast connection with no problem. My trace looks like this:

As stated earlier, the issue eventually went away.  But, it WILL come back again as it has the previous 8-10 times this has happened.

Contributor

 • 

167 Messages

3 years ago

Hey late to the thread here but are you referring to here? <I cannot justify resetting my modem/router and having to completely setup the router side again>

Is this reference to firewall rules?

Visitor

 • 

1 Message

3 years ago

I'm experiencing the exact same issue and I see no solution. It's very frustrating and Xfinity helpdesk is a joke. All they do is ask me restart the modem!

Expert

 • 

110.1K Messages

@user_0b6129​ 

Please create a new topic of your own here on this board detailing your issue. Thanks. The original poster has not returned. 4-month-old dead thread is now being closed.
 

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? Please mark an Accepted Answer!tick
forum icon

New to the Community?

Start Here