US Telco Support > AT&T > AT&T Midwest > [help] Can't access ONE web page, ATT says no issue.

[help] Can't access ONE web page, ATT says no issue.

quote:

---

Tracing route to zagg.com [204.246.134.167]
over a maximum of 30 hops:

1 6 ms 6 ms 42 ms adsl-99-152-***-***.dsl.emhril.sbcglobal.net [99.152.***.***]
2 33 ms 8 ms 6 ms adsl-99-152-***-***.dsl.emhril.sbcglobal.net [99.152.***.***]
3 6 ms 26 ms 9 ms dist1-vlan60.emhril.ameritech.net [68.22.***.***]
4 6 ms 25 ms 7 ms bb1-g0-0.emhril.ameritech.net [151.164.43.82]
5 11 ms 7 ms 6 ms 151.164.94.41
6 7 ms 9 ms 7 ms Te-3-2.Chicago1.Level3.net [4.68.110.197]
7 17 ms * 19 ms ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]
8 18 ms 22 ms 7 ms ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
9 * 48 ms 54 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
10 40 ms 52 ms * ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
11 55 ms 55 ms 59 ms ae-5-5.car2.SaltLakeCity1.Level3.net [4.69.133.125]
12 56 ms 55 ms 58 ms VIAWEST-INT.car2.SaltLakeCity1.Level3.net [64.158.68.10]
13 78 ms 60 ms 75 ms vi-011.aggm02.slc04.viawest.net [206.71.65.50]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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 have no problems accessing them from here. And my connection also goes through elmhurst.

reply to NGW1031982
Try posting this in the Direct forum. I have a feeling they need to do a rip and rebuild on your redback profile.

I ran into this issue 2 yrs ago at a customers house and that's what fixed the issue.

reply to NGW1031982
This might be due to an out-of-date BOGON filter at the zagg.com server. They could still have your subnet IP blocked even though AT&T notified them long ago that the 99.152.xxx.xxx subnet is now valid. Frankly there isn't anything that AT&T can do if the zagg.com server owner won't update BOGON filters in a timely manner.

If there are other IP blocks available on your aggregation router (other than 99.xxx.xxx.xxx subnets), you might be able disconnect your PPPoE connection for a few seconds and hope for a new IP in a different block to be assign when you re-connect. If you manage to win at this "IP roulette" game, you should be able to connect to the server.

reply to DSL12steps
DSL12steps : *removed* Found the form.

d_l : Is there any way on my end to verify that? I got a 99.142 IP, and I remember having that before and having access. That used to be all I got when I connected.

Also, the tech support was outsourced. Better managed, but still. Would forcing a technician to call me work? I could raise the MTU to 1500 and cause a nasty issue. I did that once to see what would happen, changed it back in less then 5 minutes. They called within 10.
I would prefer to try anything else before posting in the direct form, as per the requirements.

reply to NGW1031982
There isn't any way for you to verify that a BOGON filter is the cause of the access problem. Also the filter (if it is the cause) may only be restricting certain subnets within the 99.xxx.xxx.xxx subnet.

Well, I got in contact with Zagg, and there is nothing wrong on there end. Apparently they checked their firewall and blocked addresses.

reply to NGW1031982
Have you tried useing a dialup connection to get to zagg?

I think d_l is on point, that web site will not answer http and tracert requests with a 99.142 ip address

I don't like that ip range whenever a user I know has userid/password trouble they get a 99.142 ip address

I got a 99.152 IP now, and in the routers test is says no response from the host instead of a time out. I guess I will have to get an IP lower then 99.140. This could be fun...

More than likely your dsl connection will only issue 99 ip's
Use the free dialup access there's a good chance you'll get a much lower ip number

The 99.142 tracert times out after:
12 91ms 92ms 94ms vi-011.aggm02.slc04.viawest.net [206.71.65.50]

reply to NGW1031982
I'm on a 99.180.x block and I can't get to the website either.

 3  dist2-vlan60.emhril.ameritech.net (68.22.72.131)  9.327 ms  8.696 ms  9.248 ms
 4  bb2-g9-0.emhril.sbcglobal.net (151.164.94.164)  9.260 ms  8.950 ms  9.720 ms
 5  ex2-p5-0.eqchil.sbcglobal.net (151.164.42.139)  9.985 ms  9.650 ms  12.676 ms
 6  Te-3-2.Chicago1.Level3.net (4.68.110.197)  9.598 ms  11.338 ms  9.230 ms
 7  ae-31-51.ebr1.Chicago1.Level3.net (4.68.101.30)  19.437 ms  14.360 ms  19.057 ms
 8  ae-6.ebr1.Chicago2.Level3.net (4.69.140.190)  126.008 ms  126.911 ms  14.180 ms
 9  ae-3.ebr2.Denver1.Level3.net (4.69.132.61)  164.947 ms  67.404 ms  176.154 ms
