sbclark Posted June 4, 2018 Report Share Posted June 4, 2018 Hi Pete, I’ve been using FSUIPC and WideFS for years, but after installing a new router on my network, and a Win10 Spring update on my client PC running Pilot2ATC and Wide FS, Wide FS no longer connects. Some basic system configuration information: -Win10 on both the server and client PC -Running P3D v4.1 -Running ActiveSky on client (it works correctly) - Running Pilot2ATC on client (can’t connect without WideFS) -Can look at files on both PC ‘s from either PC – network works, or seems to! I worked well prior to these two changes. If you have any suggestions to offer, I would love to hear them? Bill Clark Below are three log files: WideClient.log: ********* WideClient Log [version 7.146] Class=FS98MAIN ********* Date (dmy): 04/06/18, Time 09:14:03.704: Client name is MOOSE-PC 171 LUA: "C:\WideFS\WideFS\Initial.LUA": not found 187 Attempting to connect now 187 Trying to locate server: Need details from Server Broadcast 187 Failed to connect: waiting to try again 1218 Attempting to connect now 6296 Server = KILLER-PC 6296 Trying TCP/IP host "KILLER-PC" port 8002 ... 6296 ... Okay, IP Address = 192.168.1.57 27312 Error on client pre-Connection Select() [Error=10060] Connection timed out 27312 Ready to try connection again 28328 Attempting to connect now 28328 Giving up server, looking for another! 28328 Server = KILLER-PC 28328 Trying TCP/IP host "KILLER-PC" port 8002 ... 28328 ... Okay, IP Address = 192.168.1.57 50406 Server = KILLER-PC 50406 Trying TCP/IP host "KILLER-PC" port 8002 ... 50406 ... Okay, IP Address = 192.168.1.57 72468 Giving up server, looking for another! 72468 Server = KILLER-PC 72468 Trying TCP/IP host "KILLER-PC" port 8002 ... 72468 ... Okay, IP Address = 192.168.1.57 94546 Server = KILLER-PC 94546 Trying TCP/IP host "KILLER-PC" port 8002 ... 94546 ... Okay, IP Address = 192.168.1.57 116593 Giving up server, looking for another! 116593 Server = KILLER-PC 116593 Trying TCP/IP host "KILLER-PC" port 8002 ... 116593 ... Okay, IP Address = 192.168.1.57 138609 Server = KILLER-PC 138609 Trying TCP/IP host "KILLER-PC" port 8002 ... 138609 ... Okay, IP Address = 192.168.1.57 160625 Giving up server, looking for another! 160625 Server = KILLER-PC 160625 Trying TCP/IP host "KILLER-PC" port 8002 ... 160625 ... Okay, IP Address = 192.168.1.57 182671 Server = KILLER-PC 182671 Trying TCP/IP host "KILLER-PC" port 8002 ... 182671 ... Okay, IP Address = 192.168.1.57 204718 Giving up server, looking for another! 204718 Server = KILLER-PC 204718 Trying TCP/IP host "KILLER-PC" port 8002 ... 204718 ... Okay, IP Address = 192.168.1.57 226796 Server = KILLER-PC 226796 Trying TCP/IP host "KILLER-PC" port 8002 ... 226796 ... Okay, IP Address = 192.168.1.57 248843 Giving up server, looking for another! 248843 Server = KILLER-PC 248843 Trying TCP/IP host "KILLER-PC" port 8002 ... 248843 ... Okay, IP Address = 192.168.1.57 270890 Server = KILLER-PC 270890 Trying TCP/IP host "KILLER-PC" port 8002 ... 270890 ... Okay, IP Address = 192.168.1.57 292921 Giving up server, looking for another! 292921 Server = KILLER-PC 292921 Trying TCP/IP host "KILLER-PC" port 8002 ... 292921 ... Okay, IP Address = 192.168.1.57 314984 Server = KILLER-PC 314984 Trying TCP/IP host "KILLER-PC" port 8002 ... 314984 ... Okay, IP Address = 192.168.1.57 337000 Giving up server, looking for another! 337000 Server = KILLER-PC 337000 Trying TCP/IP host "KILLER-PC" port 8002 ... 337000 ... Okay, IP Address = 192.168.1.57 359062 Server = KILLER-PC 359062 Trying TCP/IP host "KILLER-PC" port 8002 ... 359062 ... Okay, IP Address = 192.168.1.57 381109 Giving up server, looking for another! 381109 Server = KILLER-PC 381109 Trying TCP/IP host "KILLER-PC" port 8002 ... 381109 ... Okay, IP Address = 192.168.1.57 389187 ****** End of session performance summary ****** 389187 Total time connected = 0 seconds 389187 Reception maximum: 0 frames/sec, 0 bytes/sec 389187 Transmission maximum: 0 frames/sec, 0 bytes/sec 389187 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 389187 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* WideClient0.log: ********* WideClient Log [version 7.146] Class=FS98MAIN ********* Date (dmy): 04/06/18, Time 09:09:06.683: Client name is MOOSE-PC 156 LUA: "C:\WideFS\WideFS\Initial.LUA": not found 234 Attempting to connect now 234 Trying to locate server: Need details from Server Broadcast 234 Failed to connect: waiting to try again 1234 Attempting to connect now 2281 Server = KILLER-PC 2281 Trying TCP/IP host "KILLER-PC" port 8002 ... 2281 ... Okay, IP Address = 192.168.1.57 23312 Error on client pre-Connection Select() [Error=10060] Connection timed out 23312 Ready to try connection again 24375 Attempting to connect now 24375 Giving up server, looking for another! 24375 Server = KILLER-PC 24375 Trying TCP/IP host "KILLER-PC" port 8002 ... 24375 ... Okay, IP Address = 192.168.1.57 39437 ****** End of session performance summary ****** 39437 Total time connected = 0 seconds 39437 Reception maximum: 0 frames/sec, 0 bytes/sec 39437 Transmission maximum: 0 frames/sec, 0 bytes/sec 39437 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 39437 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* FSUIPC5.log: ********* FSUIPC5, Version 5.131 (17th May 2018) by Pete Dowson ********* Running inside Prepar3D v4 Module base=7FFA39990000 Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0) Prepar3D.exe version = 4.1.7.22841 Reading options from "C:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini" Checking the Registrations now ... User Name="Bill Clark" User Addr="sbclark-ext@cox.net" FSUIPC5 Key is provided WideFS7 Key is provided 0 System time = 04/06/2018 09:12:55 16 FLT UNC path = "\\KILLER-PC\Prepar3D v4 Files\" 16 Using PDK events 16 Using DialogMode 32 FS UNC path = "\\KILLER-PC\Prepar3D v42\" 94 ---------------------- Joystick Device Scan ----------------------- 94 Product= HOTAS Cougar Joystick 94 Manufacturer= Thrustmaster 94 Vendor=044F, Product=0400 (Version 1.16) 110 GUIDs returned for product: VID_044F&PID_0400: 110 GUID= {5FA1F0D0-E1B8-11E7-8001-444553540000} 110 Details: Btns=28, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X65535,Y65535,Z255 110 ------------------------------------------------------------------- 125 Device acquired for use: 125 Joystick ID = 0 (Registry okay) 125 0=Thrustmaster HOTAS Cougar 125 0.GUID={5FA1F0D0-E1B8-11E7-8001-444553540000} 125 ------------------------------------------------------------------- 141 LogOptions=00000000 00000001 141 ------------------------------------------------------------------- 141 SimConnect_Open succeeded: waiting to check version okay 141 Opened separate AI Traffic client okay 13688 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.1.7.22841 (SimConnect: 4.1.0.0) 13688 Initialising SimConnect data requests now 13688 FSUIPC Menu entry added 13688 ... Using Prepar3D with Academic License 13703 \\KILLER-PC\Prepar3D v4 Files\KSAN F-16.fxml 13719 \\KILLER-PC\Prepar3D v42\SimObjects\Airplanes\F-16AM\F-16 F100 CAT-I.air 55235 Loading Complete ... 55875 User Aircraft ID 2 supplied, now being used 55875 Aircraft loaded: running normally now ... 56141 System time = 04/06/2018 09:13:51, Simulator time = 09:13:09 (16:13Z) 56141 Aircraft="Lockheed Martin F-16AM - Orange Demo" 57141 -------------------- Starting everything now ---------------------- 57141 ASN active function link set 57141 Ready for ActiveSky WX radar with additional data 58282 Advanced Weather Interface Enabled 461828 Sim stopped: average frame rate for last 406 secs = 30.0 fps 461828 Max AI traffic was 8 aircraft (Deleted 0) 464172 === Closing session: waiting for DLLStop to be called ... 480578 === DLLStop called ... 480578 === Closing external processes we started ... 481578 === About to kill any Lua plug-ins still running ... 481719 === Closing global Lua thread 482735 === About to kill my timers ... 482938 === Restoring window procs ... 482938 === Unloading libraries ... 482938 === stopping other threads ... 482938 === ... Button scanning ... 483032 === ... Axis scanning ... 483141 === Releasing joystick devices ... 483141 === Freeing macro memory 483141 === Removing any offset overrides 483141 === Closing all WideFS threads 484485 === Clearing any displays left 484485 === NOTE: not calling SimConnect_Close ... 484485 === AI slots deleted! 484485 === Freeing button memory ... 484485 === Closing my Windows ... 484485 === Freeing FS libraries ... 485485 === Closing devices ... 485485 === Closing the Log ... Bye Bye! ... 485485 System time = 04/06/2018 09:21:00, Simulator time = 09:19:54 (16:19Z) 485485 *** FSUIPC log file being closed Minimum frame rate was 30.0 fps, Maximum was 36.6 fps Average frame rate for running time of 406 secs = 30.0 fps Maximum AI traffic for session was 8 aircraft Memory managed: 190 Allocs, 189 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 4, 2018 Report Share Posted June 4, 2018 FSUIPC5.Log is not at all relevant. You haven't shown the WideServer.LOG though! 14 minutes ago, sbclark said: 24375 Server = KILLER-PC 24375 Trying TCP/IP host "KILLER-PC" port 8002 ... 24375 ... Okay, IP Address = 192.168.1.57 Is 192.1168.1.57 the correct IP address for your P3D4 PC? 14 minutes ago, sbclark said: I worked well prior to these two changes. Well, the router could conceivably be causing the problem but it is most unikely. The most likely thing is the Windows Firewall, which has probably got changed by the Windows update. Check it at both ends. 14 minutes ago, sbclark said: Can look at files on both PC ‘s from either PC – network works, or seems to! Shared folders is a Windows Exploer link, not a Wideclient / FSUIPC link. Firewalls apply to specific programs. WideFS does not use shared folders. Pete Link to comment Share on other sites More sharing options...
sbclark Posted June 4, 2018 Author Report Share Posted June 4, 2018 Pete, Thanks so far. After exploring the firewalls on both the Server side and Client side, I discovered that by ONLY turning OFF the “Public” Firewall in the Server PC, I can connect the WideFS to P3D 100% of the time, no matter what the other settings are. This simple matrix, I hope, explains it pretty well: Server Firewall Private ON or OFF ON or OFF Public OFF ON Client Firewall Private ON or OFF ON or OFF Public ON or OFF ON or OFF WideFS Connect? YES NO I’m not quite sure how I can fix this other than turning OFF the Server Public Firewall. I would rather not have to do that, any ideas? The Server IP address is correct 192.168.1.57 Bill Clark Below is the wide server log file you requested. WideServer.log ********* WideServer.DLL Log [version 7.075] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 04/06/18, Time 09:13:52.267: Server name is KILLER-PC 15266 Initialising TCP/IP server 15266 Initialising UDP/IP server 16031 Broadcasting service every 1000 mSecs 427094 Closing down now ... Memory managed: Offset records: 190 alloc, 188 free Read buffer usage: 0 alloc, 0 free, max in session: 0 Write buffer usage: 0 alloc, 0 free, max in session: 0 Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 5, 2018 Report Share Posted June 5, 2018 10 hours ago, sbclark said: I’m not quite sure how I can fix this other than turning OFF the Server Public Firewall. I would rather not have to do that, any ideas? I don't know why it thinks your own PC Network is Public. Maybe your Network is defined incorreectly? I think Public/Private differentiation is not just between Internet and Local, but also between, for instance, different departments in a Company network. But I think you have to tell the Firewall that it should allow WideClient.exe and/or Prepare3D.exe. But I'm afraid I can't tell you how to do that -- I've never allowed the Windows firewall to operate on any of my PCs (my Network has 10 PCs -- 7 for the Cockpit alone) as it's a pain I don't want to endure. I do use third party protection (Avast at present, the free version), and I believe that, plus the good protection also provided by the Router, is enough. So, sorry, you'll need to Google it. 10 hours ago, sbclark said: Below is the wide server log file you requested. Yes, that confirms that no sign of the Client came through. Pete Link to comment Share on other sites More sharing options...
sbclark Posted June 5, 2018 Author Report Share Posted June 5, 2018 Pete, Looks like I'm off to Google Land! Thanks, Bill Clark Link to comment Share on other sites More sharing options...
sbclark Posted June 6, 2018 Author Report Share Posted June 6, 2018 Pete, I discovered that my Server and Client were setup on "Private" networks, so no issue there.......but still had a problem. However, I just happen to stumble on this video that solved my mystery. It is approximately 11 minutes long and the critical part that fixed my issue is when I enabled "Choose media Streaming options" at the 3:39 mark. https://www.youtube.com/watch?v=uNeo7O6ImAo In the video it also showed how to change from Private to Public or vice versa. Bill Clark Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 6, 2018 Report Share Posted June 6, 2018 1 hour ago, sbclark said: However, I just happen to stumble on this video that solved my mystery. It is approximately 11 minutes long and the critical part that fixed my issue is when I enabled "Choose media Streaming options" at the 3:39 mark. Interesting. I've never met that option! Thanks for the feedback. Pete Link to comment Share on other sites More sharing options...
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