Simconnect Blocked

[BobP]

I really need help as I'm out of ideas. The details are:

 

When loading the F1 Mustang I get the error 'Simconnect Blocked'. Neither my Goflight nor Aivalsoft Data Program will connect with FSX. I re-installed FSX and the same problem persist. Yesterday I re-installed Windows 7 then FSX and the problem continues. I did follow Nick's guide on Simforum for the re-install. Has anyone experienced this problem and a solution? I did remove the overclock before re-installing. Any suggestions will be appreciated and thank you!

 

Bob

[BobP]

I forgot to mention that I have ASE and PLan-G running on a client via simconnect and both programs communicate with the server. It appears to be a local machine issue. Thanks.

 

Bob

[BobP]

I really need advice from someone who understands simconnect as this is a flight simmers worst nightmare. I have hundreds if not thousands (of dollars) of add-on's I cannot use. I would appreciate any ideas as to what can block simconnect locally on two separate computers after a fresh install of FSX with acceleration on each? The second computer I installed FSX on was a new Win7 machine which was installed by the vendor. The only common parts I can think of are the Comcast modem (network), netgear router, diskeeper 12 professional , Webroot AV and Win7 Fire wall. I have opened ports on the Win Firewall.

 

What's Happening: Everything that requires simconnect does not work.

 

Default Planes:

All run normally.

 

F1 Mustang:

When loading the F1 Mustang an error message pops up 'Network Error - Simconnect is Blocked' . The VC is blank and the throttles, buttons etc. cannot be moved.

 

Aivlasoft EFB:

The Data provider starts however cannot connect to FSX. The log shows 'Simconnect Inactive'

 

PMDG J41:

Plane will load however cannot move throttles or buttons.

 

 

Networked:

 

I can connect to FSX from my client running Plan-3G via simconnect so it appears to be a local (machine issue). I have all three simconnect files in the Windows winsxs folder. I have tried to installed the SDK and the individual simconnect files on the FSX server. I am complete baffled. Any suggestions or ideas will be appreciated. Thanks.

 

Bob

[Mike_CFII_MEL]

Hi Bob,

 

What are you using IPv6 or IPv4?. I use IPv4 with a crossover cable, I use P3D, but it should be the same for FSX.

 

I set up simconnect as follows.

 

===================

Configuring Simconnect

===================

 

1.Folders to share:

 

A. D:\P3D

 

B. C:\Users\Mike\AppData\Roaming\Lockheed Martin\Prepar3D

 

C. C:\Users\Mike\My Documents\Prepar3D Files

 

------------------------------------------------------------------------------------------

The folders shown above should be shared with read/write permissions

------------------------------------------------------------------------------------------

 

2. Your P3D Computer is the server computer (Copy WideServer.dll & WideServer.ini into P3D's "MODULES" folder).

 

3. Your networked computer is the client.

 

4. Your firewall software must be configured to allow SimConnect communications on port 500,

this includes windows firewall and applies to all computers, both SERVER and CLIENT(s).

 

5. There are two files which must be configured on the server, they are:

 

A. SimConnect.xml | Location - C:\Users\Mike\AppData\Roaming\Lockheed Martin\Prepar3D

B. SimConnect.ini | Location - C:\Users\Mike\My Documents\Prepar3D Files

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

NOTE: For use with Prepar3D: You MUST copy the fsx.cfg file into your Clinet's C:\Users\Mike\My Documents\Prepar3d Files Folder

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

---------------------

SimConnect.xml

---------------------

<?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.40</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>

 

 

-------------------

SimConnect.ini

-------------------

[simConnect]

level=verbose

console=0

;RedirectStdOutToConsole=1

;OutputDebugString=1

;file=c:\simconnect%03u.log

;file_next_index=0

;file_max_index=9

 

 

10. Copy the simconnect.msi to all client computers and run the file.

 

11. Copy the SimConnect.cfg file into the following folder on all client computers.

 

A. C:\Users\Michael\My Documents

 

--------------------

SimConnect.cfg

--------------------

[simConnect]

Protocol=IPv4

Address=192.168.0.40

Port=500

MaxReceiveSize=4096

DisableNagle=0

 

 

Have you generated a log (Simconnect.ini) to see what's going on?. If not, create a file containing these lines:

 

[simConnect]

level=Verbose

console=No

file=path to FSX\Modules\SimConnect%01u.Log

file_max_index=9

 

1. You need to replace the "path statement to your P3D/FSX" folder,

2. Save the file as Simconnect.ini in your "My Documents\FSX or My Documents\P3D" folder (or, for a non-English Windows or non-English FSX, the folder where FSX stores and loads your saved Flights and Plans).

 

The Log will be found, after or even during your FSX session, in the FSX Modules folder. (You can of course set the path to somewhere more convenient).

 

With the options as shown you will get a file "SimConnect1.Log" first, then on the next FSX session "SimConnect2.Log" and so on, with it cycling to 0 after 9, overwriting previous copies.

 

If you run FSX in Windowed mode you can, if you wish, set "console=yes" to see a real-time display of what is going on.

 

Hope this helps

[BobP]

Hey Mike!

 

Thank you and I'll go through your setup tomorrow comparing to mine. I have run the simconnect log and will post that tomorrow. Thanks again!!

 

Bob

[BobP]

Mike, I finally was able to get some time to review my setup against yours. I believe I have done all that. I wonder if a new Comcast modem or Netgear Route can affect simconnect's ability to communicate on a local machine? Again, I can network FSX via simconnect from my client to the FSX server.

 

I already opened firewall ports and installed all 3 simconnect versions. I also removed Webroot completely. I have a simconnect log but have no idea what it is telling me. It appears to be logging sim actions etc. However, Aivlasoft still will not connect to FSX and reports 'simconnect inactive'. I haven't tried the Mustang again, but assume nothing has changed. I am at the point where I have tried so many solutions, I have no idea what setup I have now. Over the next day or so I'll remove FSX, clean the registry and re-install from a new Gold version. I'll follow-up. Thanks!

 

Bob..

 

Happy New Year!

[betelgeuse]

I sympathise, Bob. I find Simconnect to be a complete nightmare. Sadly, I cannot offer even a grain of comfort. It is the most perverse application I have had the misfortune to come across.

 

Take my own set up: Server PC running FSX Gold with Acceleration in W7 x64 (professionally installed); Laptop running FSX SDK of the same version as the server in W7.

Simconnect configuration tool used in both.

 

Result: ASA2012 on laptop connects via Simconnect. Plan-G v3 on laptop refuses to connect via Simconnect or FSUIPC. The IVAO client on laptop also refuses to connect.

 

Consequences: I no longer use Plan-G in FSX and am stuck for a freeware alternative. When I wish to fly online I use FS9. I gnash my teeth when, against my better judgement, I uninstall and reinstall and find that I'm back where I started.

 

If you plan to reinstall my only constructive suggestions are to follow the routines given here exactly - they worked for me with a previous PC/laptop combination. And finally, install to a root folder e.g. D:FSX and not to Program Files/..../FSX.

 

http://www.fsdevelop...tallation_(FSX)

http://www.fsdevelop...gory:SimConnect

 

You might be interested in reading through this thread too.

 

http://www.fsdeveloper.com/forum/showthread.php?t=215890

 

Good luck!