No, the other way around: Server contains FSX, client contains ASN.

Server is where FSX runs or P3D the client is where active sky runs. Only the SDK should be on the client pc NOT FSX/P3D as well. There is a very useful video on setting up fsx on a network by Froogle. Hope this helps

 

Cheers

I had the same problem for weeks, but thanks to Bedgie post #13,

changing my .xml file. Now ASNext works just fine on my second PC networked.

Also, it doesn't matter at least on my machine what order I start. FSX or ASNext.

It seems to connect now all the time.  I also Have Avilsoft EFB running on my second PC,

networked and both don't conflict.

 

Ok i had a lot of trouble sorting this bugger out, but I think I may have solved it (well it worked for me anyways)

 

If your xml file looks like this:

 

<?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.0.11</Address>

        <MaxClients>64</MaxClients>

        <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>

 

And SimConnect still doesn't work, then there's your problem!

 

You have two entries trying to use the same port (500). Only one will win,   and if it's the "local" one then you won't get a remote connection in any case.   

 

Try this one instead: 

 

<?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.54</Address>

    <MaxClients>64</MaxClients>

    <Port>500</Port>

    <MaxRecvSize>4096</MaxRecvSize>

    <DisableNagle>False</DisableNagle>

</SimConnect.Comm>

<SimConnect.Comm>

    <Disabled>False</Disabled>

    <Protocol>auto</Protocol>

    <Scope>local</Scope>

    <Address></Address>

    <MaxClients>64</MaxClients>

    <Port></Port>

    <MaxRecvSize>4096</MaxRecvSize>

    <DisableNagle>False</DisableNagle>

</SimConnect.Comm>

</SimBase.Document>

 

Just change the address I have highlighted in red to suit your machine only!

Leave the bottom address as is.

I am no computer Guru by any means I just did some digging around the net trying different ideas. and low and behold this worked.

 

P.S.

I am using Win 7 x64

WOW! After days  of stuggling to get this to work, it finally works. Thanks bedgie. You should post this in ASN forum. There are alot of people that are stuck and can't move forward from this error.

I'm having the same trouble, and tried everything, after the latest AS update.  It's not working. 

Would love to help. How far are you getting when launching ASN? What error messages do you get?

It's just not connecting.  I updated ActiveSky Next yesterday, and it hasn't connected on my network.  I installed the ASConnect on FSX too.

It's just not connecting.  I updated ActiveSky Next yesterday, and it hasn't connected on my network.  I installed the ASConnect on FSX too.

 

Hi,

 

Is your SimConnect working?

 

Check out this post here:

 

http://forum.avsim.net/topic/462339-ai-controller-14-sid-jet-route-star-and-final-approach-new-beta/?p=3214798

It's not working.  I installed an ActiveSky update and it stopped working.  Reinstalled ActiveSky and it didn't work.  I think the problem is Simconnect, but how can an ASNext SP2 update affect that program on another computer?

 This happened right after an ActiveSky update yesterday. 

It's not working.  I installed an ActiveSky update and it stopped working.  Reinstalled ActiveSky and it didn't work.  I think the problem is Simconnect, but how can an ASNext SP2 update affect that program on another computer?

 

So you're saying SimConnect isn't working?  ASN doesn't touch SimConnect.

 

Do you lock your IP address or let it be set dynamically by a router?

I use the computer name in the address.  Never had a problem with it.

Do any other SimConnect programs work? 

 

If you don't have another SimConnect program on the client, use "AI Traffic.exe" found in your SimConnect SDK folder (I think under the Samples Folder).

 

If it connects, then it's not a SimConnect issue.

Nothing is happening with AI Traffic.

OK.  Looks like you're right, and SimConnect got pooched somehow.

 

Can you post your simconnect.cfg from you client and your simconnect.xml from your FSX Appdata folder? (just copy and paste here)