Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hey Pete,

I have recently ran into a very weird issue between my FSUIPC and WIDEFS.

I have been running these two together for many moons now and it has been working perfect. I use WideFS to run my ACARS programs on a second PC.

After a computer upgrade and a complete re-install of everything, I seem to have a problem with the FSUIPC + WIDEFS connection. Basically, it all connects fine, I can start my ACARS program as normal and connect to the sim. The problem occurs some time later when FSUIPC and WideFS loose connection with eachother (i assume). Im guessing that this is what happens because after I land and check my position, my ACARS (running via widefs) thinks im still somewhere enroute.

Ive done 3 flights, first one with the Aerosoft Airbus Xtended which worked fine. But during my second 2 flights (both with the PMDG NGX) the issue above repeated itself.

Now i know 3 flights is not many and this could be an isolated event (well twice in a row is not isolated but yea) and perhaps further testing is needed. Im posting here before any further tests hoping that this is a known issue and you might have the answer for me without the need for further testing (and more loss of VA hours)

I should mention that both my FSUIPC and WideFS are registered and that I have the new FSUIPC posted a few days ago on your site.

Thanks in advance,

Tal

Posted

Now i know 3 flights is not many and this could be an isolated event (well twice in a row is not isolated but yea) and perhaps further testing is needed. Im posting here before any further tests hoping that this is a known issue and you might have the answer for me without the need for further testing (and more loss of VA hours)

I'm afraid there is no way I can help without information. After a problem session you need to close FSX and WideClient, and show me the FSUIPC Log, the WideServer log and the WideClient log.

Pete

Posted

Hey Pete,

Wow that was fast!

I have just had the above mentioned problem in my session about 15 mins ago.

Ill be more than happy to get those logs for you, could you tell me where i might find them?

Posted

Ill be more than happy to get those logs for you, could you tell me where i might find them?

