Setting NAT to Open: Guide for Xbox Live, Port Forwarding, and UPnP Test Program Results

Hello, I have a problem with the network. I can't set nat to open, I've been redirecting ports, but I'm still having trouble connecting and playing with friends on xbox live. I tried the diagnosis with the "UPnP Test Program" and I got the following results:
TEST 1 - Operating System Support - PASSED
TEST 2 - SSDP Service Running Check - PASSED
TEST 3 - SSDP Service Automatic Check - PASSED
TEST 4 - UPnPHost Service Running Check - PASSED
TEST 5 - UPnPHost Service Automatic Check - PASSED
TEST 6 - UPnP Framework Firewall Exception Check - PASSED
TEST 7 - Adapter # 0 - 192.168.0.11 -FAILED
TEST 8 - Get External IP Address -FAILED
I will add that I am connected to the Internet on the console via a router. Anyone know what to do with it? Please help

Begasia wrote:

I can't set nat open

This is "not opened", it is not for that purpose.
You have to forward the correct ports on your router because that's the problem.
You need to find out what ports the game needs to be open and enter them into the router.
And start the UPnP function (if available on the router).

That's it, I redirected the right ports, and the console still behaves as if nat was closed. I also started UPnP, but still can't connect to my friend: /

The question is whether you have a public IP on the router's WAN or are you behind the provider's router.

All I know is that I have the router from the internet provider. And at the beginning, I did not have access to the settings because the password was changed, but when I reset the router it returned to the default. I redirected ports and turned on UPnP, but I still have problems connecting with friends on xbox live: / PS my router is 8level wrt-300

jimasek wrote:

The question is whether you have a public IP on the router's WAN or are you behind the provider's router.

Without this knowledge, it is difficult to say anything more. If you have access to the router, show its status.

Begasia wrote:

All I know is that I have the router from the internet provider

Begasia wrote:

my router is 8level wrt-300

These are two routers ...?.

no, I have one: 8 level wrt-300 and I got it when setting up wifi from the provider

KOCUREK1970 wrote:

You need to find out what ports the game needs to be open and enter them into the router.
And start the UPnP function (if available on the router).

jimasek wrote:

Without this knowledge, it is difficult to say anything more. If you have access to the router, show its status

jimasek wrote:

jimasek wrote:

The question is whether you have a public IP on the router's WAN or are you behind the provider's router.

Without this knowledge, it is difficult to say more. If you have access to the router, show its status.

how to check?

jimasek wrote:

If you have access to the router, show its status.

KOCUREK1970 wrote:

KOCUREK1970 wrote:

You need to find out what ports the game needs to be open and enter them into the router.
And start the UPnP function (if available on the router).

I did this, typed all the ports and turned on UPnP, but still can't play with some people as if nat is still "closed".
And in the 1st post I wrote what the UPnP testing program showed me and there were 2 bugs and I don't know how to get rid of them, so it looks like UPnP is not working. I wonder if I should just call the internet provider, because maybe the problem is with the internet itself or the radio receiver.

Added after 2 [minutes]:

jimasek wrote:

jimasek wrote:

If you have access to the router, show its status.

I have access to this configuration page, where you can open ports etc. I can do a screenshot just what exactly to send?

Begasia wrote:

I did this, typed all the ports and turned on UPnP, but still can't play with some people as if nat is still "closed".

I understand, but did you do it correctly, as it should be in this router ?.
If you have a manual for it, check there how to enter it correctly.

I did it as it is shown here http://portforward.com/english/routers/port_forwarding/8level/WRT-150/Xbox_Live_360.htm only there was no manual for the wrt-300 8level so I did for the wrt-150 model, it seems me it makes no difference
Screen from the router settings:

You set up a virtual server.
You redirect ports to Port Triggering.

Router status screen:


Added after 2 [minutes]:

In this guide, what I gave the link was to do just that and my friend did and it works for him, but now I will try port triggering and say if it is ok :)

Added after 4 [minutes]:

Before I do that, this question: If I want to eg open port 53, what should I choose in the "Predefined Trigger Rules" field and what should I enter in other fields?

And port 53 is opened for UDP or TCP?
You enter here:

Begasia wrote:

what should I choose in the "Predefined Trigger Rules" field

I do not know this equipment ...
Expand the list of this bar, or choose nothing, skip this paragraph, and enter what you need only where I have circled.

Ok, after expanding:

Ports I need to redirect:
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
Port 1863 (UDP and TCP)
So I understand that if there is udp and tcp, I should redirect twice only once with udp and once with tcp?
Do not enter anything in Trigger Protocol and Trigger Port?

Added after 27 [minutes]:

Okay, I think I know what the problem is, I checked my ip http://whatismyipaddress.com/ on this page and I have another ip in the router status, i.e. I have a private ip, so I guess the only thing I can do now is contact the internet provider at assignment of public ip. Do you know what this allocation of a public address looks like and do they do it at home or come to the client's home?

Begasia wrote:

So I understand that if there is udp and tcp, I should redirect twice only once with udp and once with tcp?
Do not enter anything in Trigger Protocol and Trigger Port?

Exactly.
It is a momentary port opening,
while port forwarding is permanent.

I thought ... and reset the router, just in case of "W" write down the current configuration and see if it gets the public IP then. If so, set what you need now where we got to where what enter.
You probably have a radio net ...
Since the ISP offers a private IP, it "rather" won't give you a public IP - maybe I'm wrong ...
This is done remotely (IP allocation).

KOCUREK1970 wrote:

Since the ISP offers a private IP, it "rather" won't give you a public IP - maybe I'm wrong ...

Usually such a service costs extra money on radio networks.

