Hello SrdanTwo people have read the manual and applied the settings.First, the file path - what is the correct file path. I have been told two different paths..... Which is the correct path?Second, if I install everything as suggested by the manual all the AT Traffic shows is a black box then closes - indicating an incorrect set up.But, I have done everything correctly and this has been checked by another person.Thank you, Iain

I've done some more testing including checking everything twice. This includes disabling the firewall and ensuring the correct static IP address is listed in the simconnect.cfg and .xml files.

Now we're getting somewhere. Is your machine's (server's) IP static? Did you check, for example with ipconfig in cmd prompt, if you got the correct IP address? I'm just checkin...Basically: one file where fsx.cfg is (server), one file my docs/fsx (server) and one file in mydocs on the client.

First, when I run AI Traffic it does not say anything about connecting to flight simulator - just a curser.

That means bad configuration.

Second, I have been told that the folders I am placing the .xml and .ini files is the wrong folder. The ASE manual only has vista and XP file paths which I've been told are incorrect.Can you please tell me the correct file paths running two WIN 7 computers.I've been told the correct paths are:C:usersusernamedocumentsflight simulator x files for the simconnect .ini file; andC:users(username)appdataroamingmicrosoftfsx for the simconnect .xml file.

LOL, "who" has told you that?? ("I've been told...")Paths are same as for Vista.My documents: simply open explorer and access my documents on the navigation pane2nd is correct (fsx.cfg MUST be there, then you know it's right)

I'm pulling my hair out on this one... After trying to install ASE other networked programs which were working are now not working (such as Aivlasoft Electronic Flight Bag).Also, can you please tell me the correct procedure for the PS in the post above this oneI'm hoping there is a simple solution to my vexing problem. Thanks, Iain

Iain, I can assure you, everything can and will work together. It does here. I also have EFB, ASE, SB4, and some other online programs and they ALL play along.I'm gonna go a step further and post you contents of my files:Simconnect.ini in My Documents (SERVER):[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:simconnect%03u.log;file_next_index=0;file_max_index=9Simconnect.xml in FSX folder (...RoamingMicrosoftFSX) (SERVER)<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>192.168.1.100</Address> <MaxClients>64</MaxClients> <Port>1040</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.cfg on the client, in My Documents folder (CLIENT)[simConnect]Protocol=IPv4Address=192.168.1.100Port=1040MaxReceiveSize=4096DisableNagle=0Make sure you have ALL THREE.I've bolded you the very important stuff, but refer to manual as to which other settings might be important too, I don't know it oftop of my head.IP Address is OF COURSE going to be yours! Not mine...Also make sure you have installed Simconnect client on the client machine.

Same as before - black screen that disappears. Yes I have static addresses that are both the same. I was told by a guy who PMd me from the squawk box forumThis is not working. I've spent close to 8 hours doing the same things with exactly the same results.I'm doing something wrong for sure. What I cannot say, as I've followed the manual and your instructions to the letter.Can I be bold enough to ask if I can telephone you so we can walk through this step by step. Writing takes time and often is confusing for all parties.If so, please send your number via PM (including country code) or to my emailCheers, Iain

You install the SDKs on the client in order to get Sim Connect installed on the client computer. That is how ASE communicates across the network: through 2 installs of SC, one on the server and one on the client.You test the connection by running the utility on the client with SX running on the server.You never need to install the SDKs on the server in this case.

I am having similar problems. Simconnect use to work but I broke something. If I read your post correctly, it seems you say that the SDK is installed on both machines and then you say only on the client. I thought it was client only?

I am having similar problems. Simconnect use to work but I broke something. If I read your post correctly, it seems you say that the SDK is installed on both machines and then you say only on the client. I thought it was client only?

It's not about the SDK, or where it's installed.What you mean is Simconnect. And yes, it can be installed on both machines. It doesn't matter.

Thank you

It's not about the SDK, or where it's installed.What you mean is Simconnect. And yes, it can be installed on both machines. It doesn't matter.

Thank you.So at the minimum, move the SDK folder to the client, install, install SP1A?

Thank youThank you.So at the minimum, move the SDK folder to the client, install, install SP1A?

I don't get it. What do you want to move!?It goes like this, and I ain't gonna repeat it again:1) Insert FSX Disk2) Install SDK from SDK folder on FSX Disk3) Instal SDK SP1a for SDKThen you have your exe files, config files to do all the right things. Where you install SDK, does not matter.

