I have searched and read the forums regarding this topic. I am not sure where the actual problem lies. So far I have installed the SDK on the Sever (FSX machine) and Client. I have updated all the way to SP2 as this is what SP I have in FSX.I am sharing these files.Users/xxx/AppData/roaming/microsoft/fsxUsers/xxx/Documents/Microsoft Flight Simulator X Files andThe main FSX folder from the default install location.The files can be viewed, written to and saved from the client. However, ASE gives me a database update error and states that the sharing component is not setup properly. Not sure how that is. Been running ASE with FS9 for 2 years! Because of this error, I cannot use ASE now as it looks for the files and continues to error despite that fact that these files show under the server computer on the client network tab.I have read and gone through the ASE manual many times.Here are my filesSimConnect ini out of the Microsoft flight Simulator X file folder[simConnect]level=verboseconsole=0;RedirectStdOutToConsole=1;OutputDebugString=1;file=c:\simconnect%03u.log;file_next_index=0;file_max_index=9HelloHere is the xml file from the App Data/roaming/Microsoft/fsx folder<?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>Auto</Protocol><Scope>global</Scope><Address>DAVIDZYCHOWSKI</Address><MaxClients>64</MaxClients><Port>500</Port><MaxRecvSize>4096</MaxRecvSize><DisableNagle>False</DisableNagle></SimConnect.Comm></SimBase.Document> Here is the config from the client users/xxx/documents folder[simConnect]Protocol=AutoAddress=DAVIDZYCHOWSKIPort=500MaxReceiveSize=4096DisableNagle=0 I have tried IPv4 and auto modes. I have tried IP (192.168.1.9) and computer name. Yet, I still cannot get it to connect when I use the AI Package exe from the Client.Yes, the msi was configured on the client as wellI created rules and opened port 500 on both machines. I even dumped AVG on the server and went back to Windows firewall. I also disabled both of them. Still will not connect.HiFi, why did you not just use WideFS for FSX like you did for FS9? That config takes the whole of 2 minutes!If anyone can shed some guideance it will be greatly appreciated and valued. If I had to guess, it seems as if the error is in the sharing aspect of things. However, I am not sure why they can be seen, opened, written to and saved then.This makes no sense.

No one has any input to help with this?I did figure out the ASE issue. It seems that the shared files need to be in the UsersPublic folder in order for ASE to work. After I placed the folders here, I edited the registry paths and ASE now fires up.SimConnect is still not working. And, no supprt from ASE either. But, they did send survery forms about the support they never gave. What a joke! No way I will ever buy 2012 from them now.