Steku2 Posted December 8, 2020 Report Share Posted December 8, 2020 I can't convince WideClient to connect with FSUIPC7 and MFS2020. Wired LAN. MSF2020 running, flight loaded. FSUIPC7 working as expected on the server side. FSUIPC and WideFS registered via FSUIPC7 installer. Windows Defender firewall disabled on client and server. WideFS function enabled in FSUIPC7. Server name "BEATA-PIOTR". Issue persisting no matter if no server name specified, server name specified or IP specified (parameter names as specified in the manual). Both PC with Windows 10. I checked on 2 other PC clients (Win7 and Win10) - WideFS connects. So seems like client side issue. Personal data in the logs below replaced by ******************* FSUIPC7.log ********* FSUIPC7, Version 7.0.0 (4th November 2020) by John Dowson ********* No registry entries found for MSFS - setting paths from APPDATA env variable Checking for FS path in 'C:\Users\steck\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt' FS path found = P:\FS2020\Packages\ WebSocket server found: C:\Users\steck\AppData\Roaming\Microsoft Flight Simulator\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe Windows 10 Home 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0) Reading options from "C:\Users\steck\AppData\Roaming\Microsoft Flight Simulator\FSUIPC7\FSUIPC7.ini" Checking the Registrations now ... User Name="*******************" User Addr="*******************" FSUIPC7 Key is provided WideFS7 Key is provided 156 System time = 08/12/2020 19:27:12 156 FLT UNC path = "C:\Users\steck\AppData\Roaming\Microsoft Flight Simulator\" 187 ------------------------------------------------------------------- 218 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) 265 FS UNC path = "P:\FS2020\Packages\" 281 ---------------------- Joystick Device Scan ----------------------- 281 ------------------------------------------------------------------- 359 LogOptions=00000000 00000001 3218 Simulator detected 8281 SimConnect_Open succeeded 8296 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3) 8296 MSFS version = 11.0.282174.999 8296 Initialising SimConnect data requests now 8328 C:\Users\steck\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT 8328 SimObjects\Airplanes\Asobo_C172sp_classic\aircraft.CFG 8343 User Aircraft ID 1 supplied, now being used 8359 Aircraft loaded: running normally now ... 8734 Aircraft="Cessna Skyhawk Asobo" 8750 System time = 08/12/2020 19:27:21, Simulator time = 10:25:10 (09:25Z) 11812 Starting WideServer now ... 14718 -------------------- Starting everything now ---------------------- 14796 LUA.1: Could not open HID 14859 LUA.2: Could not open HID WideClient.ini ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=77,197,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=1000,1000 PollInterval=2000 Port2=9002 ReconnectMinutes=0 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ServerName=BEATA-PIOTR Protocol=TCP ; ----------------------------------------------- [User] Log=Errors+ ; =============================================== [Sounds] Path=C:\Users\Test\Desktop\WideFS7\Sound\ Device1=Primary Sound Driver Device2=Lautsprecher (Realtek(R) Audio) WideClient.log ********* WideClient Log [version 7.159] Class=FS98MAIN ********* Date (dmy): 08/12/20, Time 19:43:06.866: Client name is PRIMETAB 454 Attempting to connect now 454 LUA: "C:\Users\Test\Desktop\WideFS7\Initial.LUA": not found 500 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 500 ... Okay, IP Address = 192.168.0.7 2547 Error on client pre-Connection Select() [Error=10061] Connection refused 2547 Ready to try connection again 3547 Attempting to connect now 61969 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 61985 ... Okay, IP Address = 192.168.0.7 123516 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 123516 ... Okay, IP Address = 192.168.0.7 185110 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 185110 ... Okay, IP Address = 192.168.0.7 246688 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 246688 ... Okay, IP Address = 192.168.0.7 308250 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 308250 ... Okay, IP Address = 192.168.0.7 369813 Trying TCP/IP host "BEATA-PIOTR" port 8002 ... 369813 ... Okay, IP Address = 192.168.0.7 424344 ****** End of session performance summary ****** 424344 Total time connected = 0 seconds 424344 Reception maximum: 0 frames/sec, 0 bytes/sec 424344 Transmission maximum: 0 frames/sec, 0 bytes/sec 424344 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 424344 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* I would appreciate your advice. Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 8, 2020 Report Share Posted December 8, 2020 11 minutes ago, Steku2 said: I can't convince WideClient to connect with FSUIPC7 and MFS2020. The Client log shows the reason: 2547 Error on client pre-Connection Select() [Error=10061] Connection refused Seems you have a firewall protecting access to your MSFS PC. You need to either turn it off or create FSUIPC7 or WideClient as an exception. Sorry, I can't say how to do that specifically. I never have any firewalls on any of my sim PCs. they are just a nuisance. Note that It's also possibly, but less likely, that the protection is on your client PC. Pete Link to comment Share on other sites More sharing options...
Steku2 Posted December 8, 2020 Author Report Share Posted December 8, 2020 Strange thing... I tested from 2 other PCs. It connected. Then I returned to my main client PC and enabled the Windows Defender FW on it. And WideFS connected! I believe you just triggered some telephatic command to the WideFS and it obeyed 😉 Thank you for your immediate response! I can now continue with configuring Pilot2ATC... Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 8, 2020 Report Share Posted December 8, 2020 3 hours ago, Steku2 said: Then I returned to my main client PC and enabled the Windows Defender FW on it. And WideFS connected! Strange. But as long as it worked! 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