Client will not connect to server

[michaelfairburn]

EDIT:  Moved to proper forum by Admin

 

Hi, I'm having issues getting the client to connect to the server (on my local machine). I have tried everything I can think of (not a long list LOL) including a full reinstall of the latest (build 116) of both server and client, but to no avail. The log client log file says this:

 

2020-04-11 10:45:01.716   Debug   : ========== AivlaSoft.Efb.Client Version 2.1 (build #116) started ==========
2020-04-11 10:45:01.725   Debug   : +++++++ System info +++++++
2020-04-11 10:45:02.774   Debug   : CPU = Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
2020-04-11 10:45:02.777   Debug   : SpeedMHz = 4001, BusSpeedMHz = 100, Cores = 4, Threads = 8
2020-04-11 10:45:02.814   Debug   : OS = Microsoft Windows 10 Pro / 64-bit
2020-04-11 10:45:02.818   Debug   : Version = 10.0.18363
2020-04-11 10:45:02.821   Debug   : OS language = en-GB, Regional settings = en-NZ
2020-04-11 10:45:02.824   Debug   : Number decimal separator = '.'
2020-04-11 10:45:02.827   Debug   : Number group separator = ','
2020-04-11 10:45:02.830   Debug   : Process is 64bit
2020-04-11 10:45:02.834   Debug   : +++++++ System info +++++++
2020-04-11 10:45:02.888   Debug   : Settings loaded from: C:\Users\micha\Documents\AivlaSoft\EFB2\Client\Settings\clientSettings.txt
2020-04-11 10:45:02.895   Debug   : AutoUpdateInterval = 0
2020-04-11 10:45:02.901   Debug   : Verify software version ...
2020-04-11 10:45:03.562   Debug   : Latest versions read
2020-04-11 10:45:03.569   Debug   : Latest version is installed
2020-04-11 10:45:06.432   Debug   : IP address of this computer ('FLTSIM') is 192.168.1.24
2020-04-11 10:45:06.436   Debug   : Server mode is 'local'
2020-04-11 10:45:06.440   Debug   : Using IP endpoint 127.0.0.1/57892
2020-04-11 10:45:06.443   Debug   : TcpController initialized
2020-04-11 10:45:06.459   Warning : Colors file 'C:\Users\micha\Documents\AivlaSoft\EFB2\Client\Settings\Colors\colorsDefault.bin' doesn't exist. Loading default colors.
2020-04-11 10:45:08.958   Debug   : Services started
2020-04-11 10:45:13.407   Debug   : Trying to connect to server ...
2020-04-11 10:45:19.401   Debug   : Trying to connect to server ... ... (repeated)
 

Any ideas?

 

Mike

[aivlasoft]

Hi Mike,

the first thing that I were checking are the Windows firewall settings. Is the Client allowed to connect to the network?

 

If that doesn't fix the issue, please create a set of support files (one of the Client, one of the Server) and upload them here. Thanks.

[Michael Collins]

Hi Michael/Urs,

 

I have exactly the same problem.  In my case, the server is in remote mode, otherwise my client log appears to be identical.  Like Michael Fairburn, I have tried everything I can think of but cannot get it to connect.

 

I notice the thread before this refers to the incompatibility of  EFB with the new version of Orbx/FTX Central.  I ask this because I recently updated that program to the new version and I noticed that it re-arranged the sequence of the sceneries in the library of P3Dv4. Is there any connection between that and the failure to connect, I wonder?

 

Kind Regards,

Michael Collins (in lockdown!)

 

 

 

 

 

 

 

[lonewulf47]

1 hour ago, Michael Collins said:

I notice the thread before this refers to the incompatibility of  EFB with the new version of Orbx/FTX Central.  I ask this because I recently updated that program to the new version and I noticed that it re-arranged the sequence of the sceneries in the library of P3Dv4. Is there any connection between that and the failure to connect, I wonder?

 

No, there are no incompatibility issues with ORBX Central. I use it from the beginning along with EFB2 without any issues. Rearranging the sceneries is in no way related to connection issues between Server and Client. It just means that whenever you added/deleted an ORBX scenery through the Central, you need to re-run the DbBilder. Whenever referring to any problems it is extremely helpful to provide a complete set of support files.

 

[michaelfairburn]

Both apps are allowed through the firewall (both private and public networks), so I don't think that that's the problem. Log files attached as requestsed.

 

Mike

Client_202004120840.txt.zip Server_202004120841.txt.zip

[lonewulf47]

16 minutes ago, michaelfairburn said:

Both apps are allowed through the firewall (both private and public networks), so I don't think that that's the problem. Log files attached as requestsed.

 

Mike

Client_202004120840.txt.zip 16.2 kB · 3 downloads Server_202004120841.txt.zip 347.49 kB · 1 download

Mike,

 

For any reason that is unknown to me, you are using different port numbers on Server and Client. While your Server uses #51748, youtr Client listens to #57892. This way of course no communication can be established.

To overcome this situation is is necessary to use the same port number on both Server and Client.

Do the following:

 

- start the Server

- got to the System Tab and select "Settings and more"

- open Settings

- under TCP network change the Port number to 57892

 

 

- press apply

- close the Server

 

Thereafter start EFB2 the usual way. Connection should be established normally now.

[michaelfairburn]

Awesome, that fixed it, thank you

 

Mike

[Michael Collins]

Hi Mike/Urs

 

Mine is fixed also although my set up was different from Michael Fairburn's, it was the same problem.  My Server was using the correct port 57892 but my Client (on a remote PC) was using port 51748.  I tried to change it in the Client Settings.txt  but it reininstated the wrong number again when I restarted the program. I then uninstalled the Client and reinstalled it.  It then used the correct Port number and ran perfectly.  Easter Joy!

 

Thanks very much Urs  for the instant and excellent support.  It is much appreciated, especially in the difficult times in which we all find ourselves.

 

Keep safe.

Michael.

 

 

[lonewulf47]

1 hour ago, Michael Collins said:

 I tried to change it in the Client Settings.txt  but it reininstated the wrong number again when I restarted the program.

 

Yes, most probably because you changed the number in the ClientSettings.txt while the Client was still running. When closing the Client, the file was rewritten using the current settings...