HiI am trying to set up ASA and FSX to work in my network, but I can't connect ASA and FSX.Server Pc specs are: Windows XP Home Edition, SP 3, Pentium D 3.2 GHz, 3 GB RAMClient portable specs are: Windows Vista Home Edition, SP1, Intel Core Duo 2.2 GHz, 2GB RAMFSX +Acceleration and SDK AccelerationASA SP1When I try the simconnect AI Traffic test from the server appears an error telling me to reinstall the application and if I tried the same test from the client, a black window opens but nothing else happens. The FSX indicate that the simconnect is working.I have installed ASA SP1 I can see that ASA detects the SDK SP2 but the FSX icon reminds red (no connection)Both computers have perfect communication, I have done all the steps described in the manual, including reinstalled the FSX and the SDK twice and also checking the Norton 360 firewall but I can't find where the error is.I have read some forums regarding this problem but I didn't find the solution. I really appreciate any help in this matterJcmmg

Hi,It's not FSX so don't touch that for now.Did you go through the ASA Network chapter and set up all the files correctly, including IP addresses, and placed them in the proper folders?Running the Traffic AI program from the client and FSX on the server should show traffic comming and leaving FSX. Does the black window stay open or does it close in a short time?Please let us know.Thanks,

Hi JimAbout your questions:a) Yes the AI Traffic close without any message after some seconds:( I checked the report created by ASA during the initiation and I found this:FSX My Docs Path Value = (empty) the other are okIt looks that it doesn't recognise this particular path for the Flight simulator X files folder. How can I correct this error?c) IP adress 192.168.1.102, port 500, Ipv4, etc are right in both computersThanks for your help! Jcmmg

Hi,You need to get the AI Traffic utility communicating with FSX first. That is a SimConnect utility so it is showing that your SimConnect in not communicating with your FSX correctly yet.Thanks,

Hi JimWell I've tried a couple of times but with the same result, also I found that I need to introduce my Vista user name and password when I am trying to see my Vista folders from the Xp computer, which is an additional dialog that doesn't appear when I am navigating from my Vista computer. I wonder if this dialog is affecting the communication.I really appreciate any help in this matter, since I found a forum where the user simple give up trying to solve the problem. I don

HiI have turned off the option to ask for the Username and password from the Vista pc, but any change in the AI traffic test.

1) open a dos command window on your client pc2) type ping 192.168.1.102 ( if this is the ip address of your main machine)What do you see?If you get replys with a time then your network is ok (not relating to FS but simply pc to pc)If you get no replys then that is the first thing you need to resolve. Check firewall including Windows firewallYou need to double check the ip address of your server machine. If its set to dynamic then the ip address will change depending on what order devices are connected to your router. Each time you boot and you have been connecting other machines to your router then you will start with a different ip address. Check it is still the same as the ip address you entered in your config files

Hi,Are both computers part of the same Workgroup?

HiThanks alot with the help, what I found by pinging was that the adress 192.168.1.102 was unable to connect (no idea why), but chaging it to 192.168.1.72 and setting it not to be variable in the server, Puffffhhh! the ping establish communication. As a result the AI traffic test was successful and I got perfect connection between ASA and FSX.Jim: Thanks for your help, I think it could be a good idea to add this steps to an additional trouble shooting, I have checked many forums but not an ideal answer.Thanks againjcmmg

and setting it not to be variable in the server,

I think that this may be the key. I found that unless the IPs were static, it was like herding cats getting an XP32 and Vista machine to network. One day it would work, another it would not. I do hope that you have solved it, and it is a lasting fix.