In other words, it always searches on 234, regardless of what you tell it to use, and then it searches on the requested port as well if it's not 23456. But if you tell it to search on anything other than 23456, for example 23457, then it searches three ports: 23456, 6073, and 23457.
If you tell it to search on 23456, it searches 234, as I said above. But I'm not getting anything back for the 6073 request, so I'm guessing that the FSHost machine is never getting it.įS2004 does something else here also. What's supposed to happen is that the DirectPlay on the FSHost machine will respond to the request on 23456, and also respond to the request to 6073, but when it responds to 6073 it actually responds back on 23456 as well (or occasionally on a port in the 2302-2400 range, I don't fully understand why). When FS2004 searches, it tries whatever port you have it set to (default = 23456) as well as the "alternate DirectPlay port", 6073. I watched everything with a packet sniffer and I think I see what's going wrong. If you're not interested in the gory details, you can stop reading here. You might want to check it again and make sure it's for UDP, and it's forwarded to the right IP, and is marked as active, etc. The short answer is that something's wrong with the forward you setup for 6073. But when I tried FSNav on 23456, it worked, and it found the session (but of course it couldn't actually connect because of the password, as you said). When I tried FSNav on the default port 23432, it couldn't find the session. First, when I tried connecting with FS2004, it worked fine, as you said. My Fsnav version is 4.7 and Fsnav multiplayer connections work very well with FSINN connections.
What did I forget? I have checked that the "Disconnect FsNavigator after.xx minutes" box is UNCHECKED in FsHost config. Here is the copy of the forwarding ports of my local router: I have tried to open ports too on the FS Computer. The connection log of FsHost does not mention at all my connection try with fsnav, and reports only my connections with FS9. I use the standard port (23432) of Fsnav and when I type the server's IP address in FSNAV multiplayer window, I see my local connection sending requests to Internet, I have no error message back, but no session appears and the JOIN button remains definitely grey. I connect to the current session and I have the server's welcome message and the ?xxx commands work ok on FS screen.īut IMPOSSIBLE to connect with FSNAV. I have opened the FsHost dedicated ports on my server's router as described in the forum here, and this is a copy of the port forwarding of the server (the server is on port 82 for the global connection, as there is also a web server running on port 80 on the same computer):Īll works fine for a connection from a remote FS9 access.
#Fsnavigator for fs9 world database Pc
The server's PC has also a fixed IP local address: 192.168.1.135
This ensures that all scenery files can be read, and increases the speed of database creation.I have just installed Fshost 3.2b3 on a stand alone server with no-ip domain name and also fixed IP address. While FSNavDBC is running, Flt.Sim must not be active. Changes and additions are recognised by FSNavDBC by the names and paths of scenery (.BGL) files, the size of the scenery files and the date and time of their creation.
#Fsnavigator for fs9 world database install
When you install additional scenery or make changes in existing scenery, this will go much faster, as only the actual changes have to be made. Creating the scenery database for the first time will take several minutes. With FSNavDBC.exe for FS2000/FS2002/FS2004 you can also bring new scenery into the Flight Simul ator, or change parameters of scenery already present. After each addition to or modification of the Flt.Sim scenery files the FSNavDBC program must be re-run to add or modify data in the database. The external program FSNavDBC.exe reads these data from the Flt.Sim scenery files and copies it into a separate database. FSNavigator uses all information about Runways, VOR's, NDB's, etc.