dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1086
share rss forum feed


Shield

@sbcglobal.net

Blocked website

For some reason i cant access my bands website shieldofsalvation.com through att uverse or dsl, yet I can access it on windstream and time warner. Could someone else that is on att try to access my bands site to see if it works for them?



CarbonCopy

join:2003-01-29
Fresno, CA

Looks like one of AT&T's Ameritech routers is confused.

 Tracing route to shieldofsalvation.com [207.45.186.90] 
over a maximum of 30 hops: 
 
  1    <1 ms    <1 ms    <1 ms  172.16.1.5  
  2     1 ms     1 ms     1 ms  192.168.1.254  
  3    31 ms    21 ms    37 ms  108-227-90-3.lightspeed.frsnca.sbcglobal.net [108.227.90.3]  
  4    24 ms    22 ms    23 ms  75.56.90.6  
  5     *       22 ms    21 ms  75.56.90.17  
  6    25 ms    22 ms    24 ms  12.83.71.141  
  7  ded3-g4-3-0.sfldmi.ameritech.net [151.164.40.106]  reports: Destination host unreachable. 
 
Trace complete.
 

Level 3 has no problem getting there.
 Traceroute results from San Francisco, CA
 to 207.45.186.90(unix.securenet-server.net)
  1 ae-2-4.bar1.SanFrancisco1.Level3.net (4.69.133.150) 4 msec 0 msec 0 msec
  2 ae-0-11.bar2.SanFrancisco1.Level3.net (4.69.140.146) 0 msec 0 msec 0 msec
  3 ae-6-6.ebr2.SanJose1.Level3.net (4.69.140.154) 56 msec 56 msec 56 msec
  4 ae-3-3.ebr1.Denver1.Level3.net (4.69.132.58) 60 msec 56 msec 56 msec
  5 ae-1-100.ebr2.Denver1.Level3.net (4.69.151.182) 56 msec 56 msec 56 msec
  6 ae-3-3.ebr1.Chicago2.Level3.net (4.69.132.62) 56 msec 56 msec 56 msec
  7 ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189) 64 msec 56 msec 56 msec
  8 ae-1-100.ebr2.Chicago1.Level3.net (4.69.151.178) 56 msec 56 msec
    ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193) 56 msec
  9 ae-8-8.car1.Detroit1.Level3.net (4.69.133.241) 76 msec 56 msec *
 10 I123.car1.Detroit1.Level3.net (4.53.76.158) 56 msec 60 msec 56 msec
 11 238.223.171.68.securenet-server.net (68.171.223.238) [AS22878] 56 msec 56 msec 60 msec
 12 unix.securenet-server.net (207.45.186.90) [AS22878] 56 msec 56 msec 56 msec
 


parkut
Crunch Addict
Premium,MVM
join:2001-12-15
Harrison Township, MI
kudos:7
Reviews:
·AT&T U-Verse
·WOW Internet and..
reply to Shield

the website at »www.shieldofsalvation.com

resides on IP 207.45.186.90 and is unreachable on the ATT
network. Yet it is on other networks, including Wide Open West
and my business T-1 circuit.

Ping and traceroute fail, but work perfectly on the
IP number above and below, i.e., 207.45.186.89 and
207.45.186.91

Based on previous similar situations, I believe AT&T is blocking
the IP number.
--
Hello, my name is Bill and I'm a crunchaholic...


Proud to be hosting six Crunchenstein blades, and three Foldinator blades



Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5
reply to Shield

I can help you resolve this. Can you register here and PM me so I can explain what step you need to take next. The owner of that site needs to get in touch at AT&T to resolve this and I can tell him how to.
--
My Blog. Because I desperately need the acknowledgement of others.

The Judd Family site!



cpt panda

@sbcglobal.net

unfortunately for you it is because the 172.x.x.x ip address is commonly reserved for devices, I believe. The cause of this happening is the severe shortage of ipv4 addresses.

The fix? Nothing. Maybe factory reset your modem and cross your fingers you might get a new IP address.


Secyurityet
Premium
join:2012-01-07
untied state
reply to Shield

Looks like it's fixed.



mackey
Premium
join:2007-08-20
kudos:8
reply to cpt panda

said by cpt panda :

unfortunately for you it is because the 172.x.x.x ip address is commonly reserved for devices, I believe. The cause of this happening is the severe shortage of ipv4 addresses.

The fix? Nothing. Maybe factory reset your modem and cross your fingers you might get a new IP address.

Dude, you are totally off. First, only 172.16.0.0/12 is reserved, 172.0.0.0-172.15.255.255 and 172.32.0.0-172.255.255.255 are in fact valid public IP addresses.

More importantly however, 172.16.x.x is no different then a 192.168.x.x address and is perfectly acceptable to use on an internal network. Most people use routers which use private addresses for the internal network (such as 192.168.1.x or 172.16.1.x) and NAT them when talking to the internet. When doing a traceroute, the device is going to reply with the internal address as it's "closer" to the requesting computer.

/M


NetFixer
Snarl For The Camera Please
Premium
join:2004-06-24
The Boro
Reviews:
·Cingular Wireless
·Comcast Business..
·Vonage
·Comcast

I can get to that site from both my AT&T backup connection and my Comcast connection, but the Comcast connection is definitely cleaner.

C:\>use-att.cmd
 
Pinging 192.168.1.254 with 32 bytes of data:
 
Reply from 192.168.1.254: bytes=32 time=85ms TTL=62
 
Ping statistics for 192.168.1.254:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 85ms, Maximum = 85ms, Average = 85ms
 
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 shieldofsalvation.com
 
