I live in Los Angeles, and I'm experiencing very odd connect problems. I have both a Cingular Laptop connect card, and a Cingular 8525. Mostly i'm on edge, sometimes 3g/hsdpa. From anywhere in the world i can ping 66.102.136.161 except on my cingular network. Sometimes it works and most of the time it doesn't. It seems I can't access anything on the 66.102.128.0/20.
From what i can tell of traceroutes, its not making it past cingular's filters or firewall.
Tracing route to 66.102.136.161 over a maximum of 30 hops: 1 332 ms 238 ms 239 ms 172.26.248.2 2 819 ms 340 ms 617 ms 172.26.248.2 3 * * * Request timed out. Anyone work for cingular or WDSPCo? Other networks to the same provider work just fine. I know its not filtering on the destination network. Anyone else have the same problem? Thanks Andrew
On 4/27/07, andrew matthews <exstatica@gmail.com> wrote:
I live in Los Angeles, and I'm experiencing very odd connect problems.
I have both a Cingular Laptop connect card, and a Cingular 8525. Mostly i'm on edge, sometimes 3g/hsdpa. From anywhere in the world i can ping 66.102.136.161 except on my cingular network. Sometimes it works and most of the time it doesn't. It seems I can't access anything on the 66.102.128.0/20.
From what i can tell of traceroutes, its not making it past cingular's filters or firewall.
Is that the only IP you can't ping? Or can you not ping/traceroute in general? I myself use T-Mobile's EDGE service in Chicago, and can ping but cannot traceroute out in any functional way. -brandon
participants (2)
-
andrew matthews -
Brandon Galbraith