belisba

Well, just after my last post, I noticed that I had uninstalled ASN on my SERVER PC (pc with FSX). I guess I had uninstalled it prior to trying to set things up over the network thinking it might conflict with the CLIENT installation, configuration, etc. Jump ahead a day and some hours later when I started to give up on getting it to run from my laptop, I decided to reinstall FSN back onto my SERVER (PC with FSX) and just take the frame hits. Reinstallation went off without a hitch. Out of curiosity (first ensuring both ASN and FSX were not running on my SERVER PC) I ran up ASN on my CLIENT, ....and whallaa,...no error message! With ASN running on the CLIENT (laptop), I ran FSX on the SERVER and got a "FSX Connected". Everything is running smoothly now.

Thx, for me, that really is the key issue, I do not have FSX running when launching ASN when the error message appears. Some things I have done to try to fix include: Turning off virus protection on client and server pcs. Ensuring Active Sky Next is authorized to pass through firewall (Windows and Norton Internet Security) Not sure what else can be done. I too ran AI Traffic and things seem to be fine.

Same issue here....anyone have any idea?

Thanks for the input, will give it a go.

Recently downloaded and installed the latest FSGenesis Mesh for FSX. Nice product. However, FSGenesis states: "..These terrain files are also P3D-compatible, with manual configuration." Has anyone been successful in manual installation of mesh into P3D V2 yet?