I don't get it. What do you want to move!?It goes like this, and I ain't gonna repeat it again:1) Insert FSX Disk2) Install SDK from SDK folder on FSX Disk3) Instal SDK SP1a for SDKThen you have your exe files, config files to do all the right things. Where you install SDK, does not matter.

4) Install the simconnect on the client?

4) Install the simconnect on the client?

"Then you have your exe files, config files to do all the right things."

I wasn't going to jump into this one again, but the amount of false information being shared here is truly unbelievable.You need the SDKs in order to install SIMCONNECT on the CLIENT computer. The server computer already has SIMCONNECT installed because FSX installs SIMCONNECT when you installed FSX and the updates to FSX.Now just installing the SDKs is NOT enough because now you need to run the simconnect.msi file ON the CLIENT computer. So:1. Insert FSX DVD 1 into the drive on the client computer and install the SDK. Now find the simconnect.msi file and click on it and it will install the very first version of SIMCONNECT.2. Download the SDK1A from Microsoft and install the SDK on the CLIENT computer. Find the simconnect.msi file and click on it and it will install the 1A version of SIMCONNECT.3. Download the SDK 2 from Microsoft and install the SDK on the client computer. Find the simconnect.msi file and click on it and it will install the 2 version of SIMCONNECT.Now, configure the 3 needed files and place those in the proper locations.Install ASE on the CLIENT computer, share the proper folders, and run ASE on the client and FSX on the server.If you want to test your connections before running ASE, then run the AI Traffic utility on the CLIENT with FSX running on the SERVER and see what the Traffic utility does. If it runs for about 30 seconds and closes down that means that SIMCONNECT is NOT set up properly.

Jim, I hate this, but I must somewhat contradict you. If it was intended towards me, I just want to state that I gave in no way a false information.They were asking if SDK needs to be installed on the client - and no, it does not! If now you say it does: I'll say I don't have it installed on the client, and yes, my simconnect is working. SDK installs Simconnect.msi, as you so neatly pointed out, which is then used to install Simconnect itself. But SDK installation installs no simconnect, thus it is absolutely the same thing if you install it onto client or server, since it's just a bunch of files!But YES, you do have to install Simconnect on the client. But not on the server, since as you said, FSX already installs it.They apparently misunderstood SDK for Simconnect, which are two different things.Sometimes you really make me arrrgh...

How did you get simconnect installed on your client?Do you think it is easier to say "OK now move the .msi file versions onto the client and install them." Or do you think it is easier to install the SDKs on the client and then the .msi files are located there already."?The KISS rule really comes into play here because not everyone is a computer or network wiz.

How did you get simconnect installed on your client?Do you think it is easier to say "OK now move the .msi file versions onto the client and install them." Or do you think it is easier to install the SDKs on the client and then the .msi files are located there already."?The KISS rule really comes into play here because not everyone is a computer or network wiz.

They have to share folders to configure ASE, cuz that was the first one about, from Iain.For me, personally, it's easier - I have all my partitions shared and shortcuts. So access it is as simple as on the same machine.But yes, I do think that many people know how to share folders. I don't get it really, why would people get a laptop and want to run things off of it, but not know a single thing about networking... you wouldn't even make it work from the ground up.Anyway, I wanted to explain correctly, thoroughly, I failed apparently.Thank you for the simple explanation.

Thanks Kskroma, you offered new information that I appreaciated.

I can't get this working as well ^_^Everything is the same, exept my IP is Dynamic. 2 days ago I was trying to set everything up, but failed with IP 103. Today it's 104 and I switched it in config files.Questions:1) If I have no antiviruses, and all security stuff like defender and firewall is fully off, do i need something else to do with that?2)I shared the folders and I can copy files from SERVER (FSX desctop) to CLIENT (laptop) but i cannot cut from MS documents folder, where the weather files located and so on). I am not sure that I have done everything right with sharing settings. Can you give a word to help with this?3)How can I make my IPs static? I have WIFI router and use many divices like IPAD MACbook, phones, PCs and so on.------My guess is wrong sharing setting, because I have AITRAFFIC tool working well on fsx pc, but it's just black on Laptop...but i was pretty sure that the setting were all well...Cheers

Edited February 5, 201214 yr by FCOM