Double Nat & Xbox One problem..

Trusty

Trusty

Trusty

Soldato
Joined
12 Mar 2006
Posts
16,714
Location
In The Sea Of Leveraged Liquidity
Hey, I suspect this will be pretty easy to answer for someone who knows what they are doing.

I recently picked up a TP Link AV600 extender kit to run upstairs from the main router.

When I connect the Xbox to the AV600 with wireless, I get open nat. When I go the ethernet route, I get a double nat.

Do I have to login to the AV600 settings or the main router settings to get this to open nat via ethernet.

The setup is as follows - TP link Archer c50 (main) ---> ethernet ---> AV600 ---> ethernet ---> Xbox One

Thanks.
 
What did you buy exactly? The adapters will have part numbers (e.g. TL-PA4020P).

What does the C50 connect to? It's an Ethernet only router so there must be something.
 
Thanks for taking the time to reply.

Its satellite internet. The C50 connects to a POE.

This is the power line kit I have.

https://www.tp-link.com/uk/products/details/cat-18_TL-WPA4220KIT.html


So the setup is..

POE --> Ethernet --> Archer C50 --> Ethernet --> TP Powerline (TL-WPA4220)

I'm not using the the other part of the power line kit..

I get internet with my xbox using ethernet all the way through, its just I get double nat.

When I take out the ethernet from the Xbox One & TP Powerline and go wireless, I get open nat.
 
Last edited:
It only matters if you're playing games, and a latency measured in multiple seconds probably isn't going to be allowing you to do that any time soon.
 
I am playing games.

I get like 80/90 latency when its connected via wireless, I thought maybe taking out an extra wireless connection might help a bit. It's not going to half it or anything, but at least its only 1 wireless connection instead of 2.
 
I managed to login to the TP link C50.

I've got some info that might be of use.

C50
LAN
IP - 192.168.0.1
SUB - 255.255.255.0

WAN
IP - 10.11.14.2
GATEWAY - 10.11.14.1
DNS - 8.8.8.8.8.8.8.8

POWERLINE
IP - 192.168.0.31
SUB - 255.255.255.0

XBOX
IP - 192.168.0.103
SUB - 255.255.255.0
GATEWAY - 192.168.0.1
DNS - 192.168.0.1
PORT - 3074
 
Your WAN IP (10.11.14.2) is a private NAT address.

Your internal IPs (192.168.0.n) are also private NAT addresses.

You'd expect to always have it reporting as double NAT (because it is).

The question is why it doesn't report as double NAT when you use wireless? I think we're missing some information somewhere.
 
Obviously I'm a bit clueless about what to look for. Should I be looking for some info within the Powerline settings?

Shall I change my wired Xbox IP/DNS/Gateway settings to match up with the C50?

I tried inputting the Powerline IP into the DMZ option on my C50, that didn't work.
 
Agreed @bremen1874

There’s a device at 10.11.14.1 that is doing some sort of routing between OP’s true WAN and the C50. @Trusty , do you know what that might be? Have quickline given you any devices. If you enter http://10.11.14.1 into a browser does any sort of admin page come up giving you a clue?

The Ethernet cable from the WAN port on the C50 - where does it go. What does it plug into on the other end?
 
The Powerline adapter will be transparent. The IP it has is only used for management. You are using it in a strange way, but it should work.

You'd expect anything connected to the C50 (wired or wireless, directly or indirectly) to report double NAT.

What equipment is the C50 connected to? A model number and/or photo would be best.
 
I was using the power line the proper way I suppose, via the electrics, but I thought via ethernet would be a bit better, only cost me £10 to get a 25m cable.

The c50 connects to a POE. Shall I get a model number for that? Or do you mean the wireless dish on my house?

I spoke to Quickline about this issue earlier today, they said to go into the port forwarding settings on my C50 and put my Xbox IP settings into that, It didn't work unfortunately. I can always ring them tomorrow again, they seemed very helpful and willing to answer any questions
 
You must log in or register to reply here.
Back
Top Bottom