simonvreeke Posted March 10, 2014 Report Posted March 10, 2014 Hello, I have a problem with the connection between WideFS and Wideserver when running FSX. This situation started after the update with the current installed version of FSUIPC(7.929). I have on one PC ( WIN8.1) installed FSX and Prepar3D 2.1. On the other PC ( WIN7) installed WideFS. When I start FSX there is no connection and FSX is "waiting for clients" and WIDEFS is "waiting for connection". No matter how long I wait, but there is no connection. After that I close FSX and I start Prepar3d. Almost immidiatly there is a connection between WideFS and Wideserver. I have attached the logs of FSX Wideserver, Prepar3d Wideserver and WideFS log. In the log I have seen, that there is an error message after connecting to FSX. (10060) I have tried several things to solve the problem: rebuild widefs ini, rebuild fsx cfg, new default flight in fsx, reinstallation of fsx, but no change at all!!! Hopefully you can help me, because now I'm unable to fly with fsx and Prosim. If you need more information, please let me know. Regards, Simon
Pete Dowson Posted March 10, 2014 Report Posted March 10, 2014 I have a problem with the connection between WideFS and Wideserver when running FSX. This situation started after the update with the current installed version of FSUIPC(7.929). No updates to FSUIPC have changed anything relating to WideFS in many years. I have on one PC ( WIN8.1) installed FSX and Prepar3D 2.1. On the other PC ( WIN7) installed WideFS. When I start FSX there is no connection and FSX is "waiting for clients" and WIDEFS is "waiting for connection". No matter how long I wait, but there is no connection. After that I close FSX and I start Prepar3d. Almost immidiatly there is a connection between WideFS and Wideserver. Evidently you have something set incorrectly for FSX. Perhaps your SimConnect.xml is set to use the same port? I have attached the logs of FSX Wideserver, Prepar3d Wideserver and WideFS log. No you haven't. I don't think you can attach such files here. Best to simply paste their contents into your message. In the log I have seen, that there is an error message after connecting to FSX. (10060) After connecting? Error 10060 is the Windows error "connection timed out". That will be from the WideClient end. It is being blocked. I have tried several things to solve the problem: rebuild widefs ini, rebuild fsx cfg, new default flight in fsx, reinstallation of fsx, but no change at all!!!Hopefully you can help me, because now I'm unable to fly with fsx and Prosim. I am not surprised, because none of those things have anything at all to do with WideFs connections. And because merely upgrading FSUIPC also has nothnig at all to do with WideFS connections, I think somethnig else has changed in your system since it worked. Additionally, WdeFS is EXACTLY the same whether on FSX or on P3D. Which is why I'm suspecting that the ports needed are being taken by something else on your FSx installation, possibly SimConnect or another add-on you've installed. Pete
simonvreeke Posted March 10, 2014 Author Report Posted March 10, 2014 Hello Pete, thank you for your quick reaction. The Windows error occurs after starting FSX and after the moment I see the message "waiting for clients" and not after connection as I wrote. I've tried to copy/paste the logs into this page, but I can't. Maybe I can send them by e-mail? How and where can I see if there is a conflict with SimConnect? It looks like something is blocking the connection. I have installed the migration tool for Prepar3d to install FSX add-ons into Prepar3D. Could it be, that this package could block the connection? With kind regards, Simon
Pete Dowson Posted March 10, 2014 Report Posted March 10, 2014 I've tried to copy/paste the logs into this page, but I can't. Maybe I can send them by e-mail? Odd. you're the third person to say they can't paste into messages. It is very odd. Please see this thread which I think includes an answer. http://forum.simflight.com/topic/76255-wide-fs-connection-fsx/?hl=%2Bcut+%2Band+%2Bpaste#entry464896 How and where can I see if there is a conflict with SimConnect?It looks like something is blocking the connection. Only in the SimConnect.XML file -- you need to avoid ports 8002 and 9002. OR you can change the ports used by WideFS instead (both WideServer and Wideclient). BUT I think really it is more likely that you have installed something else on FSX and not on P3D which is doing it.? Of course, you may have the firewall in Windows set to stop FSX.EXE but not Prepar3D.exe? I have installed the migration tool for Prepar3d to install FSX add-ons into Prepar3D. Could it be, that this package could block the connection?With kind regards, I would have thought it more likely that such a tool would mess up P3D, not FSX. Why should it do anything to FSX? Pete
simonvreeke Posted March 11, 2014 Author Report Posted March 11, 2014 Hi Pete, can you tell me where can I find the SimConnect.xml? Here are the logfiles: 1. wideclientlog ********* WideClient Log [version 6.999b] Class=FS98MAIN *********Date (dmy): 10/03/14, Time 17:59:07.474: Client name is FLIGHTSIM-PC 94 LUA: "D:\Downloads\Initial.LUA": not found 110 Attempting to connect now 110 Trying to locate server: Need details from Server Broadcast 110 Failed to connect: waiting to try again 2110 Attempting to connect now 4922 New Client Application: "Prosim737" (Id=3664) 24110 Server = ERAZERSIM 24110 Trying TCP/IP host "ERAZERSIM" port 8002 ... 24110 ... Okay, IP Address = 192.168.0.140 45125 Error on client pre-Connection Select() [Error=10060] Connection timed out 45125 Ready to try connection again 47172 Attempting to connect now 47172 Giving up server, looking for another! 47172 Server = ERAZERSIM 47172 Trying TCP/IP host "ERAZERSIM" port 8002 ... 47172 ... Okay, IP Address = 192.168.0.140 70235 Server = ERAZERSIM 70235 Trying TCP/IP host "ERAZERSIM" port 8002 ... 70235 ... Okay, IP Address = 192.168.0.140 93235 Giving up server, looking for another! 93235 Server = ERAZERSIM 93235 Trying TCP/IP host "ERAZERSIM" port 8002 ... 93235 ... Okay, IP Address = 192.168.0.140 116235 Server = ERAZERSIM 116235 Trying TCP/IP host "ERAZERSIM" port 8002 ... 116235 ... Okay, IP Address = 192.168.0.140 139235 Giving up server, looking for another! 139235 Server = ERAZERSIM 139235 Trying TCP/IP host "ERAZERSIM" port 8002 ... 139235 ... Okay, IP Address = 192.168.0.140 162297 Server = ERAZERSIM 162297 Trying TCP/IP host "ERAZERSIM" port 8002 ... 162297 ... Okay, IP Address = 192.168.0.140 185297 Giving up server, looking for another! 185297 Server = ERAZERSIM 185297 Trying TCP/IP host "ERAZERSIM" port 8002 ... 185297 ... Okay, IP Address = 192.168.0.140 208297 Server = ERAZERSIM 208297 Trying TCP/IP host "ERAZERSIM" port 8002 ... 208297 ... Okay, IP Address = 192.168.0.140 231360 Giving up server, looking for another! 231360 Server = ERAZERSIM 231360 Trying TCP/IP host "ERAZERSIM" port 8002 ... 231360 ... Okay, IP Address = 192.168.0.140 254422 Server = ERAZERSIM 254422 Trying TCP/IP host "ERAZERSIM" port 8002 ... 254422 ... Okay, IP Address = 192.168.0.140 254422 Connection made okay! 291219 Received shutdown offset code = ADBC 291219 FS closing down (param=ADBC), disconnecting 291219 ********* Interim performance summary ********* 291219 Total time connected so far = 35 seconds 291219 Reception maximum so far: 29 frames/sec, 4178 bytes/sec 291219 Reception average whilst connected so far: 27 frames/sec, 3067 bytes/sec 291219 Transmission maximum so far: 13 frames/sec, 2500 bytes/sec 291219 Transmission average whilst connected so far: 11 frames/sec, 1758 bytes/sec 291219 Max receive buffer = 731, Max send depth = 6, Send frames lost = 0 291219 **************** Individual client application activity **************** 291219 Client 3664 requests: 982 (Ave 28/sec), Data: 1134193 bytes (32405/sec), Average 1154 bytes/Process 291219 *********************************************** 291344 Received shutdown offset code = ADBC 298875 Connection closed by server! 298875 Attempting to connect now 298875 Server = ERAZERSIM 298875 Trying TCP/IP host "ERAZERSIM" port 8002 ... 298875 ... Okay, IP Address = 192.168.0.140 321922 Giving up server, looking for another! 2 wideserver fsx ********* WideServer.DLL Log [version 7.929] *********Blocksize guide = 8192 (double allowed)Date (dmy): 10/03/14, Time 17:59:58.866: Server name is ERAZERSIM 15094 Initialising TCP/IP server 15094 Initialising UDP/IP server 16016 Broadcasting service every 1000 mSecs 119625 Closing down now ...Memory managed: Offset records: 61 alloc, 60 freeRead buffer usage: 0 alloc, 0 free, max in session: 0Write buffer usage: 0 alloc, 0 free, max in session: 0Throughput maximum achieved: 0 frames/sec, 0 bytes/secThroughput average achieved for complete session: 0 frames/sec, 0 bytes/sec********* Log file closed *********3. wideserver prepar3d ********* WideServer.DLL Log [version 7.929] *********Blocksize guide = 8192 (double allowed)Date (dmy): 10/03/14, Time 18:03:41.398: Server name is ERAZERSIM 15329 Initialising TCP/IP server 15329 Initialising UDP/IP server 16032 Broadcasting service every 1000 mSecs 26750 Incoming connection Accepted ok (skt=11600) TCP 26813 Connected to computer "FLIGHTSIM-PC" running WideClient version 6.999 (skt=11600) TCP 63547 Auto send stopped before sending all data (0 of 47 sent), Error=10013 (IP=255.255.255.255) UDP 70094 Close signalled to clients 71188 Closing down now ...Memory managed: Offset records: 228 alloc, 227 freeRead buffer usage: 275 alloc, 275 free, max in session: 1Write buffer usage: 1932 alloc, 1932 free, max in session: 1Throughput maximum achieved: 30 frames/sec, 4143 bytes/secThroughput average achieved for complete session: 6 frames/sec, 741 bytes/secAverage receive rate from "FLIGHTSIM-PC": 6 frames/sec, 1221 bytes/sec********* Log file closed ********* The clientlog stayed running from the moment I have started fsx, closing fsx, starting prepar3d until closing prepar3d Pete I also have tried starting fsx with firewalls disabled with the same result. I thought that the Estonia migration tool could possibly cause the problem is that is something I also recently installed. Tomorrow I will give it a try with other port numbers. With kind regards, Simon
Pete Dowson Posted March 12, 2014 Report Posted March 12, 2014 can you tell me where can I find the SimConnect.xml? Same folder as your FSX.cfg, something like C:\<user>\AppData\Roaming\Microsoft\FSX. Whilst you are there check also the DLL.XML and EXE.XML files, tell me what other FSX applications are being loaded. The logs merely show wat we know, that the FSX access is being blocked. If it isn't some sort of firewall I can only think it is some other application. The server just isn't receiving anything at all from the client. Since the code in FSUIPC4 is identical in both P3D and FSX -- they are the same modules and the Server part is 100% the same -- it must be something else installed. The clientlog stayed running from the moment I have started fsx, closing fsx, starting prepar3d until closing prepar3d Yes, I note that the Client log shows many attempts to connect to "ERAZERSIM", IP Address = 192.168.0.140 but only the last one the successful one (to P3D I assume). The closing summary confirms this: 291219 ********* Interim performance summary ********* 291219 Total time connected so far = 35 seconds 291219 Reception maximum so far: 29 frames/sec, 4178 bytes/sec 35 seconds before 291.219 seconds would approximate to timestamp 256.xxx, which relates okay to that last connection attempt: 254422 Server = ERAZERSIM 254422 Trying TCP/IP host "ERAZERSIM" port 8002 ... 254422 ... Okay, IP Address = 192.168.0.140 254422 Connection made okay! Pete
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now