North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Cingular Data Network Problems
- From: andrew matthews
- Date: Fri Apr 27 02:27:45 2007
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MKclzRIyCOk00WagxokMnOcIFuZhc14Kr5xzlkRGxBAjBy8EWwn7nOVfZYOEYwxU6M2CHR4mmRf9njnKHoo8CqYNTczFVDZ8Ijhk1S4nPAe/p3Jt5npH7/6JKWKo5hHdse4NByQHM/FvZ0Y0IqATuhKHOaKmEF7BSjyqIaFp5xk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KRR+Qvl0B1R1wdCFEsIjwsS96Gy37tBg0nV3d/1Yek1OB7VbKw5mSBoneV5CW1movsFkeLY01knqmSy1/YShlLDYcyfqWRzmy2i/xLccLZ4pe1QPs8uqztt35yDgBHtirl5lNlSX2j6+/H/3XSQnbItXSDNA/oOu7wkyCoCGW0c=
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
| 
