Hi,And you went through the Networking Chapter and set everything back up again on the server and the client?Thanks,

Yes and I will go through it now again checklistMy FSX installation folder and the C:\Users\[username]\AppData\Roaming\Microsoft\FSX and C:\Users\[username]\Documents\Flight Simulator X Files are shared since I can access them from the client and all three has read/write permission for everyone.I have Microsoft Flight Simulator X: Acceleration Pack SDK installed Under Win 7 Windows Firewall settings inbound rules I got an entry SimConnect local port 500 and protocol TCP/IPI got simconnect.xml in [ApplicationDataFolder]\Microsoft\FSX\SimConnect.xml and have enabled IPv4 with port 500Under the test step I get a Connected to Flightsimulator message when running Aitraffic utility (shouldn't everything be correctly set up then?)My registry on the client has entries for the three FSX folders on the server (and I was prompted for them when starting ASA after Win 7 installation)Am I using wrong IP address? There were several IP addresses given? But then should the AItraffic utility work

Hi,What is the server IP address?What files did you set up on the client?Thanks,

Hi,What is the server IP address?What files did you set up on the client?Thanks,

IP address 192.168.0.10. The same files on the client as before when I got it running with W7 RC since the client Win XP hasn't been reinstalled. That would be simconnect.cfg and in the add/remove program I see Microsoft Flight Simulator SimConnect client V 10.0.61259.0 and Microsoft Flight Simulator X: Acceleration SDKinstalled. All according to the ASA manual.Content of SimConnect.cfg[simConnect]Protocol=IPv4Address=192.168.0.10Port=500MaxReceiveSize=4096DisableNagle=0Content of SimConnect.xml<!-- Example Local IPv4 Server Configuration--> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>local</Scope> <MaxClients>64</MaxClients> <Address>192.168.0.10</Address> <Port>500</Port> </SimConnect.Comm>have also tried the <!-- Example Global (remote) IPv4 Server Configuration-->

Hi,Did we determine whether the computers belong to the same network? By default Win 7 assigns a different name then XP and Vista did and this is messing a lot of Win 7 users up. I know it is your network but the network names need to be the same.

Hi,Did we determine whether the computers belong to the same network? By default Win 7 assigns a different name then XP and Vista did and this is messing a lot of Win 7 users up. I know it is your network but the network names need to be the same.

I don't know. But I don't remember having to edit network names when I got things working with the RC of Win 7. But I do remember having trouble with simconnect.Exactly where and how do I see these names in Win 7 and Win XP?One more little detail I have noticed. The three network paths in the client Win XP registry is not exactly the same format as suggested in the manual. Instead I have the full path.

Hi,My Computer/Properties/Computer NameThanks,

Hi,My Computer/Properties/Computer NameThanks,

In Win XP when I rightclick My Computer and select properties and then the Computername I see this infothis information is going to be used to identify the computer on the networkComputer description XPa complete computernameWorkgroup WORKGROUPDoing the same for Win 7 I see that XP and WORKGROUP for description and Workgroup are identical to the Win XP info.

Hi,That is correct. Next I would see if one of the firewalls is blocking things.Thanks,

Hi,That is correct. Next I would see if one of the firewalls is blocking things.Thanks,

And as expected they obviously don't since the problem remains even after disabling the firewall on both computers.

Hi,Let me have you post your ASA_Log.txt file after running ASA and FSX once. Also the ASA_SimConnectionLog.txt file.Thanks,

Hi,Let me have you post your ASA_Log.txt file after running ASA and FSX once. Also the ASA_SimConnectionLog.txt file.Thanks,

I have no ASA_SimConnectionLog.txt file on either computer. The ASA_Log.txt is as before this16:03:30:0578 - Flight Plan Retrieved - Dataset data about to be processed21:36:28:0546 - Flight Plan Retrieved - Dataset data about to be processed

Hi,The ASA_Log.txt file has to be longer then that because it records everything ASA does at startup and those time are close to 5.5 hours apart.Include Hidden and System folder in your search.Thanks,

Hi,The ASA_Log.txt file has to be longer then that because it records everything ASA does at startup and those time are close to 5.5 hours apart.Include Hidden and System folder in your search.Thanks,

Ok after doing that I found an additional bigger ASA_log.txt file and also a big ASA_Simconnection file which contains all thisFirst the ASA_log.txt file23:59:24:0531 - Loading Application Data Path23:59:24:0531 - Application Data Path = C:\Documents and Settings\Jan Friberg\Application Data\HiFi\ASA23:59:24:0531 - Loading Application Executable Path23:59:24:0531 - Application Executable Path = C:\Program\HiFi\ASA23:59:24:0531 - ASA load commencing...23:59:24:0531 - Verifying Active Sky Advanced License23:59:24:0781 - FSX Path Value = \\JAN6000X2-PC\Microsoft Flight Simulator X\23:59:24:0796 - FSX My AppData Path Value = \\JAN6000X2-PC\FSX\23:59:24:0796 - FSX My Docs Path Value = \\JAN6000X2-PC\Flight Simulator X Files\23:59:24:0859 - ASA settings have been loaded...23:59:25:0687 - Initializing ASA23:59:50:0093 - FS station database update not needed (unchanged)...23:59:50:0140 - World Magnetic Model has been loaded...23:59:51:0781 - Wx Station Database loaded: 9961 station(s)23:59:52:0421 - Airports Database loaded...23:59:52:0421 - Loading Additional Weather Stations...23:59:52:0671 - Additional stations database load compete for 1704 stations23:59:52:0703 - SimConnect found and initialized23:59:54:0015 - ASA controls initialized...23:59:54:0031 - ASA v11.0.0.433 Copyright

Hi,The second log is showing that Simconnect never connects to FSX and ASA verifies this by never connecting to FSX. So either your firewalls are blocking things or Simconnect on the client is not installed properly.Thanks,

Hi,The second log is showing that Simconnect never connects to FSX and ASA verifies this by never connecting to FSX. So either your firewalls are blocking things or Simconnect on the client is not installed properly.Thanks,

How is that possible? I use the same installation of SimConnect on the client that used without problem with W7 RC. Also I tried disabling both firewalls without success. So you mean it's certain that the problem is on the client and not the server? So what should I do now (when I come back to my computers in a week)?Reinstalling SimConnect on the client? What are the exact details to think about? It's about time I get this working now?