primekillo.blogg.se

1. MY FSNAVIGATOR DOESNT WORK ANYMORE HOW TO
2. MY FSNAVIGATOR DOESNT WORK ANYMORE SIMULATOR
3. MY FSNAVIGATOR DOESNT WORK ANYMORE WINDOWS

So when Microsoft released FS2004, they changed it so it would always try to use one standard port, which was 23456.

MY FSNAVIGATOR DOESNT WORK ANYMORE HOW TO

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.īack 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 those ports have to be explicitly forwarded to the FS machine. 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. 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). 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. 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. 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. 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. My system now passes the Chocolatesoftware port tester, and the Port Forward port tester. If you don't see these entries, open the following ports in your firewall, in the exact same manner as you did above. 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: Start with 2300, and continue repeating this process until you get to port 2400.

You have just opened a port on the firewall. Now enter the port number, and select UDP, and click OK. 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.

MY FSNAVIGATOR DOESNT WORK ANYMORE WINDOWS

Go to- Start Menu / Control Panel / Windows Firewall ,and click the Exceptions tab. or disable your firewall before flying online. either open all of these ports manually in your windows/other firewall,

(differing router's will have differing pages, but the open ports will be the same, regardless of design or maker)

Your router's firewall should look like this when you are done: Where it tells you to enter 2302, make it 2300 instead.

follow the step by step instructions for EACH port listed. (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) next click on the Static IP Address guide and complete it exactly as it says to do!

MY FSNAVIGATOR DOESNT WORK ANYMORE SIMULATOR

scroll down and select Flight Simulator 2004 Scroll down the page and find your router and click on the name. After searching the FSHost forum for a solution to my port problem, I found this:ĭo EXACTLY as they say without missing ANYTHING, and you should have everything set up correctly.