Miguel Frias Posted July 30, 2015 at 09:26 PM Posted July 30, 2015 at 09:26 PM Hello, I've been flying for years now with my main FS9 computer and a side laptop using WideFS. They have always been in a local network and configured with the basics. Both have Windows XP SP3 I recently moved but brought everything along and the same setup. And... I have had it working for about 2 months. The only difference was that the laptop was now connected via Wireless instead of fixed cable. Nevertheless I've tried with a small switch and the problem persists. And what is the problem? Well I can't get WideFS to work. When I open WideClient, it opens the small window as usual but on the FS9 window it always says "waiting for clients". The laptop has internet, web, local shares, TCP/IP is working, I can ping servers and all. The laptop is using account Administrator. If I start WideClient with right-click RunAs, Administrator but with the "Protect my computer and data from unauthorized program activity" it will get FS9 to detect one client, but then all applications that use WideFS say it has a fishy protocol and it won't work. I've turned firewall off: still the same I've turned McAfee antivirus off: still the same The WideClient.ini config (which has never changed) is: ; PLEASE SEE WideFS docomeentation for parameter details ; ===================================================== [Config] ServerIPAddr=192.168.1.10 Port=8002 Window=0,701,444,37 Visible=Yes ButtonScanInterval=20 Cl[Mod - Happy Thoughts]Instance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 [Sounds] Path=C:\Docomeents and Settings\Administrator\Desktop\WideFS\Sound\ Device1=Primary Sound Driver Device2=SigmaTel Audio Device3=C-Media USB Headphone Set Now... can anyone solve the mystery? Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Miguel Frias Posted July 31, 2015 at 08:36 PM Author Posted July 31, 2015 at 08:36 PM Ok, I managed to solve it myself. I don't know how but the line "Protocol=TCP" simply vanished from the configuration file. As soon as I added it, magic occurred. Miguel Frias Senior Instructor (I3) & Certified Pilot (P4), ZLA I-11 graduate Portugal vACC Training Director (ACCPT2), VATEUD Operations Director (VATEUD8) Portugal vACC, VATEUD, VATSIM Link to comment Share on other sites More sharing options...
Recommended Posts