Jump to content
The simFlight Network Forums

WideFS7 has stopped connecting over network to MSFS


Recommended Posts

Posted

As of today, I am unable to connect  WideFS 7 to MSFS over the network. I have been using WideFS 7 in this configuration for years, but today, it will not connect. I am using both FSUIPC  and WIDEFS 7(most recent versions of each) as registered. I am using this configuration to connect my ACARS (client computer)  to MSFS running on the FS computer over the network.

I have searched the forums and tries the recommended "fixes", but nothing has worked.

 

Thank you for your help.

 

Michael

 

 

FSUIPC7.log

Posted
18 hours ago, mleuck48 said:

I have searched the forums and tries the recommended "fixes", but nothing has worked.

Well, you haven't searched that well... This exact same issue has been reported many times, and my response is always the same. RTFM!!
Read the documentation and follow all the trouble-shooting steps there, e.g. check workgroup, disable firewalls, set ServerName/Protocol, etc

Once you have tried all that, if still not working, report back, telling me what you have tried and attach the 5 files I need to see: FSUIPC7.log, FSUIPC7.ini, WideServer.log, WideClient.log, WideClient.ini.

Posted
13 hours ago, mleuck48 said:

I have  followed your request and am still unable to get connected. Attached are the files you requested.

Not exactly - you also need to tell me what you have tried, and those files are missing the WideServer.log file. Please attach that as well - and I need to see all files from the same session. so you probably need to re-attach ALL files.

Did you try with all firewalls disabled (client, server, router)? If not, please do that and also confirm that firewalls were all down when you tested.
Your WideClient.ini shows that you have not specified the Protocol ini parameter, and you have misspelled ServerIPAddr as ServerIPAdd, so also add/correct those before testing again.

John

 

Posted

Hello John 🙂

WideClient stopped working on my side too (it worked fine for years).
On my side the probable cause is having updated my main computer (the one that runs MSFS and FSUIPC 7.5.1) to Windows 11 version 24H2 (Build 26120.3073).

I tried various unsuccessful actions such as:

  • Pausing Windows firewalls on both sides
  • Adding "ServerName=MERCURE" in my WideClient.ini
  • Adding "BroadcastMode=Yes" and "ProtocolPreferred=UDP" to my FSUIPC.ini

Another "strange" fact is FSUIPC icon does not show in Tasks bars (see screenshot in ZIP).

Other programs running on LAN computer (SIMU02) are working normally and communicating correctly with main computer (MERCURE): AivlaSoft EFB, ProSim Audio and IOS for example.

Kind regards,

Didier
 

WideClientLogs.zip

Posted
1 hour ago, DaddyBoon said:

I tried various unsuccessful actions such as:

  • Pausing Windows firewalls on both sides
  • Adding "ServerName=MERCURE" in my WideClient.ini

Better to stop/disable the firewalls, and also check the firewall in your router.
You should also add "Protocol=TCP" to your WideClient.ini.

Why did you not include your WideServer.log file? As I said to the previous poster, I need to see all 5 files from the same session.

1 hour ago, DaddyBoon said:

Adding "BroadcastMode=Yes" and "ProtocolPreferred=UDP" to my FSUIPC.ini

Remove those and stick to TCP defined by the client(s).

1 hour ago, DaddyBoon said:

Another "strange" fact is FSUIPC icon does not show in Tasks bars (see screenshot in ZIP).

No idea what could cause that...Do you see the FSUIPC icon in the system tray when it is closed?

Posted
1 hour ago, DaddyBoon said:

On my side the probable cause is having updated my main computer (the one that runs MSFS and FSUIPC 7.5.1) to Windows 11 version 24H2 (Build 26120.3073).

I tried various unsuccessful actions such as:

  • Pausing Windows firewalls on both sides
  • Adding "ServerName=MERCURE" in my WideClient.ini
  • Adding "BroadcastMode=Yes" and "ProtocolPreferred=UDP" to my FSUIPC.ini

Please also check/confirm that all your computers are in the same windows Workgroup.

As your issues started after a windows update, it must be due to config of that machine, which would either be the workgroup or the firewall.
Did you also download and install the latest windows VC++ redistributables after the update? This may also be needed and does no harm, so if not done already please also try that.

John

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.