Client Waiting for Server

[Scott]

I have the client laptop connected to my router by cable along with my server and flight sim machine. I have reviewed the board discussions of this topic but none seem to do the trick. I am running build #55 pf the server and build #72 on the client software. The server software recognizes P3D v4.3.29.25520 but doesn't appear to see the client. For the client I used the IP4 address of the server PC.

 

Any suggestions on what I should do next? I have turned off all firewalls on both PCs. Thanks.

[KiloJuliett]

Hello *NEWUSER*

 

Welcome to the EFB forum. May I suggest you start first here (https://forum.aivlasoft.com/topic/2522-forum-rules-read-before-post/) and tell us your real name as per the forum rules?

To analyze your issue, please create a set of support files both on the server and the client system and upload them here. Thanks.

[Scott]

Mr. ATC - Regret not using my real first name. Corrected in the profile settings.

 

Using P3D V4.3

Using FSUIPC 5.132

Using W10 64 bit 1803 Updated

UAC disabled (lowest setting) on both server and client 

 

When I first installed V2 I placed the client on the server PC. In that configuration the server exchanged data with the client and performed as expected. I have removed the client from the Flight Sim/server PC and installed the client on a laptop. Both server and client PC are connected via RJ45 to the same modem/router. I did read through the chapters of the manual. The only process I am not sure about is that in chapter 3 concerning the server and firewall.

 

"1.1.1 Firewall
Since the Server uses the TCP/IP communication infrastructure of your computer it might be blocked by the Windows Firewall by default. This is dependent of the settings of the UAC (user access control) of your computer.
Please press “Unblock” to allow the Server to communicate with the Client(s)."

 

I do not know where the "Unblock" button is displayed or accessed. 

 

Files attached. Thank you in advance for your support. Scott

Server_201807261304.txt.zip

Client_201807261308.txt.zip

[KiloJuliett]

Thanks Scott

 

I can see in your file that the server never gets a request from a client, so there is not really a connection. I can also see you entered the IP in the client to establish connection. Can you confirm you are not using dynamic IP allocation (so the IP of the server computer is always the same)? Otherwise, I suggest to use the computer name instead of the IP. This allows the connection will always be re-established also when different IPs are used. To change the server address, click on the on/off button in the client, then click on server location to enter a new address.

[Scott]

Thanks Jonas for the suggestions...I turned off DHCP and set a static IP4 address and DNS servers (Google 8.8.8.8 and 8.8.4.4)...but no joy in the connection with either the IP address or the PC name.  The static address has '(Preferred)' text behind it -- not sure if that means anything, but my machine was set to dynamic with that wording and remained the same when I set the static address. With the PC name set on the client I receive the popup "Could not resolve IP address for computer 'DESKTOP-XYZABC'.  Please make sure computer ....is running and connected to the local network.

 

I still have my firewalls off and UAC at the lowest level on both machines.

Appreciate any other ideas to check.

Scott

[aivlasoft]

5 hours ago, Scott said:

I turned off DHCP and set a static IP4 address

Please make sure that both computers have the the same network address (installation manual, 1.3.2 -> Important).

From the logfile of the Client I can see that the Client's address is 192.168.254.126 and the Server's address is given as 192.168.7.142.

 

In the network settings of your computer you can see the so called 'subnet mask'. The subnet mask determines which part of the IP address is the network address and which part is the workstation address. Usually in the subnet mask is set to 255.255.255.0 which means that the first three groups of digits from this IP address are the network address. In the above mentioned Client address this would be 192.168.254.nnn whereas the Servers's network address is 192.168.7.nnn. So you see with this example that the connection cannot be established because there are different network addresses used.

 

If the subnet mask is given as 255.255.255.0 (on both computer it must be identical) then set the IP address to the same network address (e.g. on both computers 192.168.254.nnn, or on both computers 192.168.7.nnn) where 'nnn' means the workstation address within the network. The workstation address obviously has to be different from each other.

 

[Scott]

Hi Urs - I will admit to not understanding the alchemy of networks and settings...

 

When I did the above procedure, I set the client IP address to 192.168.7.141, the subnet mask to 255.255.255.0, the default gateway to 192.168.7.1 (same as server), and the DNS servers to the Google hubs...but then the status told me no internet was available. Is something wrong with the client IP address or the gateway I set?

Thanks, Scott

[aivlasoft]

Hi Scott,

I'm sorry but it's almost impossible to support network issues when not "sitting in front of the devices". It starts with the proper configuration of the router and there are another couple of things to properly set. I can only give you an idea of a 'standard' configuration:

Router has IP address 192.168.1.1  (the router's address usually is also the gateway address)

Today's routers usually have a built in DHCP function which assigns the IP address automatically to each workstation which is starting up (requires to configure the workstation to automatically get the IP address from the router).

If no DHCP is available, or you override it by setting the IP address of the workstations manually, then a typical address for the first workstation would be 192.168.1.2, then the next would be 192.168.1.3 and so on.

As long as the subnet mask is set to 255.255.255.0 the first three groups of digits of the IP address is the network address and must be identical for all workstations within the same logical network (here in this example it would be 192.168.1.nnn). So your Server's IP address and your Client's IP address must have the same network address. The workstation address (which is the fourth group of digits), can be set individually but also different for each of the workstation (e.g. Client 192.168.1.2, Server 192.168.1.3). 

 

More on this at Wikipedia: https://en.wikipedia.org/wiki/IPv4#Addressing

I know this might be confusing but maybe you know a friend of you who is familiar with all this stuff?

 

 

 

[Scott]

Thanks Urs - I understand the difficulty of setting this up remotely. I tried a different gateway address but that did not work. I will look for some local expertise who can see my system and perhaps configure the router and client differently.

[Scott]

Hi Urs...just a short update that I was able to connect, but in an unexpected way. I set the server IP4 to a static address and then configured the client software on a laptop to that address. But instead of using a connection via RJ45 to the router, I selected a WIFI connection for the laptop. Viola - the client now connects to the server!  Thank you for your assistance in working this solution. Scott