yair1956 Posted April 5, 2016 Report Share Posted April 5, 2016 Hello, Never had any issue before, so I don't know how to approach it, however, I had a fresh install Wind7 and FSX on 2 Rigs, have no issue of communication between the Master Rig & the Client Rig they both "see" and "talk" to each other, but when lunching Wide Client I get the "Waiting for a connection" message and that's it. I tried on a different Client machine but go the same results. Any idea Thanks in advance Yair Link to comment Share on other sites More sharing options...
DEN19 Posted April 7, 2016 Report Share Posted April 7, 2016 Have you added the client pc name to the list in the FSUIPC.ini file? Here is mine as an example [ClientNames]1=Q94502=HPLAPTOP3=I74=denlaptop Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 7, 2016 Report Share Posted April 7, 2016 Hi, was the client pc as well fresh installed? Make sure that the WideClient.ini file contains the correct PC name or IP for the server, if that i used. e.g. the server name here is TSR-DEV, so the client PC will look for that PC as server only. Same works with e.g. my server address 192.168.1.119, ServerIPAddr=192.168.1.119 [Config]ServerName=TSR-DEV This is from Pete's WideFS User Guide.pdf Okay. Once you have the same Workgroup names throughout, and either no firewall or exceptions properly made, everything should work ... ... However, if you find the connection is still not happening, or you have more than one Server and it is connecting to the wrong one, then you will need to add these lines to the [Config] section of the WideClient.ini file (add the [Config] section too if your ini file hasn‘t even got one!): ServerName=NameOfServer Protocol=TCP The protocol can be UDP instead, but that may be more problematic, so I‘d recommend sticking to TCP, especially if you are finding you need to add these lines in the first place—this does seem to indicate that there are Network problems. The ServerName is the computer name you gave to the PC on which you will be running Flight Simulator with WideServer. If you prefer you can use the Server‘s IP address instead of the name, thus: ServerIPAddr=192.168.0.3 But I‘d recommend only ever using names. The only time an explicit IP address works better is when the Broadcasts from the Server provide a bad IP address. This only seems to happen when the Network hub is a router which does odd things via "proxy" addresses. If you do specify an IP address you MUST set that specific IP address as the fixed one used in the Server PC --- you cannot then allow the Router to assign you one automatically via DHCP, as then it could change at each switch-on. More about that next (Possible Gotchas) By the way, if both Name and Address are provided in the INI file, only the latter is used. Link to comment Share on other sites More sharing options...
yair1956 Posted April 8, 2016 Author Report Share Posted April 8, 2016 tnx guys I did it all amd still nothing nada null "PC Client waiting for connection" However reviewing the connection log WideClient Log [version 6.999n] Class=FS98MAIN *********Date (dmy): 07/04/16, Time 21:06:50.360: Client name is FSX-RIG2 109 LUA: "C:\Users\FSX2\Downloads\WideFS\Initial.LUA": not found 172 Attempting to connect now 172 Trying to locate server: Protocol not yet decided 172 Failed to connect: waiting to try again 2231 Attempting to connect now 4290 Server = FSX-RIG 4431 Trying TCP/IP host "FSX-RIG" port 8002 ... 4431 ... Okay, IP Address = 192.168.5.101 25460 Error on client pre-Connection Select() [Error=10060] Connection timed out 25460 Ready to try connection again 27503 Attempting to connect now 27503 Server = FSX-RIG 27503 Trying TCP/IP host "FSX-RIG" port 8002 ... 27503 ... Okay, IP Address = 192.168.5.101 50591 Server = FSX-RIG 50591 Trying TCP/IP host "FSX-RIG" port 8002 ... 50591 ... Okay, IP Address = 192.168.5.101 73679 Server = FSX-RIG 73679 Trying TCP/IP host "FSX-RIG" port 8002 ... 73679 ... Okay, IP Address = 192.168.5.101 96768 Server = FSX-RIG 96768 Trying TCP/IP host "FSX-RIG" port 8002 ... 96768 ... Okay, IP Address = 192.168.5.101 119856 Server = FSX-RIG 119856 Trying TCP/IP host "FSX-RIG" port 8002 ... 119856 ... Okay, IP Address = 192.168.5.101 142944 Server = FSX-RIG 142944 Trying TCP/IP host "FSX-RIG" port 8002 ... 142944 ... Okay, IP Address = 192.168.5.101 166032 Server = FSX-RIG 166032 Trying TCP/IP host "FSX-RIG" port 8002 ... 166032 ... Okay, IP Address = 192.168.5.101 189120 Server = FSX-RIG 189120 Trying TCP/IP host "FSX-RIG" port 8002 ... 189120 ... Okay, IP Address = 192.168.5.101 212208 Server = FSX-RIG 212208 Trying TCP/IP host "FSX-RIG" port 8002 ... 212208 ... Okay, IP Address = 192.168.5.101 235296 Server = FSX-RIG 235296 Trying TCP/IP host "FSX-RIG" port 8002 ... 235296 ... Okay, IP Address = 192.168.5.101 258385 Server = FSX-RIG 258385 Trying TCP/IP host "FSX-RIG" port 8002 ... 258385 ... Okay, IP Address = 192.168.5.101 281473 Server = FSX-RIG 281473 Trying TCP/IP host "FSX-RIG" port 8002 ... 281473 ... Okay, IP Address = 192.168.5.101 304561 Server = FSX-RIG 304561 Trying TCP/IP host "FSX-RIG" port 8002 ... 304561 ... Okay, IP Address = 192.168.5.101 327649 Server = FSX-RIG 327649 Trying TCP/IP host "FSX-RIG" port 8002 ... 327649 ... Okay, IP Address = 192.168.5.101 350737 Server = FSX-RIG 350737 Trying TCP/IP host "FSX-RIG" port 8002 ... 350737 ... Okay, IP Address = 192.168.5.101 373825 Server = FSX-RIG 373825 Trying TCP/IP host "FSX-RIG" port 8002 ... 373825 ... Okay, IP Address = 192.168.5.101 396913 Server = FSX-RIG 396913 Trying TCP/IP host "FSX-RIG" port 8002 ... 396913 ... Okay, IP Address = 192.168.5.101 420002 Server = FSX-RIG 420002 Trying TCP/IP host "FSX-RIG" port 8002 ... 420002 ... Okay, IP Address = 192.168.5.101 443090 Server = FSX-RIG 443090 Trying TCP/IP host "FSX-RIG" port 8002 ... 443090 ... Okay, IP Address = 192.168.5.101 466178 Server = FSX-RIG 466178 Trying TCP/IP host "FSX-RIG" port 8002 ... 466178 ... Okay, IP Address = 192.168.5.101 489266 Server = FSX-RIG 489266 Trying TCP/IP host "FSX-RIG" port 8002 ... Does it mean anything ???? Reg. Yair Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 8, 2016 Report Share Posted April 8, 2016 Hi, check your firewall on the server. Link to comment Share on other sites More sharing options...
yair1956 Posted April 9, 2016 Author Report Share Posted April 9, 2016 checked, seems to be okay, however, I might miss something .... frustrated Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 9, 2016 Report Share Posted April 9, 2016 Hi, best is to show (copy and paste) your FSUIPC.ini and WideClient.ini files. Also are the basics ok, GroupName, IP and SubNetMask? Link to comment Share on other sites More sharing options...
yair1956 Posted April 10, 2016 Author Report Share Posted April 10, 2016 Sever side [General]UpdatedByVersion=4949History=F3RFO61749M6190NMB4PTInitDelayDevicesToo=NoNewInterceptTextMenu=NoUseSystemTime=NoUseMidMouseBtn=YesMouseWheelMove=NoMouseWheelTrim=NoMouseWheelTrimSpeed=1JoystickTimeout=20PollGFTQ6=YesBlankDisplays=NoFixControlAccel=NoFixMachSpeedBug=NoDeleteVehiclesForAES=YesAutoScanDevices=YesAssignJoystickIDs=YesVisibilityOptions=NoOneCloudLayer=NoCloudTurbulence=NoCloudIcing=NoGenerateCirrus=NoSuppressCloudTurbulence=NoMaxIce=3MinIce=-4UpperWindGusts=NoSuppressWindTurbulence=YesSuppressWindVariance=NoWindTurbulence=NoTurbulenceRate=1.0,5.0TurbulenceDivisor=20,20,40,40SuppressAllGusts=YesMaxSurfaceWind=0WindLimitLevel=200WindDiscardLevel=400WindAjustAltitude=NoWindAjustAltitudeBy=2000SmoothBySimTime=NoWindSmoothing=YesWindSmoothness=2WindSmoothAirborneOnly=YesPressureSmoothness=20TemperatureSmoothness=100DisconnTrimForAP=NoZeroElevForAPAlt=NoThrottleSyncAll=NoWhiteMessages=NoShowPMcontrols=NoSpoilerIncrement=512MagicBattery=YesRudderSpikeRemoval=YesElevatorSpikeRemoval=YesAileronSpikeRemoval=YesReversedElevatorTrim=NoClockSync=NoClockSyncMins=5ClearWeatherDynamics=NoOwnWeatherChanges=NoTimeForSelect=4LoadFlightMenu=NoLoadPlanMenu=NoPauseAfterCrash=NoBrakeReleaseThreshold=75SaveDataWithFlights=NoZapSound=fireworkShortAircraftNameOk=SubstringUseProfiles=YesEnableMouseLook=NoDelayedMouseLookZoom=NoAxesWrongRange=NoTCASid=FlightTCASrange=40AxisCalibration=NoDirectAxesToCalibs=NoShowMultilineWindow=YesSuppressSingleline=NoSuppressMultilineFS=NoAxisIntercepts=NoDontResetAxes=NoInitDelay=0GetNearestAirports=YesOOMcheck=YesOOMcheckInterval=10WeatherReadFactor=2WeatherRewriteSeconds=1CustomWeatherModify=NoSimConnectStallTime=1LuaRerunDelay=66Console=NoFSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0SimConnectUsed=10.0.61259.0 [JoyNames]AutoAssignLetters=No2=Mad Catz Pro Flight Rudder Pedals2.GUID={B12DE780-F68F-11E5-8001-444553540000}4=Fuel Tank Select4.GUID={FB279DB0-F750-11E5-8001-444553540000}5=DTA Rotary Encoder5.GUID={A8274D80-F823-11E5-8001-444553540000}3=Mad Catz Pro Flight Cessna Trim Wheel3.GUID={B12E0E90-F68F-11E5-8002-444553540000}1=Saitek Pro Flight Throttle Quadrant1.GUID={5A8EB900-F68E-11E5-8006-444553540000}0=Pro Flight Yoke0.GUID={5A8EB900-F68E-11E5-8005-444553540000} [Axes]PollInterval=10RangeRepeatRate=100=0X,256,D,1,0,0,01=0Y,256,D,2,0,0,02=2R,256,D,3,0,0,0 [buttons]PollInterval=25ButtonRepeat=20,102=P4,16,C65957,03=P4,17,C65956,04=P4,18,C65958,05=P4,19,C65955,06=R0,16,C66162,07=U0,16,C66162,0 [AutoSave]Next=1Interval=60Files=10SaveOnGround=NoAutoSaveEnabled=No [GPSout]GPSoutEnabled=No [GPSout2]GPSoutEnabled=No [WideServer]WideFSenabled=YesAdvertiseService=1Port=8002Port2=9002 [sounds]Path=D:\FSX\Sound\Device1=Primary Sound DriverDevice2=1 - PanasonicTV0 (AMD High Definition Audio Device)Device3=Speakers (C-Media PCI Audio Device)Device4=Realtek Digital Output(Optical) (Realtek High Definition Audio)Device5=Realtek Digital Output (Realtek High Definition Audio) [JoystickCalibration]AllowSuppressForPFCquad=YesExcludeThrottleSet=YesExcludeMixtureSet=YesExcludePropPitchSet=YesSepRevsJetsOnly=NoApplyHeloTrim=NoUseAxisControlsForNRZ=NoFlapsSetControl=0FlapDetents=NoReverserControl=66292Reverser1Control=66422Reverser2Control=66425Reverser3Control=66428Reverser4Control=66431MaxThrottleForReverser=256AileronTrimControl=66731RudderTrimControl=66732CowlFlaps1Control=66162CowlFlaps2Control=66163CowlFlaps3Control=66164CowlFlaps4Control=66165SteeringTillerControl=0MaxSteerSpeed=60Aileron=-16384,-512,512,16288Elevator=-16159,-512,512,16192Rudder=-16380,-512,512,16320Throttle1=-16384,-512,512,16256Throttle2=-16384,-512,512,16383ElevatorTrim=-16152,-512,512,16383 [ClientNames]1=FSX-Rig2 ----------------------------------------------------------------------------- Client; PLEASE SEE WideFS documentation for parameter details; ===================================================== [Config]Port=8002Window=43,44,886,589Visible=Yes ; -----------------------------------------------[user]Log=Errors+ ; =============================================== Link to comment Share on other sites More sharing options...
Thomas Richter Posted April 10, 2016 Report Share Posted April 10, 2016 Hi, your WideClient.ini file seems to be inclompete/ only 3 parameters? Just delete the WideClient.ini file and restart WideClient to create a new file. Link to comment Share on other sites More sharing options...
yair1956 Posted April 13, 2016 Author Report Share Posted April 13, 2016 okay, how about this Widclient [Config]serverName=FSX-RigButtonScanInterval=20ClassInstance=0NetworkTiming=5,1MailslotTiming=2000,1000PollInterval=2000Port=8002Port2=9002ResponseTime=18ApplicationDelay=0TCPcoalesce=NoWaitForNewData=500MaxSendQ=100OnMaxSendQ=LogNewSendScanTime=50Priority=3,1,2Window=75,81,601,493[sounds]Path=C:\Users\FSX2\Downloads\WideFS\Sound\Device1=Primary Sound DriverDevice2=Realtek Digital Output (Realtek High Definition Audio) --------------------------------------------------------------------------------------------------- Tried with 3ed computer and the something "Waiting for connection" Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 13, 2016 Report Share Posted April 13, 2016 okay, how about this Widclient [Config] serverName=FSX-Rig ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port=8002 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=75,81,601,493 [sounds] Path=C:\Users\FSX2\Downloads\WideFS\Sound\ Device1=Primary Sound Driver Device2=Realtek Digital Output (Realtek High Definition Audio) --------------------------------------------------------------------------------------------------- Tried with 3ed computer and the something "Waiting for connection" If you speciffy the Server Name (or, better, the IP address) you need also to specify the Potoocol, as it clearly tells you in the documentation. This is because you are effectively telling it to ignore the broadcast information which would otherwise instruct it. Both WideClient and WideServer produce logs which may contain diagnostic information. Have you bothered to look at those? That's what they are for, to help! Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 13, 2016 Report Share Posted April 13, 2016 Have you added the client pc name to the list in the FSUIPC.ini file? Here is mine as an example [ClientNames] 1=Q9450 2=HPLAPTOP 3=I7 4=denlaptop You never need to add client names yourself, and you shouldn't edit that section. The clients are listed when detected by the server, and the numbers need to stay as assigned because they are used to identify button presses from the clients in Button assignments. Pete Link to comment Share on other sites More sharing options...
yair1956 Posted April 13, 2016 Author Report Share Posted April 13, 2016 ..okay Problem solved (in away) I turned the Firewall Home or work (privet) netrwork off and wallah, everything is conected ...not sure if and how I compremised security but the client & server are communication Reg all Yair Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 13, 2016 Report Share Posted April 13, 2016 ..okay Problem solved (in away) I turned the Firewall Home or work (privet) netrwork off and wallah, everything is conected ...not sure if and how I compremised security but the client & server are communication Firewalls are always a problem. If you are concerned you can make Wideclient an exception somewhere, but if you have a good security setting on your router that should keep the outside world off. Having firewalls between your own computers on your own Network always seems a bit over the top to me -- if the router is accessible to the whole network in any case I don't see how a firewall between them helps. It's just a nuisance. 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