Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dangerousdave26]

We just set up a new Flight Server for the Sim-outhouse

www.sim-outhouse.com and www.sim-outhouse.net

The FS Host portion is working fine but I can not get FS Navigator to see the server no matter what I do.

This is a Windows 2008 server 32 bit. The fire wall is open with both out bound and inbound rules allowing all ports on FS Host for UDP. TCP were open but I closed them to see if it would make difference or not. It did not.

I even went so far as to create a separate rule for the FS Navigator port for 23432 but that made no difference.

I have even tried connecting the FS Navigator to another port with no luck.

Does it matter what port you try and connect the FS Navigator to FS Host. I see where I can select a port in the FS Navigator but not assign one in FS Host.

Anyway at this point I am lost.

[Dangerousdave26]

I should also mention

We are running IIS 7 webserver with MySQL and PHP installed for the forums.

[Dangerousdave26]

Here is some more testing I did.

I allowed all inbound TCP and UDP on port 23432

I allowed all outbound TCP and UDP on port 23432

FS Navigator can not see the session but if I search for the session on the default port 23456 I can see the session and I can connect.

Of course once I connect with FS Navigator I can not connect as a player.

If I connect as a player I can not see the session with FS Navigator.

[Dangerousdave26]

Repeat after me...

Its always the fire wall

Its always the fire wall

I have been saying this for years.

Here is the skinny

When creating the fire wall rules in Windows Server 2008 to not specify the program that will be using the ports. For some reason FS Navigator will never be able to connect if you do.

Create both in bound and outbound rules.

I created rules for both TCP and UDP. Those rules allow all ports

The only thing that does not work now is the connection to the Web based admin page.

[Dangerousdave26]

For those who might happen to need it later.

I posted my last comment after I got it working. Then went back and tweeked it to close the door on what did not need to be open. This took me about 3.5 hrs to figure out.

Windows 2008 built in Fire wall can be managed from the MMC console.

You need to create rules for inbound and out bound traffic.

Inbound rules

Status page and Web Admin

• Allow rule
  Protocol = TCP
  Local ports = 80 (8X or 808X which ever you are going to use)
  Remote ports  = All ports
  Program = FS Host32.exe

Player connection

• Allow Rule
  Protocol = UDP
  Local Ports = 2300 - 2400, 6073, 23456
  Remote Ports = All Ports
  Program = FS Host32.exe

FS Navigator

• Allow Rule
  Protocol = UDP
  Local Ports = 6073 - 23432
  Remote Ports = All Ports
  Program = All Programs (there is a reason for this)

Outbound Rule

• Allow rule
  Protocol = TCP
  Local ports = All Ports
  Remote ports  = All ports
  Program = FS Host32.exe

• Allow rule
  Protocol = UDP
  Local ports = All Ports
  Remote ports  = All ports
  Program = FS Host32.exe

• Allow rule
  Protocol = UDP
  Local ports = All Ports
  Remote ports  = 6073, 23432
  Program = All programs

I could not figure out which program needs to be allowed in order for the FS Navigator to connect. When ever the FS Host ports are tied only to FS Host32.exe FS Navigator can not connect. If you allow only the FS Navigator port with out including 6073 it also fails.

This tells me the problem is DX9 related but I had no time to test how it should work. When I nail it down I will update the thread.