US Telco Support > AT&T > AT&T U-verse > Blocked website

reply to kawemt

Re: Blocked website

reply to kawemt

reply to kawemt
FWIW, it is not just U-verse connections that can't get to the site in question; I can't get to it from my backup AT&T DSL connection either (but Comcast has no problems reaching it).

C:\>use-att.cmd
 
Pinging 192.168.1.254 with 32 bytes of data:
 
Reply from 192.168.1.254: bytes=32 time=13ms TTL=253
 
Ping statistics for 192.168.1.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 13ms, Average = 13ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.9 metric 10
You are now using the Windcrest AT&T backup connection!
 
C:\>ping rottweilerconnection.ca
 
Pinging rottweilerconnection.ca [97.74.215.113] with 32 bytes of data:
 
Request timed out.
Request timed out.
Request timed out.
Request timed out.
 
Ping statistics for 97.74.215.113:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
 
C:\>use-comcast.cmd
 
Pinging 192.168.9.254 with 32 bytes of data:
 
Reply from 192.168.9.254: bytes=32 time<1ms TTL=64
 
Ping statistics for 192.168.9.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.254 metric 10
You are now using the Comcast Business Class connection!
 
C:\>ping rottweilerconnection.ca
 
Pinging rottweilerconnection.ca [97.74.215.113] with 32 bytes of data:
 
Reply from 97.74.215.113: bytes=32 time=83ms TTL=48
Reply from 97.74.215.113: bytes=32 time=85ms TTL=48
Reply from 97.74.215.113: bytes=32 time=83ms TTL=48
Request timed out.
 
Ping statistics for 97.74.215.113:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 83ms, Maximum = 85ms, Average = 83ms
 
C:\>use-att.cmd
 
Pinging 192.168.1.254 with 32 bytes of data:
 
Reply from 192.168.1.254: bytes=32 time=6ms TTL=253
 
Ping statistics for 192.168.1.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 6ms, Average = 6ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.9 metric 10
You are now using the Windcrest AT&T backup connection!
 
C:\>tracert rottweilerconnection.ca
 
Tracing route to rottweilerconnection.ca [97.74.215.113]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ps1.dcs-net [192.168.9.9]
  2     4 ms     3 ms     3 ms  ap1-dcs-net [192.168.8.254]
  3     8 ms     8 ms     8 ms  192.168.1.254
  4    31 ms    31 ms    31 ms  adsl-98-87-59-1.bna.bellsouth.net [98.87.59.1]
  5    35 ms    33 ms    35 ms  70.159.210.120
  6    35 ms    35 ms    34 ms  70.159.210.122
  7   162 ms   175 ms   173 ms  70.159.210.119
  8    37 ms    38 ms    37 ms  12.81.32.144
  9    34 ms    31 ms    33 ms  12.81.32.45
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14  ^C
C:\>use-comcast.cmd
 
Pinging 192.168.9.254 with 32 bytes of data:
 
Reply from 192.168.9.254: bytes=32 time<1ms TTL=64
 
Ping statistics for 192.168.9.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
 
C:\>route change 0.0.0.0 mask 0.0.0.0 192.168.9.254 metric 10
You are now using the Comcast Business Class connection!
 
C:\>tracert rottweilerconnection.ca
 
Tracing route to rottweilerconnection.ca [97.74.215.113]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  gw1.dcs-net [192.168.9.254]
  2    31 ms    10 ms    26 ms  107.3.232.1
  3    10 ms    10 ms     9 ms  xe-4-0-0-0-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  4    11 ms     9 ms    11 ms  xe-2-1-1-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.53]
  5    22 ms    28 ms    19 ms  pos-5-7-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.181]
  6    20 ms    18 ms    16 ms  146.82.35.121
  7    68 ms    68 ms    67 ms  po2-20G.ar2.PHX1.gblx.net [67.16.132.70]
  8    83 ms    84 ms    83 ms  64.210.13.110
  9    84 ms    84 ms    84 ms  be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
 10    84 ms    83 ms    83 ms  be39.trmc0215-01.ars.mgmt.phx3.gdg [184.168.0.73]
 11   194 ms    83 ms    83 ms  ip-216-69-188-102.ip.secureserver.net [216.69.188.102]
 12    83 ms    83 ms    84 ms  p3nlh264.shr.prod.phx3.secureserver.net [97.74.215.113]
 
Trace complete.
 

reply to kawemt
This is not a problem with u-verse but rather with the AT&T network . I manage a website for a local theater group hosted by GoDaddy. Since Wednesday of this week I have not been able to access this site from my home U-verse network using my Either of my macs, my iPod, iPhones, or my windows 7 laptop. Further investigation I find it's not available form AT&T 3G or 4g networks. Users of our site have complained that it they can not reach either . These users include at least one AT&T DSL user and uverse users. I spent some time on the phone withmy AT&T uverse support. That was getting pointless has I had a real hard time convincing the script monkeys on the support line that this was not related to my home connection but rather an issue with the broder AT&T network.

I then called tech support at GoDaddy which is fortunately staffed by individuals we have graduated beyond script monkey school. We tried serverla things including try to acces via the shared IP. No dice. It's not a DNS issue. The support staff found that it is a known issue and GoDAddy was actively working on the issue with AT&T. No ETA. This was last night about 900 P! Eastern time. I will follow up with them later and if I have news I will update this post.

reply to kawemt
Our network admin just about had a nervous breakdown trying to work with AT&T on the issue I mentioned above. And we had an expensive, dedicated line.

reply to kawemt
Working here at 5:30pm PST on AT&T U-verse.

Works for me too, on U-verse internet in northwest Florida.

reply to kawemt
It seems to be resolved. I am able to connect now.

reply to kawemt
Yep, fixed.

reply to kawemt
works fine on my uverse in indiana