David Gursky
New Around Here
I havc a [T-Mobile supplied] femtocell (a Nokia SS2FII). [Actually, I have two -- one here at my home in VA, another at SWMBO's home in MD.]
About four months ago, the VA unit stopped connection to TMo, and the MD unit followed suit about a month ago. I worked with TMo to try and ascertain the problem, to no avail. I have now inserted a protocol analyzer between the VA unit and my home router, and it appears that the Cellspot is trying to initiate an ISAKMP session to a TMo server (serving1tep1-4sgwphi21-22.smallcell.t-mobile.com -- who comes up with these names anyhow???) but it seems to go nowhere -- the request is initiated, but there is no acknowledgement.
What is even odder is that I get different results from traceroute. On my protocol analyzer, I get this:
Tracing route to serving1tep1-4sgwphi21-22.smallcell.t-mobile.com [208.54.90.15]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms RT-AC66U_B1-D290.gursky.home [192.168.60.1]
2 1 ms 1 ms <1 ms 208.54.90.15
Trace complete.
On my primary router, I get this:
traceroute to serving1tep1-4sgwphi21-22.smallcell.t-mobile.com (208.54.90.11), 30 hops max, 38 byte packets
1 * * *
2 B3365.WASHDC-LCR-22.verizon-gni.net (100.41.136.160) 2.902 ms 4.130 ms B3365.WASHDC-LCR-21.verizon-gni.net (100.41.136.158) 4.417 ms
3 * * *
4 0.ae1.BR1.IAD8.ALTER.NET (140.222.239.77) 3.438 ms 3.528 ms 4.020 ms
5 xe-2-1-0.er2.iad10.us.zip.zayo.com (64.125.13.173) 2.993 ms 3.862 ms 3.075 ms
6 ae1.cs4.iad93.us.zip.zayo.com (64.125.25.164) 10.367 ms * *
7 ae9.cs2.dca2.us.eth.zayo.com (64.125.25.100) 21.760 ms 8.174 ms 8.618 ms
8 ae5.mpr4.phl2.us.zip.zayo.com (64.125.30.57) 8.967 ms 9.473 ms 9.864 ms
9 ae4.mpr3.phl2.us.zip.zayo.com (64.125.21.73) 9.612 ms 8.353 ms 9.118 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 208.54.90.11 (208.54.90.11) 20.013 ms 26.279 ms 9.955 ms
[Both 90.11 and 90.15 are IP addresses to serving1tep1, that's not what's odd, it is the VERY different results.]
Thoughts? Help!
About four months ago, the VA unit stopped connection to TMo, and the MD unit followed suit about a month ago. I worked with TMo to try and ascertain the problem, to no avail. I have now inserted a protocol analyzer between the VA unit and my home router, and it appears that the Cellspot is trying to initiate an ISAKMP session to a TMo server (serving1tep1-4sgwphi21-22.smallcell.t-mobile.com -- who comes up with these names anyhow???) but it seems to go nowhere -- the request is initiated, but there is no acknowledgement.
What is even odder is that I get different results from traceroute. On my protocol analyzer, I get this:
Tracing route to serving1tep1-4sgwphi21-22.smallcell.t-mobile.com [208.54.90.15]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms RT-AC66U_B1-D290.gursky.home [192.168.60.1]
2 1 ms 1 ms <1 ms 208.54.90.15
Trace complete.
On my primary router, I get this:
traceroute to serving1tep1-4sgwphi21-22.smallcell.t-mobile.com (208.54.90.11), 30 hops max, 38 byte packets
1 * * *
2 B3365.WASHDC-LCR-22.verizon-gni.net (100.41.136.160) 2.902 ms 4.130 ms B3365.WASHDC-LCR-21.verizon-gni.net (100.41.136.158) 4.417 ms
3 * * *
4 0.ae1.BR1.IAD8.ALTER.NET (140.222.239.77) 3.438 ms 3.528 ms 4.020 ms
5 xe-2-1-0.er2.iad10.us.zip.zayo.com (64.125.13.173) 2.993 ms 3.862 ms 3.075 ms
6 ae1.cs4.iad93.us.zip.zayo.com (64.125.25.164) 10.367 ms * *
7 ae9.cs2.dca2.us.eth.zayo.com (64.125.25.100) 21.760 ms 8.174 ms 8.618 ms
8 ae5.mpr4.phl2.us.zip.zayo.com (64.125.30.57) 8.967 ms 9.473 ms 9.864 ms
9 ae4.mpr3.phl2.us.zip.zayo.com (64.125.21.73) 9.612 ms 8.353 ms 9.118 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 208.54.90.11 (208.54.90.11) 20.013 ms 26.279 ms 9.955 ms
[Both 90.11 and 90.15 are IP addresses to serving1tep1, that's not what's odd, it is the VERY different results.]
Thoughts? Help!
