Rob,

 

No ASN entries in DLL.xml or EXE.xml in my :

C:\Users\vaughan\AppData\Roaming\Lockheed Martin\Prepar3D v2

 

So, I copied the DLL.xml ASN entry from my FSX DLL.xml into my P3D DLL.xml and all is working.

 

<Launch.Addon>
    <Name>as_connect</Name>
    <Disabled>False</Disabled>
    <Path>as_srv\as_btstrp.dll</Path>
  </Launch.Addon>

 

 

You fixed it!

Thanks a bunch.

I added port 445 to the Windows firewall to try to fix my previous error (ASN crashed).

It did not fix my problem.

 

So, I removed Port 445 from the server and workstation PCs.

 

All is OK without port 445

Also, port 445 has never been in use on my PC in past 3 years since I purchased this PC..

 

So, the question is ... because I may be causing a problem by not having it ,,,,

What is Port 445 used for?

 

 

No ASN entries in DLL.xml or EXE.xml in my :
C:\Users\vaughan\AppData\Roaming\Lockheed Martin\Prepar3D v2

 

Oh, yeah, that'll be a problem ... glad you got is sorted ... as for port 445 you'll have to check with the ASN folks, they can provide more details than I could.

 

Cheers, Rob.

Rob,

Thanks, I will ask over there.

Also, port 445 has never been in use on my PC in past 3 years since I purchased this PC..

 

So, the question is ... because I may be causing a problem by not having it ,,,,

What is Port 445 used for?

Hi Vaughan,

 

I think your answer about Port 445 is on Page 80 of the ASN Manual:

 

"Finally, you may need to open port 445 (TCP) on both client and server to enable proper pipe communications between ASN client and the AS Connect module on the server. This is the same as the “File and Printer sharing port” and is normally enabled by default when Windows networking is enabled, but may need to be opened manually in some cases."

 

"With a proper SimConnect installation and configuration, proper file sharing paths and access, proper opening of the radar data network port, and proper opening of port 445 on your firewalls, ASN will be able to properly operate in a networked environment."

 

Hope this helps.

Jim,

 

Thanks for the follow up.

 

I do have the printer sharing and Active Sky programs has permissions ......... so far I have not needed the Port 445.

This may or may not help. I upgraded to the latest ASN beta (2) . I run ASN on a client machine. I had downloaded the full install. I uninstalled Beta 1, installed Beta 2 and experienced the '...ambient...' message.

 

Finally, I uninstalled Beta 2 and eliminated all traces of ASN from both machines including: as_srv on the main machine, the dll.xml entry on the server machine; and all traces of ASN on the client machine including: %APPDATA%\Roaming\HiFi. The first time I installed Beta 2, I didn't uninstall the AppData.

 

After the second install, ASN runs correctly, without the ambient weather error. This may apply to others, maybe not. This was my experience.

 

Graham