Forum Discussion
NAT/forwarding issues while gaming/streaming
Hey guys, I'm new here... I just got my gateway in yesterday... I must say, I'm highly disappointed and I only wish I researched this further before I ordered it...I've already done multiple searches on this topic, so I'm not gonna ask the question I've been wanting to ask which was: "Why isn't my connection open NAT?", or "Why can't I port forward?". I've pretty much answered all of those questions myself by simply searching. I have taken it upon myself to call T-mobile's tech support anyways in the event that somehow a miracle is sent my way....
Fortunately for me, a very kind gentleman by the name of Alex, employee number 786457, assured me that they will be fixing the problem within a 48 hour period. I was told there will be some Beta software sent to my unit "possibly". And yes, that was the word used... Not sure how far I can believe that, seeing as how a lot of you are having issues. But anyway, this is my journey. I will post some updates here n there to let y'all know the outcome. Worst case scenario this causes me to vacate the community & the service entirely. Because this is probably one of the largest handicaps any network can have, it's almost like having parental control without it actually being implemented. Stay tuned folks, I'll let you know what happens.
Hopefully this "beta" program isn't bullcucky.
A "specific question" was answered. And that's how to (paraphrasing here) work around the problem. If you honestly think that you will find a "fix" for a cellular data connection not giving you a static IPv4 connection... Then I don't know what to tell you. In my honest opinion, workarounds are the only absolute thing you've got right now. Go call the FCC and tell them how butthurt you are.
Actually, it does not answer the specific questions being asked.
What goes in in that video is still a workaround.
It is not a native fix to the problem.
As in a firmware update that in and of itself solves the problem end to end.
djb14336 wrote:
Probably getting "spammed" because very specific questions were not getting answered.
The true problem has always been tied to unsolicited inbound traffic properly getting through the perimeter network layers... even with the local router set to open/forward inbound packets, those packets were still getting filtered/blocked further up the chain. Basically, it is making the consoles think you have a different NAT type than you actually have. When it comes to truly unsolicited inbound traffic (not coming back in from a previous outbound communication), it was still getting blocked at a higher level. All of this was confirmed back on the Askey modems... the ones that gave us local control over both DMZ and port traversal.
The above video literally just answered every question on this thread.
So your response is basically null and void.
On second thought, I'm glad this video is up now. So, anyone past this point in the discussion that is complaining has nobody to blame but themselves. You're basically a laughing stock.
Alright then, that's a wrap. Good game, and if you can't follow simple directions then you deserve zero port forwarding abilities.
💀
Probably getting "spammed" because very specific questions were not getting answered.
The true problem has always been tied to unsolicited inbound traffic properly getting through the perimeter network layers... even with the local router set to open/forward inbound packets, those packets were still getting filtered/blocked further up the chain. Basically, it is making the consoles think you have a different NAT type than you actually have. When it comes to truly unsolicited inbound traffic (not coming back in from a previous outbound communication), it was still getting blocked at a higher level. All of this was confirmed back on the Askey modems... the ones that gave us local control over both DMZ and port traversal.
extremetm wrote:
T-Mobile has been 'fixing' the issue in 48 hours for at the past year. Most likely just to get people off the phone. Not sure what they did to fix your issue but if they can open ports then why isn't an option to do it manually and why isn't it being done on the Nokia.
My guess is they allowed a static route to Xbox servers which would bounce back to your Xbox.
COULD NOT AGREE MORE. My anger grows every time I think of the weasel Tier ZERO tech support rep who sold me the same line of Chit. GOODBYE TMOBILE FOR THAT ALONE.
My gateway’s firmware version is: 1.2201.00.0313.
This is what I need to be rid of NAT Type 3:
1 Access the Port Forwarding menu.
2 Add a new Port using the following details:
TCP: 1935, 3478-3480
UDP: 3074, 3478-3479
gracias
p.s. this is the first piece of hardware granting me internet access that gives zero options to tweak my connectivity options. Even xfinitys hardware allows me to do port forwarding.
@Allergic Fungus Could you please tell us what firmware version is currently on your gateway so that we know what version we need to get the techs to give us? You can see the version in the TMHI app by going to the More tab at the bottom and then "Gateway information". Thanks so much!
Hurmph! I have a PS5, provided T-Mobile with the information to open the ports (port forwarding) so I (we) could be NAT 0 ( zero) or NAT1 and was told “we can’t do that”.
Now, I love the speed, and the price.
However if I’m stuck at NAT 3, then I will have to change services so I can play the multiplayer games I paid my hard earned money on just so I could play with my friends.
Are you listening T-Mobile? Do you actually care about us, the people who are paying for unsatisfactory service?
I just spoke to someone a couple of days ago about my Xbox One's NAT Type on strict. They pushed a firmware update through manually and when that didn't fix the problem they told me to connect a router to the gateway… which I am trying to figure out now because I have a double NAT issue. I'm not sure what you did but more insight on your Xbox settings would be appreciated.
