Been trying to migrate to FSX but have encountered a fundamental problem, SimConnect won't communicate with AI Traffic.exeon either the Server or the Client on the LAN. Initially I thought the problem had something to do with ASA and therefore made a postin that Forum where Jim Skorna was kind enough to follow through things until finally, it became obvious it was a SimConnect issue.http://forums1.avsim.net/index.php?showtopic=260699In brief:2 PCs on LAN/Router.2 PCs each assigned a static IP addressAll relevant folders shared with Total Control permissionsNetwork comms very fast and working perfectly.FSX installed followed by SP1 & SP2ASA reported initially that it couldn't find a working simconnect connection.Installed FSX SDK followed by FDK Sp1 and the SP2.Reinstalled SimConnect included on SDK Sp2 on server and client which resulted in ASA no longer giving any error messages, however it failedto communicate with the FSX as did AI Traffic.exe when run on the clientor the server.SimConnect.cfg, ini and xml files in the right directories. Linked post abovehas full details.So I guess this forum is my last hope and live in the hope may be someone in this Forum may know the answer.ThanksJoaquin

If you use Vista, sometimes the Windows firewall blocking SimConnect comms is the culprit. You can try manually adding the following exception to the Windows firewall:Microsoft.FlightSimulator.SimConnect.dllTo start with, you have to have the Windows FSX SDK and all SDK updates through SP2 installed. If you try to use the SimConnect SDK that came with RTM or SP1 it'll cause problems. You need the SP2 (or Acceleration if that's installed) update TO THE SDK. You'll need to copy or write down the full path to this dll file, which is normally in the SDK directory on your FS drive. G is my FS drive, so the file is located at: G:\FSX SDK\SDK\Core Utilities\SimConnect SDK\lib\managed\Microsoft.FlightSimulator.SimConnect.dllTo add the exception to the firewall, you open control panel, then Windows Firewall, in the left column click on "Allow a program through Windows Firewall," then exceptions tab, and click on the "Add program" button.Paste or type in the complete path to the dll file in the "Path" dialog box. Note that you cannot use the "Browse" feature as it only looks for .exe and .com files. Click OK, and ensure that the checkbox next to the dll is checked in the exceptions tab. Close the window out, and reboot.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO