kawemt
join:2012-12-12
Oshkosh, WI | Blocked website Hi I am new here but I had my AT&T U-Verse installed yesterday. My favorite website is a forum that is run out of Canada. I go to the site several time daily. Now that I have switched providers I can no longer reach the website.
I tried different browsers, even a different computer in my house that was on the same internet and none of them would allow the page to open. I contacted the Forum administrator (she is a friend) and she said there were no issues going on with the actual forum. I jumped on my smart phone and was able to access the site with my 3g but still had no luck via my new internet.
When I talked to AT&T last night they assured me they don't block any websites and that it must be my firewall on my pc. I turned that off and tried again and still had no luck. Does anyone here have any suggestions on what I can do to fix this problem?
»rottweilerconnection.ca/
That is the website, as you can see, nothing illegal about it. Could it be because of the .ca on it? |
|
| I just tried pinging the website (I'm on Uverse too), and I get the message "No reply from host". |
|
 stormbowFreedom isn't FREEPremium
join:2002-07-31
Simi Valley, CA | reply to kawemt
I can get to it via my work computer, but my server at home (on U-verse) cannot |
|
|
|
kawemt
join:2012-12-12
Oshkosh, WI | That is exactly the issue I am having and never had before. I can get to it via any internet connect BUT my new U-Verse connection. I had the forum admins double check things at their end for me but everything is up to par with them. Has anyone heard of this happening with U-Verse before? |
|
| reply to kawemt
Works on StLouis Charter cable |
|
alana
join:2009-10-20
Crystal Lake, IL | reply to kawemt
It works on my work backup connection which is a CLEC that Comcast purchased a few years ago (CIMCO).
However, my primary work Internet connection who our ISP uses is AT&T (not Uverse) and I cannot ping it there.
/alan |
|
 MooJohn
join:2005-12-18
Milledgeville, GA | reply to kawemt
Might be an issue with AT&T's DNS -- try switching your DNS settings to some of the free ones, like 4.2.2.1 & 4.2.2.2 -- and see if you can reach the site then.
--
John M - Cranky network guy |
|
mattmac
join:2011-03-27
West Palm Beach, FL | reply to kawemt
I had to use a proxy server .
got to the site fine use any free proxy
I have ATT uverse 12/3 |
|
stormbowFreedom isn't FREEPremium
join:2002-07-31
Simi Valley, CA | reply to MooJohn
said by MooJohn:Might be an issue with AT&T's DNS -- try switching your DNS settings to some of the free ones, like 4.2.2.1 & 4.2.2.2 -- and see if you can reach the site then.
Not DNS, I did nslookups on both my systems and got the same number. There is a bad route somewhere. |
|
| reply to kawemt
From about 5 minutes ago...
C:\Windows\System32>tracert www.rottweilerconnection.ca
Tracing route to rottweilerconnection.ca [97.74.215.113]
over a maximum of 30 hops:
1 3 ms 3 ms 3 ms 192.168.1.254
2 41 ms 24 ms 25 ms 76-243-36-2.lightspeed.cntmoh.sbcglobal.net [76
243.36.2]
3 * * * Request timed out.
4 25 ms 24 ms 24 ms 75.56.96.29
5 27 ms 26 ms 27 ms 12.83.45.1
6 * * * Request timed out.
7 * * * Request timed out.
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 ^C
C:\Windows\System32>ping 97.74.215.113
Pinging 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), |
|
 LagzPremium
join:2000-09-03
The Rock
 ·AT&T DSL Service
