Satellite > WildBlue Satellite > [Exede] ATT 3G M-Cell failure on Exede

[Exede] ATT 3G M-Cell failure on Exede

"If that doesn't work then you may have to setup port forwarding and assign a permanent IP to your MicroCell via the MAC address. That's what I had to do with my AEBS. This doesn't work for everyone but in my case it did. Our MicroCell has been rock solid since even with power outages and updates."

»forums.att.com/t5/3G-MicroCell/M···/2773867

The M-Cell seems to need ports 500 and 4500. I can certainly give M-Cell a static address like 192.168.0.200 and forward those two ports from my router to the M-Cell. However the Exede modem may not be forwarding those ports to my router. In fact the M-cell no longer works even if plugged directly into the modem. I have no access to the modem's port settings. Also its hard to see how this could help if indeed ATT is right in saying that Exede is now blocking acccess to ATT's M-Cell IP address 12.230.209.134. Maybe I need an outside proxy - divert packets going to 12.230.209.134 to proxy and the proxy then forwards to 12.230.209.134.

I get request timed out for 12.230209.134 from both my Exede and ATT Uverse Internet connections.

I've not yet tried hooking up my ATT Microcell (really a femtocell) to the Exede connection but may play with that later today.

It is certainly possible that an IP wouldn't accept pings, but if it is supposed to use both 500 and 4500:

telnet 12.230.209.134 500
Connecting To 12.230.209.134...Could not open connection to the host, on port 500: Connect failed

telnet 12.230.209.134 4500
Connecting To 12.230.209.134...Could not open connection to the host, on port 4500: Connect failed

Both attempts from an AT&T DSL connection
--
Author of hnFAP-Alert, PC-OPI and DSSatTool

reply to mcbryan
Install Telnet Client: Applies To: Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Vista

»technet.microsoft.com/en-us/libr···%29.aspx

reply to mcbryan
MicroCell Troubleshooting Guide with Port Forwarding

»forums.att.com/t5/3G-MicroCell/M···/3304923

Ports to forward are:

UDP 123 public and private

UDP 4500 public and private

UDP 500 public and private

TCP 443 public and private

reply to dbirdman

Nothing weird here (also Win7), just another failure to connect:

telnet 12.230.209.134 443
Connecting To 12.230.209.134...Could not open connection to the host, on port 443: Connect failed
--
Author of hnFAP-Alert, PC-OPI and DSSatTool

My Microcell was working happily on my ATT Uverse connection. Unplugged it and connected to my Exede connection and no joy.

It did not connect after at least 20 minutes of waiting.

Opened up the various ports suggested in one of the earlier posts above but no change. Note that I don't have anything special opened up on the router that handles my ATT Uverse Internet connection and the Microcell connected just fine.

Moved Microcell back to the ATT Uverse connection once I could see that it didn't appear to be connecting on Exede and within a few minutes back on Uverse the Microcell was happily working again.

I'll send a note off regarding this.

reply to mcbryan
Using Wildblue service (no Exede):

Ping Plotter (uses TTL timeout in UDP packets?)

Target Name: N/A
IP: 12.230.209.134
Date/Time: 2/24/2013 6:27:56 PM MST

 1 1401 ms  [10.18.0.1]
 2 1401 ms  [10.244.20.1]
 3 2116 ms  [10.244.30.24]
 4 1999 ms  [10.244.30.1]
 5 2069 ms  [10.244.100.2]
 6 2023 ms  [10.244.110.2]
 7 1992 ms  [12.125.98.197]
 8 1961 ms  cr83.la2ca.ip.att.net [12.122.128.186]
 9 1930 ms  gar26.la2ca.ip.att.net [12.122.128.237]
10   *       [-]

  1  1433 ms  1343 ms  1544 ms  10.18.0.1
  2  1340 ms  1328 ms  1446 ms  10.244.20.1
  3  1429 ms  1428 ms  1563 ms  10.244.30.24
  4  1345 ms  1820 ms  1326 ms  10.244.30.1
  5  1702 ms  2080 ms  3275 ms  10.244.100.2
  6   787 ms  1005 ms  1523 ms  10.244.110.2
  7  1459 ms  1523 ms  1517 ms  12.125.98.197
  8  1981 ms  1642 ms  1452 ms  cr83.la2ca.ip.att.net [12.122.128.186]
  9  2225 ms  1428 ms  1467 ms  gar26.la2ca.ip.att.net [12.122.128.237]
 10     *        *        *     Request timed out.

reply to mcbryan
Just an FYI from a non Exede customer, I cannot ping it either:

Pinging 12.230.209.134 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

I am on Clearwire service