10  ae-1-100.ebr1.Denver1.Level3.net (4.69.132.37)  177.564 ms  163.462 ms  49.835 ms
11  ae-5-5.car2.SaltLakeCity1.Level3.net (4.69.133.125)  216.345 ms  183.955 ms  199.133 ms
12  VIAWEST-INT.car2.SaltLakeCity1.Level3.net (64.158.68.10)  58.595 ms  59.271 ms  58.297 ms
13  vi-010.aggm02.slc04.viawest.net (206.71.65.19)  58.805 ms  61.338 ms  58.511 ms
14  * *^C
 

Well, I was able to talk to a tech person at ZAGG via E-Mail, I am relaying this information to him as well as how apparently there were some issues with other BOGON filters not likening 99.xxx.xxx.xxx IP addresses.

I will update here as things go on.

reply to NGW1031982
FWIW
A) I am having the same problem now.
B) TRACERT stops at the same point.
C) My IP is in the form 99.135.* *

Well, I have had a number of IP addresses, but they always start with 99. It seems that anything with 99 as the first set is blocked, and I would guess the earliest I would get a response or that it would be looked into is Monday. So unless proven otherwise, I will assume addresses starting with 99 are ignored and the BOGON list needs to be updated.

Also, I do not have a dial-up modem, so I can not test that way.

...let me test for you.

Current connection in EMHRIL (same Ip as above):

  3     9 ms     8 ms     9 ms  rback1-g1-1.emhril.sbcglobal.net [68.250.251.1]
  4     8 ms     8 ms     9 ms  bb1-g9-0.emhril.sbcglobal.net [151.164.94.162]
  5     9 ms    20 ms     9 ms  ex2-p5-0.eqchil.sbcglobal.net [151.164.42.139]
  6    10 ms     9 ms     9 ms  Te-3-2.Chicago1.Level3.net [4.68.110.197]
  7    18 ms    18 ms    17 ms  ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]
  8    10 ms    10 ms     9 ms  ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
  9    42 ms    52 ms    54 ms  ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
 10    49 ms    54 ms    53 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
 11    58 ms    58 ms    58 ms  ae-5-5.car2.SaltLakeCity1.Level3.net [4.69.133.125]
 12    58 ms    57 ms    58 ms  VIAWEST-INT.car2.SaltLakeCity1.Level3.net [64.158.68.10]
 13    58 ms    58 ms    57 ms  vi-010.aggm02.slc04.viawest.net [206.71.65.19]
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
 

Tracing route to zagg.com [204.246.134.167]
over a maximum of 30 hops:
 
  1    29 ms    30 ms    29 ms  adsl-67-67-11-254.dsl.okcyok.swbell.net [67.67.11.254]
  2    30 ms    30 ms    30 ms  dist1-vlan60.okcyok.sbcglobal.net [151.164.23.162]
  3    31 ms    30 ms    30 ms  bb1-g3-0-0.okcyok.sbcglobal.net [151.164.38.178]
  4    49 ms    49 ms    49 ms  151.164.171.238
  5    49 ms    50 ms    49 ms  Te-3-2.Chicago1.Level3.net [4.68.110.197]
  6    51 ms    53 ms    54 ms  ae-31-55.ebr1.Chicago1.Level3.net [4.68.101.158]
  7    50 ms    50 ms    50 ms  ae-6.ebr1.Chicago2.Level3.net [4.69.140.190]
  8    66 ms    72 ms    72 ms  ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
  9    64 ms    68 ms    72 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
 10    86 ms    85 ms    85 ms  ae-5-5.car2.SaltLakeCity1.Level3.net [4.69.133.125]
 11    84 ms    85 ms    85 ms  VIAWEST-INT.car2.SaltLakeCity1.Level3.net [64.158.68.10
 12    85 ms    86 ms    85 ms  vi-011.aggm01.slc04.viawest.net [206.71.65.51]
 13    85 ms    85 ms    86 ms  204.246.134.167
 
Trace complete.
 

reply to NGW1031982
removed would be a good resource here. I sent him an IM with the link to this thread.

He's good with this type of stuff. Was a good contributor when we got the 75.x.x.x addresses as well as the 77.x.x.x as well. Even created a document on what to say and how to say it.

I recommend the removed manuever
--
If you have a topic in the direct forum please reply to it or a post of mine, I get a notification when you do this.
Koetting Ford, Granite City, illinois... YOU'RE FIRED!!

reply to NGW1031982
I've sent an email to the owner of this netblock - hopefully they'll be able to take care of this since the problem appears to be on their end. I'll follow up with you guys once I get a response.
--
irc.removed.us - #dslr | DSLR Phishtracker | Email: removed@dslr.net

reply to NGW1031982
So what is the removed manuever out of curiosity?

Anyone haveing an issue accessing the site, try it now. I just went there and had NO issue!