🛈 Announcement
Greetings! Ghost-Recon forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game.
  1. #1

    If you have a Strict or Moderate NAT Type...

    It will be extremely hard for you to find games. I cant even join my other friends' games, but on other games we could all play together. Also, when get put into a game, right before its starts to load up the match, it says "Connection to Server Lost".... What gives?!

    Please, make this game easier to find games and connect with their friends.
    Share this post

  2. #2
    All the mutiplayer games have problems with NAT types not being open. How about spending 30 min figuring out how to fix your NAT?
    Share this post

  3. #3
    Forward the correct ports in your router and assign a static IP to your console and NAT shouldnt be a problem. Most multiplayer games require open NAT and its not really a game issue i.e. nothing that Ubisoft could fix for you.
    Share this post

  4. #4
    Kaiskune's Avatar Senior Member
    Join Date
    Mar 2008
    Posts
    1,174
    I have to agree with Uloi, they can only do some much from their end a middle ground is needed. opening your ports is deceptively simple.

    http://portforward.com/english/appli...60/default.htm

    find your routers maker, then model number and it'll tell you how to do it from there
    Share this post

  5. #5
    Mr_Shade's Avatar Senior Community Manager
    Join Date
    Nov 2009
    Location
    EMEA CRC
    Posts
    21,335
    360: http://ubisoft.custhelp.com/app/answ...st/p/1421,2184
    PS3: http://ubisoft.custhelp.com/app/answ...st/p/1483,2480

    for 360:
    If you are receiving any multiplayer connection issues, or having trouble connecting to a multiplayer game please try the following:

    - Start by testing your Xbox live connection with the following steps:

    1. Start at the Xbox 360 dashboard.
    2. From the My Xbox menu scroll to the far right to System Settings.
    3. Choose Network Settings.
    4. Select your connection type (wired or wireless).
    5. Choose Test Xbox Live connection.

    - If this test shows your connection as either moderate or strict then you will most likely have some sort of interference within your connection to Xbox Live. In this case, please try the steps below:

    1. Restart your network hardware. Turn off your Xbox 360, Modem, and Router and wait about 15 - 30 seconds
    2. Fully power up your modem
    3. Fully power up your router
    4. Turn on your Xbox 360 and test the Xbox Live connection again.

    - At this point if you still have trouble then you may have a firewall interfering with your connection. Please configure the following network ports within your router:

    TCP 53
    TCP 80
    TCP 3074

    UDP 88
    UDP 3074
    UDP 53

    - Finally, if this does not solve your issue, try placing your Xbox 360 in the DMZ of the router or establishing a direct connection to your modem and retry.

    For PS3:

    If you are receiving any multiplayer connection issues, or having trouble connecting to a multiplayer game please try the following:

    - Start by testing your network connection with the following steps:

    1. Start at the PS3 XMB.
    2. Scroll to Settings.
    3. Choose Network Settings.
    4. Select Internet Connection Test.


    - If this test shows your connection as NAT type 3, then you will most likely have some sort of interference within your connection to the online servers. In this case, please try the steps below:

    1. Restart your network hardware. Turn off your PS3, Modem, and Router and wait about 15 - 30 seconds
    2. Fully power up your modem
    3. Fully power up your router
    4. Turn on your PS3 and test the network connection again


    - At this point if you still have trouble then you may have a firewall interfering with your connection. Please configure the following network ports within your router:

    PlayStation Network Required Ports
    UDP: 3658
    UDP: 3478-3479
    TCP: 80, 443, 5223

    Game Ports for Ghost Recon: Future Soldier
    UDP &TCP: 2346, 80, 21400

    - Finally, if this does not solve your problem, try establishing a direct connection to your modem (bypass the router) and retry.
    Share this post

  6. #6
    GI_Ace's Avatar Junior Member
    Join Date
    Feb 2017
    Location
    Los Angeles
    Posts
    1

    Open ports for Ghost Recon Wildlands PC

    Can someone please post the ports for PC version? I keep having NAT Status offline.
    Share this post

  7. #7
    The replies in this thread are comical. Port 80 is for HTTP traffic. Port 53 is for DNS. You're telling me in order to run your game, I need to setup destination NAT so inbound connections can make DNS and HTTP queries to my computer? Get a life.

    Your devs need to learn how to get away from this UPnP BS and people on forums need to stop talking like they understand how networks work. Opening your computer to the internet isn't a good idea. "Plug directly into your modem"... Why? So people can connect to my file shares, remote desktop, any other service that my computer is running directly from the internet? Jesus....
     4 people found this helpful
    Share this post

  8. #8
    Originally Posted by MinkSauce Go to original post
    The replies in this thread are comical. Port 80 is for HTTP traffic. Port 53 is for DNS. You're telling me in order to run your game, I need to setup destination NAT so inbound connections can make DNS and HTTP queries to my computer? Get a life.

    Your devs need to learn how to get away from this UPnP BS and people on forums need to stop talking like they understand how networks work. Opening your computer to the internet isn't a good idea. "Plug directly into your modem"... Why? So people can connect to my file shares, remote desktop, any other service that my computer is running directly from the internet? Jesus....
    This!
    Share this post

  9. #9
    Originally Posted by MinkSauce Go to original post
    The replies in this thread are comical. Port 80 is for HTTP traffic. Port 53 is for DNS. You're telling me in order to run your game, I need to setup destination NAT so inbound connections can make DNS and HTTP queries to my computer? Get a life.

    Your devs need to learn how to get away from this UPnP BS and people on forums need to stop talking like they understand how networks work. Opening your computer to the internet isn't a good idea. "Plug directly into your modem"... Why? So people can connect to my file shares, remote desktop, any other service that my computer is running directly from the internet? Jesus....
    Its going to make TCP & UDP connections not DNS or HTTP so you are mistaken sir and double check your ports and what they do.
    Share this post

  10. #10
    Originally Posted by DMF-Lokiey Go to original post
    Its going to make TCP & UDP connections not DNS or HTTP so you are mistaken sir and double check your ports and what they do.
    Ports 53 and 80 are well known ports - meaning they are reserved for DNS and HTTP traffic, respectively; per RFC.

    I also have problems with strict NAT, and like many others, will not open well known ports directly to my computer, nor bypass my firewall just to play a game. Even for a patched system it would take minutes for it to be hacked (at worst) or seconds for it to be pummeled by attempts to be hacked (at best). Port scans are as ubiquitous as background noise.

    I have no problem configuring a rule that allows bi-directional traffic for connections that are established outbound first (send/receive UDP for example) but I will not allow inbound receive/send through my firewall unless I'm publishing a service.

    I'm not a developer, but IMHO the right way to do this is to initiate the connection outbound, even for friend-based coop, to some sort of "lobby" rather than trying to connect to friends' instances directly. Much more secure. This just seems to me that Ubisoft is trying to save on hardware at the expense of the security of their customer base.

    Wildlands shows much promise, but the requirement to forward well known service ports inbound is ridiculous, and a deal breaker.
     3 people found this helpful
    Share this post