All things to do with FSUIPC are in the FS Modules folder alongside FSUIPC! All things to do with WideClient on the Client are in the folder you placed WideClient into! (It really isn't hard!).

You'll be best just pasting them into a message here. Don't try uuploading the files themselves.

Pete

Posted

Right, I have found all the log files, before I post them just a quick question. Would you need to see the logs right after a problem session? In other words, do the logs only reflect the last connection?

The reason I ask is, after I had shut down the sim I restarted everything just to make sure that I can actually connect, which worked fine. Im assuming the logs as they are now will only reflect that successful connection?

Posted

Right, I have found all the log files, before I post them just a quick question. Would you need to see the logs right after a problem session? In other words, do the logs only reflect the last connection?

Yes.

Pete

  • 3 weeks later...
Posted

Hey Pete

Since i started this thread the problem seemed to have cured it self and i was able to fly several flights without issue.

over the past few days I've been experiencing the same disconnects again. This time i got the logs, so ill paste them below.

Thanks and hope you can spot the issue.

WideClient Log

********* WideClient Log [version 6.995] Class=FS98MAIN *********

Date (dmy): 05/06/13, Time 23:37:04.992: Client name is TOM-PC

2980 LUA: "C:\Users\Tom\Desktop\WideFS - NEW!!!\Initial.LUA": not found

2996 Attempting to connect now

2996 Trying to locate server: Need details from Server Broadcast

2996 Failed to connect: waiting to try again

3058 New Client Application: "PVA ACARS" (Id=4336)

5039 Attempting to connect now

7098 Server = FRUMERMAN-PC

7145 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

7145 ... Okay, IP Address = 192.168.0.2

7145 Connection made okay!

14430 ASE with WX requester detected

583897 New Client Application: "BAVPhoenix" (Id=6652)

1414929 Timed out send() of 43 bytes [Time=501 mSecs]

1414961 send() failed [0 bytes] after 40 retries, request depth is 6

1417004 Attempting to connect now

1417004 Server = FRUMERMAN-PC

1417051 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1417051 ... Okay, IP Address = 192.168.0.2

1438049 Error on client pre-Connection Select() [Error=10060] Connection timed out

1438049 Ready to try connection again

1440061 Attempting to connect now

1440061 Giving up server, looking for another!

1440061 Server = FRUMERMAN-PC

1440077 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1440077 ... Okay, IP Address = 192.168.0.2

1463118 Server = FRUMERMAN-PC

1463134 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1463134 ... Okay, IP Address = 192.168.0.2

1486160 Giving up server, looking for another!

1486160 Server = FRUMERMAN-PC

1486175 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1486175 ... Okay, IP Address = 192.168.0.2

1509185 Server = FRUMERMAN-PC

1509201 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1509201 ... Okay, IP Address = 192.168.0.2

1532242 Giving up server, looking for another!

1532242 Server = FRUMERMAN-PC

1532663 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1532663 ... Okay, IP Address = 192.168.0.2

1555689 Server = FRUMERMAN-PC

1555689 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1555689 ... Okay, IP Address = 192.168.0.2

1578715 Giving up server, looking for another!

1578715 Server = FRUMERMAN-PC

1578715 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1578715 ... Okay, IP Address = 192.168.0.2

1601725 Server = FRUMERMAN-PC

1601725 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1601725 ... Okay, IP Address = 192.168.0.2

1624735 Giving up server, looking for another!

1624735 Server = FRUMERMAN-PC

1624735 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1624735 ... Okay, IP Address = 192.168.0.2

1647745 Server = FRUMERMAN-PC

1647745 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1647745 ... Okay, IP Address = 192.168.0.2

1670771 Giving up server, looking for another!

1670771 Server = FRUMERMAN-PC

1670771 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1670771 ... Okay, IP Address = 192.168.0.2

1693781 Server = FRUMERMAN-PC

1693781 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1693781 ... Okay, IP Address = 192.168.0.2

1716807 Giving up server, looking for another!

1716807 Server = FRUMERMAN-PC

1716807 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1716807 ... Okay, IP Address = 192.168.0.2

1739817 Server = FRUMERMAN-PC

1739817 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1739817 ... Okay, IP Address = 192.168.0.2

1762827 Giving up server, looking for another!

1762827 Server = FRUMERMAN-PC

1762827 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1762827 ... Okay, IP Address = 192.168.0.2

1785837 Server = FRUMERMAN-PC

1785837 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1785837 ... Okay, IP Address = 192.168.0.2

1808848 Giving up server, looking for another!

1808848 Server = FRUMERMAN-PC

1808848 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1808848 ... Okay, IP Address = 192.168.0.2

1831873 Server = FRUMERMAN-PC

1831873 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1831873 ... Okay, IP Address = 192.168.0.2

1854883 Giving up server, looking for another!

1854883 Server = FRUMERMAN-PC

1854883 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1854883 ... Okay, IP Address = 192.168.0.2

1877894 Server = FRUMERMAN-PC

1877894 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1877894 ... Okay, IP Address = 192.168.0.2

1900904 Giving up server, looking for another!

1900904 Server = FRUMERMAN-PC

1900935 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1900935 ... Okay, IP Address = 192.168.0.2

1923992 Server = FRUMERMAN-PC

1923992 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1923992 ... Okay, IP Address = 192.168.0.2

1947018 Giving up server, looking for another!

1947018 Server = FRUMERMAN-PC

1947049 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1947049 ... Okay, IP Address = 192.168.0.2

1970075 Server = FRUMERMAN-PC

1970075 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1970075 ... Okay, IP Address = 192.168.0.2

1993085 Giving up server, looking for another!

1993085 Server = FRUMERMAN-PC

1993100 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1993100 ... Okay, IP Address = 192.168.0.2

2016111 Server = FRUMERMAN-PC

2016111 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

2016111 ... Okay, IP Address = 192.168.0.2

2039121 Giving up server, looking for another!

2039121 Server = FRUMERMAN-PC

2039136 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

2039136 ... Okay, IP Address = 192.168.0.2

2062178 Server = FRUMERMAN-PC

2062240 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

2062240 ... Okay, IP Address = 192.168.0.2

2063020 ****** End of session performance summary ******

2063020 Total time connected = 1408 seconds

2063020 Reception maximum: 40 frames/sec, 6784 bytes/sec

2063020 Reception average whilst connected: 27 frames/sec, 2634 bytes/sec

2063020 Transmission maximum: 10 frames/sec, 780 bytes/sec

2063020 Transmission average whilst connected: 3 frames/sec, 130 bytes/sec

2063020 Max receive buffer = 3805, Max send depth = 6, Send frames lost = 6

2063020 **************** Individual client application activity ****************

2063020 Client 4336 requests: 18301 (Ave 12/sec), Data: 56408861 bytes (40063/sec), Average 3082 bytes/Process

2063020 Client 6652 requests: 39136 (Ave 27/sec), Data: 902670 bytes (641/sec), Average 23 bytes/Process

2063020 ********* Log file closed (Buffers: MaxUsed 7, Alloc 96253 Freed 96253 Refused 0) *********

WideServer Log

********* WideServer.DLL Log [version 7.90] *********

Blocksize guide = 8192 (double allowed)

Date (dmy): 05/06/13, Time 23:36:38.012: Server name is FRUMERMAN-PC

15038 Initialising TCP/IP server

15038 Initialising UDP/IP server

16099 Broadcasting service every 1000 mSecs

35864 Incoming connection Accepted ok (skt=9888) TCP

35911 Connected to computer "TOM-PC" running WideClient version 6.995 (skt=9888) TCP

1428969 Retried 20 times: sends blocked for over 5 secs! (0 of 293 sent), Error=10035 (skt=9888) TCP

1431044 Send ok but needed 8 attempts! (335 of 335 sent) (skt=9888) TCP

1433571 Restarting service due to zero reception!

2113220 Closing down now ...

Memory managed: Offset records: 2460 alloc, 2459 free

Read buffer usage: 4050 alloc, 4050 free, max in session: 1

Write buffer usage: 85852 alloc, 85852 free, max in session: 1

Throughput maximum achieved: 32 frames/sec, 6975 bytes/sec

Throughput average achieved for complete session: 9 frames/sec, 885 bytes/sec

Average receive rate from "TOM-PC": 1 frames/sec, 84 bytes/sec

********* Log file closed *********

FSUIPC4 Log

********* FSUIPC4, Version 4.90 by Pete Dowson *********

Running inside FSX on Windows 7

Module base=678E0000

User Name="tal frumerman"

User Addr="tal3000@hotmail.com"

FSUIPC4 Key is provided

WideFS7 Key is provided

110 System time = 05/06/2013 23:33:52

110 FLT UNC path = "\\FRUMERMAN-PC\Users\Tal\Documents\Flight Simulator X Files\"

500 Trying to connect to SimConnect Acc/SP2 Oct07 ...

500 FS UNC path = "\\FRUMERMAN-PC\FSX\"

687 LogOptions=00000000 00000001

687 SIM1 Frictions access gained

687 Wind smoothing fix is fully installed

687 G3D.DLL fix attempt installed ok

687 SimConnect_Open succeeded: waiting to check version okay

687 Trying to use SimConnect Acc/SP2 Oct07

4524 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

4524 Initialising SimConnect data requests now

4524 FSUIPC Menu entry added

4571 \\FRUMERMAN-PC\Users\Tal\Documents\Flight Simulator X Files\Default.FLT

4571 \\FRUMERMAN-PC\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

7878 Weather Mode now = Global

32215 \\FRUMERMAN-PC\FSX\SimObjects\Airplanes\PMDG 737-800NGX\B737-800.AIR

163115 Weather Mode now = Theme

163115 Weather Mode now = Global

163302 System time = 05/06/2013 23:36:35, Simulator time = 16:30:36 (14:30Z)

163302 Aircraft="Boeing 737-800NGX British Airways Virtual G-DOCF"

165627 Starting everything now ...

165736 Advanced Weather Interface Enabled

192974 Weather Mode now = Theme

193145 Weather Mode now = Global

455711 Weather Mode now = Theme

455835 Weather Mode now = Global

2271110 Sim stopped: average frame rate for last 2110 secs = 34.4 fps

2281203 System time = 06/06/2013 00:11:53, Simulator time = 15:05:11 (15:05Z)

2281203 *** FSUIPC log file being closed

Average frame rate for running time of 2110 secs = 34.4 fps

G3D fix: Passes 39385, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 2460 Allocs, 2460 Freed

********* FSUIPC Log file closed ***********

Thanks again Pete.

Tal

Posted

over the past few days I've been experiencing the same disconnects again. This time i got the logs, so ill paste them below.

Thanks and hope you can spot the issue.

The issue seems to be simply that all of a sudden neither end can see any requests or replies arriving from the other, just like a physical disconnection :

And it isn't temporary. Retries (attempts at complete reconnection) aren't working:

WideClient Log

1414929 Timed out send() of 43 bytes [Time=501 mSecs]

1414961 send() failed [0 bytes] after 40 retries, request depth is 6

1417004 Attempting to connect now

1417004 Server = FRUMERMAN-PC

1417051 Trying TCP/IP host "FRUMERMAN-PC" port 8002 ...

1417051 ... Okay, IP Address = 192.168.0.2

1438049 Error on client pre-Connection Select() [Error=10060] Connection timed out

1438049 Ready to try connection again

1440061 Attempting to connect now

1440061 Giving up server, looking for another!

So, things get stopped or blocked or disconnected after nearly 24 minutes, and the reconnection doesn't work -- not 'refused', just ... nothing, no response. The error 10060 is from Windows.

WideServer Log

1428969 Retried 20 times: sends blocked for over 5 secs! (0 of 293 sent), Error=10035 (skt=9888) TCP

1431044 Send ok but needed 8 attempts! (335 of 335 sent) (skt=9888) TCP

1433571 Restarting service due to zero reception!

The identical problem really, reflected at the Server end at the same time.

This really is looking like some sort of hardware problem. Maybe overheating, or a real intermittent fault in the Ethernet hardware at one end or the other.

Are they both using motherboard-based Ethernet? Any chance of trying a separate Network Interface Card instead -- first one end, then the other, which should clearly identify which end is responsible. Or if you are using a separate card, moving it to a different slot perhaps.

If I thought it was a software issue, maybe network drivers, I'd suggest trying UDP protocol instead of TCP. It might be worth a hot, but it does look like hardware to me.

Regards

Pete

Posted

This really is looking like some sort of hardware problem. Maybe overheating, or a real intermittent fault in the Ethernet hardware at one end or the other.

Are they both using motherboard-based Ethernet? Any chance of trying a separate Network Interface Card instead -- first one end, then the other, which should clearly identify which end is responsible. Or if you are using a separate card, moving it to a different slot perhaps.

If I thought it was a software issue, maybe network drivers, I'd suggest trying UDP protocol instead of TCP. It might be worth a hot, but it does look like hardware to me.

Regards

Pete

Hi Pete,

at the moment the setup is like this:

Client PC - Laptop connected to router wirelessly

Server PC - PC connected to router via Ethernet cable.

The laptop is an old laptop that I have been using to run Wideclient for years without any issues what-so-ever. The issues only started after i bought my new FS machine, the server in the setup. Im not sure if the ethernet is motherboard-based or not, nfortunately hardware isnt my strong point :P It does sit on the motherboard with the actual plug on the back of the pc, if that helps. I dont think heat is playing a big role here, as I have a pretty useful water cooler and I monitor my temps when the comp is under load and all seems well within limits. I think your diagnostics regarding the ethernet could be the culprit here.

I also have a built-in wireless on the motherboard. Perhaps I could test using that and eliminating the ethernet all together? its not ideal, as im sure you know the onboard wireless is pretty slow compared with Ethernet, but i guess it could help identify the problem if it is related to the ethernet?

I should mention, even when WideFS+FSUIPC lose connection, i can still use the internet and all other things requiring internet on the Server pc. It is only the widefs connection that is affected. Am I correct in assuming that if it was ethernet related i would also experience disconnects in other apps that use the internet?

Also, as far as I can see, after these disconnects, simconnect seems to still be running fine, ie ActiveSky still says that its connected to the sim and still injects weather into the sim over the network

I will also try switching to UDP protocol and see if that helps...

Thanks for helping me troubleshoot and hopefully we can identify the culprit :)

