Recent content by jolt_man

  1. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    What are the APNs you've got setup on your phone? What WiFi router are you using? Are you using custom firmware on your router? Have you tried the method I mentioned in a previous post? Have you installed Android Terminal Emulator and tried pinging your MMS APNs from the phone (try pinging...
  2. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    Glad I was able to help at least one person! Jensen: Were you using the same APNs? What about pinging all DNS names from those APNs?
  3. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    This is the link I've followed for the APNs specifically for my wife's GS4 GE. It seems to work for her. I'm not sure what is causing the issue for you. My issue was that I couldn't even resolve proxy.mobile.att.net. I think that what's happening is that because there is no route to the host...
  4. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    You won't receive a ping reply from that address on your computer. The public internet cannot route those private internet addresses. The app I use on the phone is called Android Terminal Emulator. If your computer can successfully resolve that address then your phone on the same network via...
  5. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    My issue was that when I was connected behind my pfSense router and ran the ping, it wouldn't resolve at all. Once I tried the address from my work machine, proxy.mobile.att.net would resolve (172.26.39.1) but remain un-pingable. This is to be expected as the address is in a private address...
  6. J

    MMS's won't send when wifi connected (GPE s4... ATT S4 works fine)

    I had been having the same issue with my wife's Google Edition Galaxy S4 behind a pfSense 2.0.3 and 2.1 firewall. Here is my thread (from xda) on how I fixed it: SOLVED! I have finally solved the issue. I'm so happy it's fixed. For those that happen upon this thread, here's what I did...