lztat573 said:
What if your ports are blocked by your IP. I have opened them up on my router, windows, and Internet security program and can't get .47 to work because it tells me my ports are not open.
If your ports are blocked by your provider you would need to contact them. However, as others have already stated, the likelihood of that being the case is pretty slim.
More than likely you are overlooking a simple configuration step. Have a look around at some of the other threads dealing with this and you'll see what I'm talking about.
https://forums.realflight.com/showthread.php?t=23398 is a good example of a configuration problem that can cause a lot of confusion. It's usually something very simple that has been overlooked or changed inadvertently that is causing the problem.
Recheck your configuration and make sure you have everything setup correctly. Check your router manufacturer's web site for updated firmware and documentation. If you are using any third party firewall or "Internet Security" suites you will need to allow the ports in those as well. Check the sites for those applications and make sure you read the documentation regarding how to open ports or allow inbound connections.
If you use windows firewall run the following commands to open the proper ports. Even if you don't use windows firewall run these commands and then they'll be open if you ever should need to use it later.
Range 1
Code:
for /L %i in (61234,1,61250) do netsh firewall add portopening UDP %i "RealFlight MultiPlayer Port Range 1 - UDP %i"
Range 2
Code:
for /L %i in (61300,1,61316) do netsh firewall add portopening UDP %i "RealFlight MultiPlayer Port Range 2 - UDP %i"
Then download the
pfportchecker tool and run it against your computer to see if your ports are open.
If you still can't get it working post some information about your configuration in the form of your router make, model and version numbers, screenshots of your router port forwarding configuration page(s), screenshot of the output of the "ipconfig /all" command, and attach the ports.txt file produced by the "netsh firewall show portopening >> c:\ports.txt" command. You could also include the technical support document produced by
this process.
If you get all of that information together someone should be able to help you out. Take your time and be methodical, you'll find your issue.