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
As in that other poster's thread, perhaps the results of a trace route to the site will reveal where the blocking is ?
FWIW, it still may be that your previous Comcast assigned WAN /public IP address was being blocked by the site for some reason. By using your own separate router, the system saw the new MAC address of it which forced a change of your Public IP addy. YMMV.
Seen hosting companies say that many times before, and traces proved them to be wrong. As I stated earlier, a trace route may have proved something either way.
EG my apologies I did a traceroute earlier as I posted the first one. So I just did it again and it shows the same exact thing as before so here is the trace:
traceroute to 68.66.205.103 (68.66.205.103), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.455 ms 6.492 ms 1.466 ms
2 96.120.98.89 (96.120.98.89) 21.812 ms 19.882 ms 19.668 ms
3 te-8-2-ur01.sebring.fl.westfl.comcast.net (68.85.98.217) 20.342 ms 18.705 ms 19.966 ms
4 162.151.6.17 (162.151.6.17) 17.397 ms 38.680 ms 31.225 ms
5 162.151.6.61 (162.151.6.61) 20.279 ms 27.077 ms 29.386 ms
6 be-33661-cr02.56marietta.ga.ibone.comcast.net (68.86.95.41) 33.364 ms 42.272 ms 30.360 ms
7 be-11440-pe01.56marietta.ga.ibone.comcast.net (68.86.85.246) 49.322 ms 31.336 ms 30.018 ms
8 50.242.148.190 (50.242.148.190) 30.014 ms 27.206 ms 39.983 ms
9 be2848.ccr42.atl01.atlas.cogentco.com (154.54.6.117) 39.945 ms 40.069 ms 36.595 ms
10 be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 43.391 ms be2113.ccr42.dca01.atlas.cogentco.com (154.54.24.221) 49.733 ms be2112.ccr41.dca01.atlas.cogentco.com (154.54.7.157) 41.873 ms
11 be2891.ccr21.cle04.atlas.cogentco.com (154.54.82.249) 66.175 ms be2892.ccr22.cle04.atlas.cogentco.com (154.54.82.253) 64.749 ms 68.849 ms
12 be2006.rcr21.dtw04.atlas.cogentco.com (154.54.5.10) 61.183 ms be2028.rcr21.dtw04.atlas.cogentco.com (154.54.6.217) 69.867 ms be2006.rcr21.dtw04.atlas.cogentco.com (154.54.5.10) 59.907 ms
13 38.142.132.58 (38.142.132.58) 63.173 ms 61.878 ms 84.349 ms
14 75.98.175.255.static.a2webhosting.com (75.98.175.255) 55.451 ms 62.960 ms 68.455 ms
15 75.98.175.210.static.a2webhosting.com (75.98.175.210) 59.794 ms 62.316 ms 64.100 ms
16 * * *
17 * * *
18 * * *
This is the exact same results as earlier so I don't know what happened.
I've worked as a Network Admin since 1997 and retired in April 2012 and trust me this one stumped me big time....I've had to deal with DNS stuff not changing and many other things but never seen this. What was weird is I was able to connect to A2hosting.com with no issues but as soon as I clicked on login thats where the problem started. Yes I know it has to do what server my stuff is on but man this has me scratching my head....
Yep well your packets are in the web host's web space so it's not a Comcast block.