| reply to kawemt
» network-tools.com/default.asp?pr···ction.caIP address: 97.74.215.113 Host name: rottweilerconnection.ca Alias: rottweilerconnection.ca 97.74.215.113 is from United States(US) in region North America TraceRoute from Network-Tools.com to 97.74.215.113 [rottweilerconnection.ca] Hop (ms) (ms) (ms) IP Address Host name 1 1 0 0 206.123.64.42 - 2 0 0 0 64.124.196.225 xe-4-2-0.er2.dfw2.us.above.net 3 4 0 0 64.125.27.81 xe-0-1-0.cr2.dfw2.us.above.net 4 5 5 5 64.125.26.134 xe-1-2-0.cr2.iah1.us.above.net 5 28 28 71 64.125.28.73 xe-0-1-0.mpr4.phx2.us.above.net 6 29 29 29 209.66.64.6 209.66.64.6.t01121-04.above.net 7 55 55 55 184.168.0.73 be39.trmc0215-01.ars.mgmt.phx3.gdg 8 55 55 55 184.168.0.73 be39.trmc0215-01.ars.mgmt.phx3.gdg 9 72 72 72 216.69.188.102 ip-216-69-188-102.ip.secureserver.net 10 75 77 75 97.74.215.113 p3nlh264.shr.prod.phx3.secureserver.net Trace complete Retrieving DNS records for rottweilerconnection.ca... DNS servers ns58.domaincontrol.com [208.109.255.29] ns57.domaincontrol.com [216.69.185.29] Answer records rottweilerconnection.ca A 97.74.215.113 3600s rottweilerconnection.ca MX preference: 0 exchange: smtp.secureserver.net 3600s rottweilerconnection.ca MX preference: 10 exchange: mailstore1.secureserver.net 3600s rottweilerconnection.ca NS ns57.domaincontrol.com 3600s rottweilerconnection.ca NS ns58.domaincontrol.com 3600s rottweilerconnection.ca SOA server: ns57.domaincontrol.com email: dns@jomax.net serial: 2010012600 refresh: 28800 retry: 7200 expire: 604800 minimum ttl: 3600 3 --
When somebody tells you nothing is impossible, ask him to dribble a football. |
|
stormbowFreedom isn't FREEPremium
join:2002-07-31
Simi Valley, CA | reply to kawemt
traceroute to rottweilerconnection.ca (97.74.215.113), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 2.138 ms 2.071 ms 13.175 ms
2 99-8-140-2.lightspeed.simica.sbcglobal.net (99.8.140.2) 48.575 ms 48.598 ms 48.615 ms
3 * * *
4 * * *
5 * * *
6 12.83.38.145 (12.83.38.145) 45.703 ms 25.580 ms 12.83.38.129 (12.83.38.129) 25.472 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
That last reporting router belongs to AT&T --> /usr/local/bin/fwhois 12.83.38.129@whois.arin.net
[whois.arin.net]
#
# Query terms are ambiguous. The query is assumed to be:
# "n 12.83.38.129"
#
# Use "?" to get help.
#
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=12.83.38.129?showDetails=true&showARIN=false&ext=netref2
#
AT&T Worldnet Services ATTSVC-12-80-0-0 (NET-12-80-0-0-1) 12.80.0.0 - 12.83.255.255
AT&T Services, Inc. ATT (NET-12-0-0-0-1) 12.0.0.0 - 12.255.255.255
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
--> /usr/local/bin/fwhois "!NET-12-0-0-0-1@whois.arin.net"
[whois.arin.net]
#
# Query terms are too ambiguous. Please refine query.
#
#
|
|
kawemt
join:2012-12-12
Oshkosh, WI | So what do you guys suggest I do? I see that the error is being caused by packets not going through but if they seem to go through with other web providers. Do you think by letting AT&T know that this is happening they can fix it or is it going to be something I need to acquire a work around for?
Bullwhip, what did you do to have the packets all go through? Was that with AT&T? |
|
stormbowFreedom isn't FREEPremium
join:2002-07-31
Simi Valley, CA | said by kawemt:So what do you guys suggest I do? I see that the error is being caused by packets not going through but if they seem to go through with other web providers. Do you think by letting AT&T know that this is happening they can fix it or is it going to be something I need to acquire a work around for?
Bullwhip, what did you do to have the packets all go through? Was that with AT&T?
I don't know if they will do anything. The support person was telling the truth, it isn't "blocked" it just has no route to it. Bullwhip was on a different network when that traceroute was run. |
|
 parkutCrunch AddictPremium,MVM
join:2001-12-15
Harrison Township, MI
kudos:6
 ·AT&T U-Verse
 ·WOW Internet and..
·AT&T Midwest
| reply to kawemt
Re: u-verse routing problem rottweilerconnection.ca resolves to 97.74.215.113
fails on home u-verse. works fine from work t-1 connection
PING www.rottweilerconnection.ca (97.74.215.113) 56(84) bytes of data.
64 bytes from rottweilerconnection.ca (97.74.215.113): icmp_seq=1 ttl=47 time=76.9 ms
u-verse ping, www, traceroute all fail
Ping works to IP number above and below
PING 97.74.215.112 (97.74.215.112) 56(84) bytes of data.
64 bytes from 97.74.215.112: icmp_seq=1 ttl=46 time=90.0 ms
PING 97.74.215.114 (97.74.215.114) 56(84) bytes of data.
64 bytes from 97.74.215.114: icmp_seq=1 ttl=46 time=89.5 ms
The IP's look to belong to GoDaddy.com, LLC
I have reported via e-mail to: uversecare@att.com based on suggestion from reading of similar problems in these forums in the past . Perhaps if more people reported it, it could get resolved sooner than later?
--
Hello, my name is Bill and I'm a crunchaholic...
Proud to be hosting six Crunchenstein blades, and three Foldinator blades |
|
kawemt
join:2012-12-12
Oshkosh, WI | Thanks, I will report it as well. I found out another forum member is having the same issue so I will tell her to report it too. She said it just started a few days ago. |
|
| Not working for me here in Texas and I just got Uverse a week ago. |
|
LagzPremium
join:2000-09-03
The Rock Reviews:
·AT&T DSL Service
1 edit | reply to stormbow
Re: Blocked website said by stormbow:said by kawemt:Bullwhip, what did you do to have the packets all go through? Was that with AT&T?
I don't know if they will do anything. The support person was telling the truth, it isn't "blocked" it just has no route to it. Bullwhip was on a different network when that traceroute was run. Yes. That was done from network-tools servers to rottweilerconnection.ca
All my pings and tracert from at&t gets timed out. I figure something is going on with 12.83.72.137 or one of the routers up north. Network-tools.com can't ping or tracert 12.83.72.137. It might be miss configured or something.
--
When somebody tells you nothing is impossible, ask him to dribble a football. |
|
 MichailPremium
join:2000-08-02
Boynton Beach, FL
kudos:1 | reply to kawemt
Has it gotten resolved yet? Even on a business account it's hard/next to impossible convincing AT&T they have something miss-configured. |
|
kawemt
join:2012-12-12
Oshkosh, WI | Nope, still not resolved, they told me it had to be something on my end. I am still working on it though. |
|