I have radio internet in a housing association in my city. There is always a problem with ip on radio internet? If I could not reset the router, I will call the cooperative and ask if they would assign this public address. I was looking at their site and they have a permanent ip for free in their services. Does this have anything to do with my problem? If they do not want to grant me a public ip, I can change the supplier, I even thought about it, because the competition has a more profitable offer. But how is it with this internet radio? Better to take cable? Tomorrow I will reset this router and write as it is, although I reset it some time ago and as there were problems with the internet, they still are.

A fixed IP is not the same as a public IP ... to run the server you need a public IP, and you usually have to pay extra for it (if it is available at all).

Ports are redirected in Virtual Servers, Port Triggering is used for something else, but UPnP itself consists in the fact that the application can add the necessary redirects itself.

Port triggering is the redirection of the indicated port to the address of the host that opened the connection to the indicated port (trigger). If it is to be a typical server that does not open anything itself, but listens for connections, then you need to use virtual servers - the computer on which the server is running should have a fixed IP address (it can be associated with MAC on DHCP).

In your case, you have a fixed IP, only that from the internal pool of the operator with which you bought the net. - COSTS on the ISP side are then lower.
You can have a fixed IP, but public, where you have direct access to the world.
The network should be: Ty-> net-> world, and it is: Ty-> net-> ISP-> world.
If you can, take a cable net (I have UPC myself), radio stations and problems with them are 50% of entries in the network section.

So I can't do anything myself? I'll call the provider and ask for that public ip. Then everything should be ok? If he does not agree, I will probably choose another supplier. So it's better to take cable? Does it have any disadvantages? I am just browsing the website of another provider in my city and I noticed that cable internet is much cheaper than radio. Why is it like that? And this provider has the options to change ip to public.

Begasia wrote:

better to take cable? Does it have any disadvantages?

You have to pay .
But make sure they'll do the installation for you and connect the net !.

Begasia wrote:

I noticed that cable internet is much cheaper than radio. Why is it like that?

Yes, "by peasant reason":
In the radio Internet, you have to make a "connection" to each individual (equipment, antennas, etc.), 50 clients, that's 50 "costs" of such an installation.
In cable TV, the signal goes to the block with one cable or fiber optic (the cost incurred by the company is one), and you can sell it cheaply to a larger number of customers - that is, whether their network has 20 or 200 customers in the company's expenses it makes practically no difference, the "cost" of laying the cable was the same for the company regardless of the number of customers (of course, it must pay off for them. ).
The backbone of the installation is here - just sell the service and change the servers in the headquarters to more efficient ones.
The second thing is the owner of the radio net "buys", say, a 50 Mb link and then divides it indefinitely - for a client 2345 in the queue to the network there are scraps of it.
The cable "buys" a net in GB - so when buying such a connection, they pay much less for the same 50 Mb, because they bought a net "per hectare" - you buy a lot, pay cheaper.
It's so "blatantly".

There are several ways to troubleshoot a double nat, but there are solutions that always work and those that only might help.
Double nat arises when on the way from us to the Internet there are, for example, two routers, i.e. at our home and another at the Internet provider, i.e. at the other end of the cable (or radio link) that enters our home.
A solution that always works is the setting of the public (external) IP for us by the provider and setting the so-called demilitarized zone on our home router, i.e. DMZ on the IP address permanently assigned to our Console (address reservation).
And here are some important comments:
If our provider sets a public IP for us, it does not automatically mean that on our router at the WAN input, the public IP will be downloaded from the provider. Our router will still be able to get internal IP within the provider's internal subnet. For us, public IP means that this public IP leads only to us, i.e. whatever appears on this public IP will go to us, i.e. as if all ports were redirected to our router. Of course, there may be a network where our router will immediately download the same public IP that is visible on the IP checking pages, but this is not a necessary condition and in many cable networks all users get the local IP internal to their router and still have public IP outside and This is fine.
How to check public IP:
Such IP should be able to be pinged from another network (of course, on our router you have to allow it if there is such a blockade). Another network is access to the Internet from outside our provider's local network, for example: we provide mobile internet on a smartphone as a WiFi hotspot for our laptop and then in the command line (CMD in windows) enter

ping xxx.xxx.xxx.xxx

Where these x are our public IP
If packets go through, we have 100% public IP
Alternatively, you can check what IP is displayed to all our colleagues on the websites for checking IP, e.g. my-ip.eu if all our friends who have internet from the same provider have a different IP on this website than ours, 99% of our IP is public and only available to us.
Relatively, we can temporarily set up the management of our router from anywhere on the Internet on some specific unusual port. If we manage to log into the router from outside our network, it means that our router is 'visible'. Ie we are visible at any selected port - only that there are a lot of these ports, so it's a bit of a lottery with this testing.
If the above tests are positive, it does not matter how many network devices there is a supplier between us and the Internet !!
It is best at the beginning to believe our provider that we have external and assigned only to our IP to run DMZ and check NAT.
Having a public IP and setting the DMZ for the IP that our router assigns to the Console via DHCP or that we have set hard for this console 100% solves the problem with double NAT which is then 'NAT Open'
Any other combinations like port forwarding, DMZ setup with us but no public IP etc. may or may not help. If the external IP and DMZ work, you can possibly be interested in these port forwarding and disabling DMZ, but I wouldn't exaggerate demonizing the DMZ. If we open the necessary ports for consoles and games, we will be exposed to the same attack as with DMZ only in theoretically narrower range and no problem. Theoretically, because the console itself has all unnecessary ports closed, so after opening the ports without DMZ, the difference is only in the ports that the console is open for other needs (e.g. service) than games.