I cannot get any communication between the Server and Client PCs.The AI Traffic program opens and shuts down immediately (so test failed).I am hitting my head to try to find out what is wrong.So here are the definitions and settings for this connection.First the server is Windows 7 64 bits (ultimate)The client is Vista 32 bitsThe ASA has been installed on the client 2 years ago and worked perfectly with XP.I now have a new mobo and CPU. (no I5, 7 or 9 Intel)So I installed FSX De Luxe then Accelerator. I executed the SDK installations from the De Luxe and Accelerator.On the server:Simconnect.xml in .../.../AppData/Roaming/Microsoft/FSX<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="SimConnect" version="1,0"><Descr>SimConnect Server Configuration</Descr><Filename>SimConnect.xml</Filename><Disabled>False</Disabled><SimConnect.Comm><Disabled>False</Disabled><Protocol>IPv4</Protocol><Scope>global</Scope><MaxClients>64</MaxClients><Address>192.168.1.3</Address><Port>500</Port><MaxRecvSize>4096</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm><SimConnect.Comm><Disabled>False</Disabled><Protocol>Auto</Protocol><Scope>local</Scope></SimConnect.Comm></SimBase.Document>Simconnect.ini in My Documentrs/Flight Simulator X Files[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:\simconnect%03u.log;file_next_index=0;file_max_index=9On the client:Simconnect.cfg in Program Files/HiFi/ASA/SimconnectFiles[simConnect]Protocol=IPv4Address=192.168.1.3Port=500MaxReceiveSize=4096DisableNagle=0--------------------------------------------------------------------------------------------------------------------------I checked the master address and it is 192.168.1.3 (the client is 192.168.1.2)IPv4 defined both sides.Microsoft Firewall used both PCs.On server (W7) Port 500 defined as ASA access in allowed programs, protocol TCP. Also FSX is checked with Port 500.On client (Vista) Port 500 defined for FSX in Exception list and checked. . An entry Active Sky X WX Engine is also defined and checked but with a path to the Program Files (no port defined and no way to define it, only a path).Both PCs are defined in Workgroup network.I have mapped the shared files (Flight Simulator X files, AppData/Roaming/Microsoft/FSX, and My Documents/Flight Simulator X Files. I can access by both PCs these files and write in them through Explorer.On the client the registeries show for FSXAppDataPath Y:\ FSXPath Z:\ No indications for the paths, no name, nothing. The Y and Z are the mapping for the correct files.Oh yes: UAC disabled on both PCs.Still something is wrong and at this moment I have no idea what it is.Can someone help me to show where I should now look or do ?

Hi Roger,The first thing to note is that under Win 7 the default Workgroup name is different than what we all are used to under previous operating systems. What this means is that different computers that belong to different workgroups cannot communicate across a network. So you need to change the Win 7 computer workgroup name to the same name as the Vista computer. Then re-boot both computers and see if the Traffic utility connects to FSX and stays running.

Hi Roger,The first thing to note is that under Win 7 the default Workgroup name is different than what we all are used to under previous operating systems. What this means is that different computers that belong to different workgroups cannot communicate across a network. So you need to change the Win 7 computer workgroup name to the same name as the Vista computer. Then re-boot both computers and see if the Traffic utility connects to FSX and stays running.

Jim,I followed your instructions but it did not help. That doesn't surprise me. The default HOMEGROUP cannot communicate accross a network. Name Workgroup should be able to communicate. Still I change the names on both PCs to FSnetwork. Traffic utility starts and stops immediately.What else can I do now ?

Hi Roger,The first thing to note is that under Win 7 the default Workgroup name is different than what we all are used to under previous operating systems. What this means is that different computers that belong to different workgroups cannot communicate across a network. So you need to change the Win 7 computer workgroup name to the same name as the Vista computer. Then re-boot both computers and see if the Traffic utility connects to FSX and stays running.

Jim,I am able to fetch a flight plan from ASA into the FSX Files folder. So communication between PCs is good.

Hi Roger,The first thing to note is that under Win 7 the default Workgroup name is different than what we all are used to under previous operating systems. What this means is that different computers that belong to different workgroups cannot communicate across a network. So you need to change the Win 7 computer workgroup name to the same name as the Vista computer. Then re-boot both computers and see if the Traffic utility connects to FSX and stays running.

Jim,I am on the trail of what is going wrong.the msg: " A network error occured while attempting top read from the file C:/.../.../... .../Simconnect_SP1a.msi"is due to multiple install of the msi. So I deleted all SDK from the server and the client. Then I reinstalled the SDK on the server and executed the msi (from de luxe then from Acceleration) on the client. Now I get some connection. But not fully. I still have an error when executing the traffic test: "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail."I will work on that now or tomorrow morning (Belgian time).

Hi Roger,The first thing to note is that under Win 7 the default Workgroup name is different than what we all are used to under previous operating systems. What this means is that different computers that belong to different workgroups cannot communicate across a network. So you need to change the Win 7 computer workgroup name to the same name as the Vista computer. Then re-boot both computers and see if the Traffic utility connects to FSX and stays running.

Jim,I finally succeeded to make ASA work.To make a big story a short one, I finally had to restore the whole sytem from a Acronis back-up done last week. I also needed to execute SimConnect.MSI and ConfigSDK.exe.Now FSUIPC4 (which ASA don't care) and ASA are working perfectly. What happened: I do not really know but I did some real messing up.