Regards,

Tal

Posted

Client PC - Laptop connected to router wirelessly

Server PC - PC connected to router via Ethernet cable.

The laptop is an old laptop that I have been using to run Wideclient for years without any issues what-so-ever.

Hardware problems are things which develop, unlike software which stays the same unless it gets its data corrupted.

BTW you are lucky that you don't get intermittent cross-interference on the wi-fi link. In my house i find WiFi is fine for short-term data exchanges, eg with iPhone and iPad, or even file transfers to/from a laptop, but I can't rely on it for regular continuous connections such as that needed by WideFS when flying -- at least, not in rooms with lots of electrical equipment running like my cockpit room!

I also have a built-in wireless on the motherboard. Perhaps I could test using that and eliminating the ethernet all together? its not ideal, as im sure you know the onboard wireless is pretty slow compared with Ethernet, but i guess it could help identify the problem if it is related to the ethernet?

It might be worth trying it even if only as a way of eliminating things like the router and the hardwired ethernet connection. If you were to adopt this permanently it would be best to keep your internet (router) connection hardwired, for speed, and, using a different (fixed) IP addrerss for the wireless side, put the explicit IP address into the Client INI file so it uses that wirelss link, not the one to the router.

I should mention, even when WideFS+FSUIPC lose connection, i can still use the internet and all other things requiring internet on the Server pc. It is only the widefs connection that is affected. Am I correct in assuming that if it was ethernet related i would also experience disconnects in other apps that use the internet?

I don't know. It might well imply a problem at the client end, or with the Wireless part of the router. Do you still have good internet connection from the Client after WideFS disconnects?

Also, as far as I can see, after these disconnects, simconnect seems to still be running fine, ie ActiveSky still says that its connected to the sim and still injects weather into the sim over the network

Is ActiveSky running on the Client, then?

I will also try switching to UDP protocol and see if that helps...

UDP is the protocol that SimConnect and Windows Explorer uses.

Thanks for helping me troubleshoot and hopefully we can identify the culprit :)

One problem is that I'm by no means a Network expert. Whenever I've had problems in the past I've always had to narrow things down by trial and error, eliminating things bit by bit. What seems odd in your case is that it started when you changed your Server PC, so it is more likley to be related to that, unless you can thing of something else that's changed.

Regards

Pete

Posted

Hi Pete,

BTW you are lucky that you don't get intermittent cross-interference on the wi-fi link. In my house i find WiFi is fine for short-term data exchanges, eg with iPhone and iPad, or even file transfers to/from a laptop, but I can't rely on it for regular continuous connections such as that needed by WideFS when flying -- at least, not in rooms with lots of electrical equipment running like my cockpit room!

Will it be worth trying to connect the laptop with ethernet as well? This way I can keep all of widefs related connections hardwired.