reply to dbirdman

reply to DrStrangLov
Below is detailed info from ATT as to what is required for the M-Cell (ignore Overview). The correct IP address is femtocell.wireless.att.com which starts with 12.230 but might not be exactly what the tech gave me yesterday. I'm guessing that the last firmware upgrade for the Exede modem affected one of the items below. I took my M-Cell to a non-Exede ISP today and it worked fine.

Overview 

If the AT&T 3G MicroCell is not working after connected to the router/gateway, first try the basic troubleshooting steps contained in the User Guide. If the 3G MicroCell still will not connect to the AT&T network (as indicated by a continuous blinking 3G light), then use the following instructions to check the router settings and change them, as needed. Please contact the router manufacturer or the ISP provider to obtain assistance with configuring the router settings.

Normally, just plugging the 3G MicroCell into the router/gateway is all that is required. However, sometimes router/gateway settings have been changed or the 3G MicroCell will not connect properly. This section will show how to change the settings for some popular modems/routers to enable the 3G MicroCell to connect successfully. 
 
Procedure 
NOTE: Please be advised that the router manufacture or the ISP provider will not provide support for AT&T 3G MicroCell, but they can assist with configuring the router settings.

DHCP is on
Data is not restricted from passing through ports 4500 and 500 (AKA Port Blocking).
MTU size is set to 1492
MAC address filtering is either turned off or allowing the MAC address of the AT&T 3G MicroCell
IPSec Pass-Through is Enabled
Block Fragmented Packets is Disabled
If using multiple routers, the 3G MicoCell must be connected to the first router connected to the broadband modem
If the 3G MicroCell is connected to a router that is connected to a modem and both the router and the modem have NAT (Network Address Translation) enabled, disable NAT either in the router or the modem.
Ensure the modem / router is using the latest software (firmware). Please see the manufacturer's documentation.
TCP/UDP Ports
NOTE: All ports listed need to be configured for inbound and outbound connections.
123/UDP: NTP timing (NTP traffic)
443/TCP: Https over TLS/SSL for provisioning and management traffic
4500/UDP: IPSec NAT Traversal (for all signaling, data, voice traffic)
500/UDP: IPSec Phase 1 prior to NAT detection (after NAT detection, 4500/UDP is used)
4500/UDP: After NAT detection, 4500/UDP is used

Internal Only

Additional Troubleshooting

1. Ping or perform an NSLookup on femtocell.wireless.att.com. If the address does not resolve to 12.230.x.x, manually map the name to the IP address returned or change to an alternate DNS server that includes the entry.
2. Temporarily Disable Stateful Packet Inspection (SPI). If this resolves the issue, re-enable SPI and contact your router / firewall manufacturer for assistance troubleshooting the conflict.

NOTE:

Related Links

For information on Routers/Modems that require additional configuration to work with the AT&T 3G MicroCell, see the AT&T 3G MicroCell Advanced Troubleshooting Guide.
AT&T 3G MicroCell settings for TimeWarner Ubee / Ambit modem router
AT&T 3G MicroCell settings for Qwest Q1000 Actiontec modem router
AT&T 3G MicroCell settings for Linksys router
AT&T 3G MicroCell settings for D-Link router
AT&T 3G MicroCell settings for Netgear router
AT&T 3G MicroCell settings for Westell DSL modem

Reply from 12.89.7.246: Destination net unreachable.
Request timed out.
Reply from 12.89.7.246: Destination net unreachable.
Reply from 12.89.7.246: Destination net unreachable.
 
Ping statistics for 12.230.208.41:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
 

reply to mcbryan
I did a lookup via Dallas and only received one IP address back:

IP address: 12.230.209.130
Host name: femtocell.wireless.att.com

And it pings out:

Ping 12.230.209.130
Timed out
Timed out
Timed out
Timed out
Timed out

reply to DrStrangLov
I did manage to get in to 12.89.7.246 on port 443:
telnet 12.89.7.246 443
Trying 12.89.7.246...
Connected to 12.89.7.246.
Escape character is '^]'.
And this is through my Exede modem.
However attempts to get to ports 123, 500, 4500, all fail (from behind my Exede modem).

C:\>ping 12.230.208.41
 
Pinging 12.230.208.41 with 32 bytes of data:
Reply from 12.89.7.246: Destination net unreachable.
Request timed out.
Reply from 12.89.7.246: Destination net unreachable.
Request timed out.
 
Ping statistics for 12.230.208.41:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
 

While traceroute -p 123 12.89.7.246 fails from Exede it succeeds from comcast. This suggests that the Exede modem is possibly blocking port 123 (and may not have been a week ago).