Tracing route to shieldofsalvation.com [207.45.186.90]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  ps1.dcs-net [192.168.9.9]
  2     3 ms     3 ms     4 ms  ap1-dcs-net [192.168.8.254]
  3    13 ms    10 ms    10 ms  192.168.1.254
  4    38 ms    31 ms    29 ms  99-71-148-3.lightspeed.nsvltn.sbcglobal.net [99.71.148.3]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    51 ms    35 ms    37 ms  70.159.210.156
  9    40 ms    41 ms    46 ms  12.81.32.118
 10    41 ms    33 ms    39 ms  12.81.32.111
 11    42 ms    42 ms    37 ms  74.175.192.138
 12    49 ms    41 ms    52 ms  cr1.nsvtn.ip.att.net [12.122.148.14]
 13    50 ms    50 ms    50 ms  cr2.attga.ip.att.net [12.122.28.105]
 14   164 ms    88 ms    49 ms  12.122.140.245
 15   224 ms   219 ms     *     te2-5.ccr01.atl02.atlas.cogentco.com [154.54.10.69]
 16    54 ms    63 ms    61 ms  te0-4-0-7.ccr21.atl01.atlas.cogentco.com [154.54.88.201]
 17    61 ms    55 ms    64 ms  te4-3.ccr01.ind01.atlas.cogentco.com [154.54.85.66]
 18    57 ms    58 ms    63 ms  te3-7.ccr01.sbn01.atlas.cogentco.com [154.54.3.29]
 19    65 ms    73 ms    58 ms  te4-3.ccr01.tol01.atlas.cogentco.com [154.54.7.153]
 20    77 ms    65 ms    73 ms  te4-3.ccr01.dtw04.atlas.cogentco.com [154.54.5.153]
 21    75 ms    66 ms    63 ms  38.122.60.66
 22    60 ms    60 ms    63 ms  unix.securenet-server.net [207.45.186.90]
 
Trace complete.
 
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 shieldofsalvation.com
 
Tracing route to shieldofsalvation.com [207.45.186.90]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  gw1.dcs-net [192.168.9.254]
  2    36 ms    20 ms    31 ms  107.3.232.1
  3     9 ms     9 ms     8 ms  xe-4-0-0-32767-sur02.murfreesboro.tn.nash.comcast.net [68.85.50.129]
  4    11 ms    11 ms    14 ms  xe-0-0-8-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.53]
  5    24 ms    21 ms    20 ms  pos-5-6-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.89]
  6    33 ms    31 ms    31 ms  he-2-14-0-0-cr01.chicago.il.ibone.comcast.net [68.86.87.113]
  7    31 ms    36 ms    35 ms  he-1-14-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.88.22]
  8    30 ms    30 ms    30 ms  pos-0-13-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.250]
  9    38 ms    39 ms    38 ms  cr-1.sfld-mi.123.net [66.208.233.62]
 10    38 ms    38 ms    38 ms  238.223.171.68.securenet-server.net [68.171.223.238]
 11    38 ms    39 ms    36 ms  unix.securenet-server.net [207.45.186.90]
 
Trace complete.
 

--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.

When governments fear people, there is liberty. When the people fear the government, there is tyranny.


Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5
reply to Shield

Guys calm down it was just a security issue that needed to be addressed between AT&T and the site owner.



CarbonCopy

join:2003-01-29
Fresno, CA

said by Dennis:

Guys calm down it was just a security issue that needed to be addressed between AT&T and the site owner.

Well, OK, but it looks like the site owner addressed it by using Cogentco's network instead of AT&T's. Compare this traceroute to the first one in my post above. They are different after hop 6.

Tracing route to shieldofsalvation.com [207.45.186.90]
over a maximum of 30 hops:
 
  1    <1 ms    <1 ms    <1 ms  172.16.1.5 
  2     1 ms    <1 ms    <1 ms  192.168.1.254 
  3    30 ms    22 ms    22 ms  108-227-90-3.lightspeed.frsnca.sbcglobal.net [108.227.90.3] 
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    25 ms    23 ms    23 ms  12.83.71.141 
  7    31 ms    41 ms    40 ms  ggr6.wswdc.ip.att.net [12.122.86.89] 
  8    31 ms    31 ms    30 ms  be3000.ccr21.sjc03.atlas.cogentco.com [154.54.11.45] 
  9    31 ms    31 ms    31 ms  te0-7-0-0.ccr22.sjc03.atlas.cogentco.com [154.54.86.106] 
 10    32 ms    31 ms    31 ms  te0-1-0-4.ccr22.sjc01.atlas.cogentco.com [154.54.86.101] 
 11    33 ms    33 ms    32 ms  te0-3-0-5.mpd22.sfo01.atlas.cogentco.com [154.54.86.189] 
 12    77 ms    76 ms    76 ms  te0-4-0-3.mpd22.mci01.atlas.cogentco.com [154.54.45.85] 
 13    81 ms    80 ms    80 ms  te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54.30.177] 
 14    89 ms    88 ms    88 ms  te4-2.ccr01.dtw04.atlas.cogentco.com [154.54.27.158] 
 15    89 ms     *      101 ms  38.122.60.66 
 16    89 ms    87 ms    88 ms  unix.securenet-server.net [207.45.186.90] 
 
Trace complete.
 


Dennis
Premium,Mod
join:2001-01-26
Algonquin, IL
kudos:5

said by CarbonCopy:

said by Dennis:

Guys calm down it was just a security issue that needed to be addressed between AT&T and the site owner.

Well, OK, but it looks like the site owner addressed it by using Cogentco's network instead of AT&T's. Compare this traceroute to the first one in my post above. They are different after hop 6.

Well...I guess that is one way to fix it. Now we'll never know I guess why they were blocked in the end.
--
My Blog. Because I desperately need the acknowledgement of others.

The Judd Family site!