It might be worth trying it even if only as a way of eliminating things like the router and the hardwired ethernet connection. If you were to adopt this permanently it would be best to keep your internet (router) connection hardwired, for speed, and, using a different (fixed) IP addrerss for the wireless side, put the explicit IP address into the Client INI file so it uses that wirelss link, not the one to the router.

Ill give this a shot this evening. Like you say, if anything, it will help eliminate some variables.

I don't know. It might well imply a problem at the client end, or with the Wireless part of the router. Do you still have good internet connection from the Client after WideFS disconnects?

Yes, both client and server still have a good connection to the internet. that is mainly whats puzzling me

Is ActiveSky running on the Client, then?

Yes it is, and seems to stay connected throughout these disconnects

UDP is the protocol that SimConnect and Windows Explorer uses

interesting, seeing as both simconnect and IE seem to have a continuous connection, maybe the problem lies somewhere in the TCP protocol. i shall definitely try this.

What seems odd in your case is that it started when you changed your Server PC, so it is more likley to be related to that, unless you can thing of something else that's changed

These are my thoughts too. Im sure the issue is somewhere somehow with the new pc, the Server.

One more question, probably a long shot, but could antivirus and associated firewalls be causing any of these disconnects? I have disabled the firewall aswell as the antivirus, however, I can see that the antivirus (bullguard) processes are still running. My old setup (before this new server) didnt involve anything to do with antivirus as I didnt have one installed on the old server. This is the only other change I can think of.

