Search the archive:
YaBB - Yet another Bulletin Board
 
   
 
Pages: 1 2 3 4
Send Topic Print
I SOLVED my port problems (Read 8142 times)
Sep 8th, 2009 at 10:44am

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
After searching the FSHost forum for a solution to my port problem, I found this:

http://www.portforward.com/english/routers/port_forwarding/routerindex.htm

Do EXACTLY as they say without missing ANYTHING, and you should have everything set up correctly.

-Scroll down the page and find your router and click on the name.

-Skip the advertisment page

-scroll down and select Flight Simulator 2004

-next click on the Static IP Address guide and complete it exactly as it says to do!
Direct link: http://www.portforward.com/networking/staticip.htm
(Not all systems will work with this setup, that's OK, set everything back to default like it says, and then move on to the next step)

-follow the step by step instructions for EACH port listed. Where it tells you to enter 2302, make it 2300 instead.

Your router's firewall should look like this when you are done:
(differing router's will have differing pages, but the open ports will be the same, regardless of design or maker)
...



-Now, You must
    -either open all of these ports manually in your windows/other firewall,
    - or disable your firewall before flying online.

To Open Windows Firewall Ports in XP:
Go to- Start Menu / Control Panel / Windows Firewall ,and click the Exceptions tab.


...






now click the 'Add Port...' tab

...






Now enter a name for the port, I find that fs#### works, as I know it's a flight sim port, and the number is the same as the port, helping to keep track of where you are when opening 101 ports.  Wink

Now enter the port number, and select UDP, and click OK.
You have just opened a port on the firewall. Cool

Start with 2300, and continue repeating this process until you get to port 2400.

...



When you are done, you should have 101 entries for ports 2300-2400, and if you've already tried or have been online using the FShost server program, you should also have these entries listed:


...

If you don't see these entries, open the following ports in your firewall, in the exact same manner as you did above.

UDP 23456 
UDP 6073
UDP 23432
TCP 47624
TCP 80




Found the info here: http://www.chocolatesoftware.com/forum/index.php?topic=737.0

My system now passes the Chocolatesoftware port tester, and the Port Forward port tester.

It's A LOT easier than you think. Wink

Special Note:


-IF you use the windows firewall, be aware that you must set ALL 101 ports to open individually with 2300-2400. Otherwise you will have 99 closed ports if you just open 2300 & 2400.

-Disabling the windows firewall automatically opens all of these ports. Do so only if you know what you are doing.



This is a complete list of all ports that will be tested and  need to be open:


...
...


I verified this on two different testers, so unless you can get yours and FSPorttest to say everything is OK, I wouldn't trust it yet. I've never been able to get it to say that I'm good, and now I can. Wink

FSNavigator users should also make sure that port 23432 is open.
« Last Edit: Nov 21st, 2009 at 5:42pm by ShaneG »  
IP Logged
 
Reply #1 - Sep 8th, 2009 at 11:02am

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
I think this is why there are so many port problems:

Some people may not realize there are 101 ports to open with 2300-2400, and only open the two leaving the other 99 closed,

but wait, aren't those the FS2002 ports you ask....


read this explanation of Multiplayer ports from the FSHost creator:

Quote:
I've had a couple of emails from people asking why the tests fail on their machine even though FS2004 and/or FSX seem to be working ok.

I've seen that happen before.  What's happening is that FS is connecting to the server on 23456, and since the router sees the connection initially being made from inside your LAN, it allows the connection out and then also automatically forwards data coming back in on that port to the same machine that requested it.  This is why you don't have to forward every port your machine connects out on -- because the router sees the outgoing request and then allows data to come back in on the same port without a forwarding rule.  And you can even have multiple machines going out on the same port, and your router is smart enough to automatically forward the return data back to the right machine.

However, sometimes FS will end up switching off of the 23456 port and onto the "alternate" ports, which are 6073 and a sorta-random port in the 2300-2400 range (typically the lower numbered ports in that range).  It only does it in certain situations, but when it does, data will be coming back into those ports and the router will have never seen any data going out on them, so it won't know how to forward them to the right machine.  So those ports have to be explicitly forwarded to the FS machine.  This can also happen when you have FS and FSHost on the same machine and you're connecting to your own session, because in that case you have to tell FS to use some port other than 23456 (since it's already being used by FSHost), and then FS will switch to the alternate ports.

Back in FS2002, it always used a port in the 2300-2400 range, and it caused lots of problems for people that didn't know how to setup their networks to allow the incoming data on a random port.  So when Microsoft released FS2004, they changed it so it would always try to use one standard port, which was 23456.  But they left the random port stuff in there as well, for the cases where it wasn't able to use 23456.  FSHostClient (for FSX) uses the FS2004 method of connecting to the session, so it behaves the same as FS2004 in that case.

So you can usually get away with just using 23456 with FS2004 and FSX.  But you should be aware that your setup is not optimal (networking-wise, anyway), and there's a slight chance that it could cause problems for other people in the session.  For that reason, it's always best if you can setup your firewall or router to forward the correct ports to the FS machine, and then you'll be sure that everything's ok.

Unfortunately if you have FSHost and FS on different machines in your local network, there's no good way to solve the problem because you can't explicitly forward a port to more than one machine.  If you can run both on the same machine, it's always better because you can forward all the ports to just one machine (and usually FSHost doesn't cause problems for FS).  Otherwise I'd suggest forwarding all the ports to the FSHost machine, and then just rely on port 23456 for the FS machine, since your router will do the automatic routing when it sees the outgoing connection from that machine.

Hope that helps explain it a bit... It's a bit of a mess, this whole thing with how FS uses ports.

Russell



So based on this, you could have the needed FS9 & FSX ports open, but if your game for some reason decides to switch over to one of those FS2002 ports, and someone doesn't have all 99 in between ports open, it's game over for all.


Your Router & Firewall must have all 101 ports from 2300-2400 open or this is bound to keep happening.

The mystery may finally be solved. Grin Wink


 
IP Logged
 
Reply #2 - Sep 8th, 2009 at 11:32am

JBaymore   Offline
Global Moderator
Under the curse of the
hombuilt cockpit!

Gender: male
Posts: 10261
*****
 
Thanks for posting this in detail Shane.  Maybe it will help.

This info is and has been "out there"... it is just that people will not make the effort to DO it because it typically affects OTHERS... not them enjoying their flying on-line.

And yes... opening those 100+ ports is a "labor of love" in the annoyance factor category.  Did it long ago....... and thought it was CRAZY,....as well a a bit scary.  Cheesy

The REAL issue here is Microsoft putting such an absurd situation into play for the original software for multiplayer use.  This software is intended for the casual user..... NOT the computer and network guru.  WHAT were they thinking?  Roll Eyes

best,

..................john
 

... ...Intel i7 960 quad 3.2G LGA 1366, Asus P6X58D Premium, 750W Corsair, 6 gig 1600 DDR3, Spinpoint 1TB 7200 HD, Caviar 500G 7200 HD, GTX275 1280M,  Logitec Z640, Win7 Pro 64b, CH Products yoke, pedals + throttle quad, simpit
IP Logged
 
Reply #3 - Sep 8th, 2009 at 11:32am

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
Digging around in the stickies here will produce similar results!  Grin Wink

http://forums.simviation.com/cgi-bin/yabb2/YaBB.pl?num=1220714574
« Last Edit: Mar 18th, 2013 at 7:51am by pete »  
IP Logged
 
Reply #4 - Sep 8th, 2009 at 11:45am
Crash   Ex Member

 
I will apply all those things tonight. I do not use the Windows firewall but the free version of Zonealarm. Do I have to open all those ports in there too? Or should I do it anyway just in case?

Crash Wink

EDIT: Just checked something. Fsporttest still says that there is a problem and times out after three seconds. However, using the porttester of Utorrent (I know. Don't ask.) tells me that all the ports I need (23456, 23457, 23458, 6073 and 2300-2400) are open and working. Now what? Firewall disabled for the time being.
 
IP Logged
 
Reply #5 - Sep 8th, 2009 at 11:52am

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
Those ports should be open regardless of which firewall you use. Any kind of closure prevents signal from traveling, and that appears to be what causes the problem, at least that how I read it. Wink

I've just taken the habit of shutting down my windows firewall before doing multi player, and now I know for sure that my router is truly set up correctly. 

Anything that manages to make it past my router's firewall, NickN has said, is sure to move past the windows firewall as though it wasn't even there, so I don't feel any less safe with it turned off during online play.
 
IP Logged
 
Reply #6 - Sep 8th, 2009 at 11:53am

Fozzer   Offline
Colonel
An elderly FS 2004 addict!
Hereford. England. EGBS.

Posts: 24861
*****
 
I purchased the "Port Forward" download program (£15) http://portforward.com/  some time ago, when my ISP gave me a Free Modem/Router for my Broadband connection.
It failed dismally to detect the necessary ports on my Smart AX MT 882 ADSL Broadband Wired Modem/Router, even by Manually going into the Router Software to detect them.
The result was, to ensure there were no Port problems during Multiplayer, I was forced to abandon the Router idea completely, and purchase a simple Wired ADSL USB Modem only, to cure the problem completely.
All my previous Port problems were contained within the Router!
Running the "Port Test" now, checks a long list of Ports throughout my whole system, and reports then all as; "Open"!

Paul.... Smiley...!


 

Dell Dimension 5000 BTX Tower. Win7 Home Edition, 32 Bit. Intel Pentium 4, dual 2.8 GHz. 2.5GB RAM, nVidia GF 9500GT 1GB. SATA 500GB + 80GB. Philips 17" LCD Monitor. Micronet ADSL Modem only. Saitek Cyborg Evo Force. FS 2004 + FSX. Briggs and Stratton Petrol Lawn Mower...Motor Bikes. Gas Cooker... and lots of musical instruments!.... ...!
Yamaha MO6,MM6,DX7,DX11,DX21,DX100,MK100,EMT10,PSR400,PSS780,Roland GW-8L v2,TR505,Casio MT-205,Korg CX3v2 dual manual,+ Leslie 760,M-Audio Prokeys88,KeyRig,Cubase,Keyfax4,Guitars,Orchestral,Baroque,Renaissance,Medieval Instruments.
IP Logged
 
Reply #7 - Sep 8th, 2009 at 11:56am

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
I have no choice, I HAVE to use a router here. Wink

If I had it my way, it would be gone, quickly. But it isn't a problem anymore. Wink Grin Cool

And I didn't buy that silly program of theirs, I just followed the instructions and did it manually. Takes less time than a NickN system tweak.  Grin Wink
 
IP Logged
 
Reply #8 - Sep 8th, 2009 at 11:58am
Crash   Ex Member

 
See EDIT in my previous posting.

Crash Wink
 
IP Logged
 
Reply #9 - Sep 8th, 2009 at 12:02pm

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
Quote:
See EDIT in my previous posting.

Crash Wink


Which ports does it time out on with FSport test?

And is the firewall off when you run it?
 
IP Logged
 
Reply #10 - Sep 8th, 2009 at 12:30pm

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
This is a complete list of all ports that will be tested and  need to be open:

...
...


I verified this on two different testers, so unless you can get yours and FSPorttest to say everything is OK, I wouldn't trust it yet. I've never been able to get it to say that I'm good, and now I can. Wink
 
IP Logged
 
Reply #11 - Sep 8th, 2009 at 12:39pm
Crash   Ex Member

 
...

This is with all the right ports open in my router, all firewalls disabled.

Crash Wink
 
IP Logged
 
Reply #12 - Sep 8th, 2009 at 12:43pm

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
Just to make sure all of the bases are covered, have you done the 'Static IP address' setup at the PortForward link?

http://www.portforward.com/networking/staticip.htm
 
IP Logged
 
Reply #13 - Sep 8th, 2009 at 1:09pm
Crash   Ex Member

 
ShaneG wrote on Sep 8th, 2009 at 12:43pm:
Just to make sure all of the bases are covered, have you done the 'Static IP address' setup at the PortForward link?

http://www.portforward.com/networking/staticip.htm


Yes, i do have a static ip address. Just checked each and every port using the Utorrent porttester. They are all open. Any other random port is closed as it should be. I think, no I know I did everything I had to do. Still going to open all the ports in Windows Firewall, just to make sure.

Crash Wink
 
IP Logged
 
Reply #14 - Sep 8th, 2009 at 1:19pm

ShaneG   Offline
Colonel
I turned into a Martian!

Posts: 10000
*****
 
That would be the only other thing I could think of that we've done different then. Undecided

It took me about 5 minutes to do them all, and damn near gave me carpal tunnel. Grin Wink

  Have you tried the PortForward port tester? I would believe that a 2-1 result would be rather assuring, but either way you should still open the FS ports everywhere possible.
 
IP Logged
 
Pages: 1 2 3 4
Send Topic Print