atrailblazer Posted April 26, 2019 Share Posted April 26, 2019 Hello Guys... I did the update (build #106) for both client and server. The Client never loaded..'Waiting for Server' (local). I have the Server going but the Client never loads. Any help would be appreciated!! Alex B. Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted April 26, 2019 Share Posted April 26, 2019 3 hours ago, atrailblazer said: Hello Guys... I did the update (build #106) for both client and server. The Client never loaded..'Waiting for Server' (local). I have the Server going but the Client never loads. Any help would be appreciated!! Alex B. Hi Alex, Please post the Support Files. Quote Link to comment Share on other sites More sharing options...
atrailblazer Posted April 26, 2019 Author Share Posted April 26, 2019 Lonewulf...I hope I did this right Alex Client_201904260809.txt.zip Server_201904260809.txt.zip Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted April 26, 2019 Share Posted April 26, 2019 Thanks Alex, It seems that you did not update both Server and Client the same way. You obviously downloaded the Full Client Installer and updated the Server. This way two different TCP Port numbers are used which makes a connection of course impossible. What I see from the Support Files: Server TCP Port Number: 51748 Client TCP Port Number: 57892 We have changed the Port Numbers with the latest update for several reasons. This implies however that either BOTH Server and Client are UPDATED (this will not change the TCP Port Number) or BOTH Server and Client are NEWLY INSTALLED (this will change the TCP Port Number). Using Update on one component and Full Install on the other just results in what you have got. Easy remedy: Close both Server and Client. Start the server, go to the tab Settings/System and change the TCP Port Number to 57892. Then restart the Server and the Client and you should be fine. Quote Link to comment Share on other sites More sharing options...
atrailblazer Posted April 26, 2019 Author Share Posted April 26, 2019 Lonewulf... It's working now! Thank you for your help. Yes, I uninstalled the Client, reinstalled it. When I did the update it showed an error and didn't take. I should have done both, but didn't. Again, thank you. Have a good weekend! Alex Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted April 26, 2019 Share Posted April 26, 2019 10 minutes ago, atrailblazer said: Lonewulf... It's working now! Thank you for your help. Yes, I uninstalled the Client, reinstalled it. When I did the update it showed an error and didn't take. I should have done both, but didn't. Again, thank you. Have a good weekend! Alex Thanks Alex, for the update. Great to hear that it works now. Quote Link to comment Share on other sites More sharing options...
RRVyper Posted May 8, 2019 Share Posted May 8, 2019 Just wanted to add my experience to this thread - I started the Server and it said there was an update (#108), which I did. It said to run the DbBuilder to update the sim, which I also did. Then I started the Server. I then ran the Client and it asked to update (to #108) so I let it update as well. However, when I tried to run it, it stuck at 'Waiting for Server (local)'. I had to go into the ClientSettings.txt and change the port to what the Server was set to (57892). There were no errors and both programs are run as administrator. It appears the client updater does not change the port (but it did change the Program Version entry). Just letting you know. Randy Quote Link to comment Share on other sites More sharing options...
aivlasoft Posted May 8, 2019 Share Posted May 8, 2019 Hi Randy, 12 minutes ago, RRVyper said: However, when I tried to run it, it stuck at 'Waiting for Server (local)'. what you describe is exactly the situation which Lonewulf47 explained some posts before. When you ran the complete Installer on the Server side, it was setting a new port number. But you did not run the complete installer for the Client, instead of just ran the automatic update which does not change the port number. Therefore you had to manually adjust the port number. Quote Link to comment Share on other sites More sharing options...
RRVyper Posted May 8, 2019 Share Posted May 8, 2019 Negative, Urs. I ran the automatic update for both the Server and the Client. That's why I wanted to mention it. Randy Quote Link to comment Share on other sites More sharing options...
robert_folmer Posted May 16, 2019 Share Posted May 16, 2019 Hello And I have the exact same issue as mention by RRVyper above I was prompted by MS to do an update and reboot on windows 10. This morning an update on EFB. Server part went ok Client is now waiting for server Quote Link to comment Share on other sites More sharing options...
lonewulf47 Posted May 16, 2019 Share Posted May 16, 2019 1 hour ago, robert_folmer said: Hello And I have the exact same issue as mention by RRVyper above I was prompted by MS to do an update and reboot on windows 10. This morning an update on EFB. Server part went ok Client is now waiting for server No update on Client?? Please submit Support Files. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.