Thanks again,

Regards,

Tal

Posted

Will it be worth trying to connect the laptop with ethernet as well? This way I can keep all of widefs related connections hardwired.

I always recommend hardwiring if possible, in any case, and it's worth a shot here just in case the wireless link is glitching.

Yes, both client and server still have a good connection to the internet. that is mainly whats puzzling me

Yes, puzzles me too.

One more question, probably a long shot, but could antivirus and associated firewalls be causing any of these disconnects? I have disabled the firewall aswell as the antivirus, however, I can see that the antivirus (bullguard) processes are still running. My old setup (before this new server) didnt involve anything to do with antivirus as I didnt have one installed on the old server. This is the only other change I can think of.

Hmm. Maybe, but why only WideFS? But it's an area I know little of. I only run AV and Firewall stuff on my development PC, where I also do all my support and download/upload activity. Whilst the cockpit PCs are also all connected to the Internet, I don't do email or interact on websites specifically on any of those. I rely on good security settings in the Router.

Regards

Pete

Posted

As always, Thank you Pete, your support is second to none, normally I would find myself waiting a good few days for answers, with you its most often a few minutes, if that.

So to summarise my 'homework' for the next few flights:

1. Try to run everything wired - looking for a problem with the wireless aspect of my connection

2. Failing step 1, try to run everything wireless - looking for a problem with the wired aspect (wire itself, ethernet port on router or port on pc)

3. Try UDP protocol instead of TCP (im guessing its changing a line in the .ini file?)

did I miss anything?

I guess I will change the protocol to UDP first and see if that makes a difference. The thing is, whats most puzzling (even more than simconnect staying connected) is that since i opened this thread, everything had been working just fine for many hours of flight, it was only recently it crept back with the disconnects.

I'll report back in any case,

Thanks again!

Regards,

Tal

Posted

3. Try UDP protocol instead of TCP (im guessing its changing a line in the .ini file?)

From your WideClient log earlier, this line:

2996 Trying to locate server: Need details from Server Broadcast

indicates that you allow Wideclient to find the Server by itself. That's fine, and then you can choose the protocol in the [WideServer] section of the FSUIPC4.INI file. It's "ProtocolPreferred=UDP". Please have a read of the first feew paragraphs in the "Configure Your Network" section in the WideFS user guide (about the 4th page).

However, if you have both wired and wireless services in the Server, with different IP addresses, you'd need to use both the ServerIPAddr and Protocol parameters in the WideClient.INI file in order to make sure it chooses the right one.

I guess I will change the protocol to UDP first and see if that makes a difference. The thing is, whats most puzzling (even more than simconnect staying connected) is that since i opened this thread, everything had been working just fine for many hours of flight, it was only recently it crept back with the disconnects.

Are you sure there's nothing around which might be generating intereference at certain times. Some machinery maybe?

Anyway, the wired connection test should eliminate airborne intereference.

Regards

Pete

Posted

Hi Pete,

Back with an update...

Hardwired the client laptop to the router and all is well. Many hours of flight with no disconnects and clean logs.

I also found a setting in the Ethernet properties on the server pc "power saving mode" which was enabled, I don't know much about this but I disabled it anyway.

Once again, thank you for your excellent support.

Regards,

Tal

Posted

Hardwired the client laptop to the router and all is well. Many hours of flight with no disconnects and clean logs.

Great! Thnks for getting back with this.

I also found a setting in the Ethernet properties on the server pc "power saving mode" which was enabled, I don't know much about this but I disabled it anyway.

Good idea. I don't know what it does either, but it doesn't sound very performance friendly!

Regards

Pete

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.