News:

Thou shalt confirm thine airspeed on final, lest the earth rise up and smite thee. (pre-landing checklist, v1)

Main Menu

Simconnect problems with two Win7 computers

Started by TCA2754, February 11, 2011, 05:47:11 PM

Previous topic - Next topic

TCA2754

Hi,

I need help to solve a simconnect problem that only happen with Plan-G.

I run Win7 on all my computers expcept the computer I have FX install (it is 64X, the rest are 32X bit) The comunication between them (Homegrupp) are running fine but with Plan-G I cant get any connection between the computers. I have FSX on one computer and Plan-G program on a second computer were I install simconnect client.

I have add the program in Windows Firewall (on both computers) and also edit the advance option "rules for in & out traffic" Below are my settins for Plan-G on both computers.

1. Allow connection
2. Program & Service, point to the program ( On FSX computer I have add the patch to the program on the second computer were I point the patch to FSX)
3 Protocoll and ports, both TCP & UDP "Specific port 4500-4600"
4. Local & Remote IP address, Set IP between 192.168.0.100 - 192.168.0.199.
5. Advance option = Private & Public and Edge traversal are set to program.

I use a router (D-Link) and set the program & port in Port Forwarding for Simconnect.
My FSX computers IP are 192.168.0.112, and the computer with Plan-G are 192.168.0.198.Which one should I use ? In the router I have two more options, Virtual server & Application Rules but dont use them. May that be the problem ?

I run FSX with accelerator and use MS Security Essentials.

When I start Plan-G and load a fltpln I got a message after a while complaning on the script and ask me if I like to use it or not, if then the program maybe wont work proper ?? The fltpl are made with FlightSim Commander ver.8.6
Whats that ?

Then when I connect to FSX I got a error saying
" Unable to connect to remote Flight Simmulator (timeout)
Check FSX is running, and that you protocol setting are correct.

I have look in the forum for a solution but could not find any that fix my problem.
I even use the suggestion to use my computers name (PAR). WideFS - simconnect worked but not Plan-G

Hope someone cane help me out here as the program seams to be nice to use, if not I have to send it to my trasbox. LOL

Pär

tim arnot

The script warning is dealt with in the FAQ.

In Plan-G you must specify the IP of the FS computer.

Did you also set the Simconnect.xml on your FSX PC? Instructions are in the manual, starting at p89.

Tim. @TimArnot

TCA2754

HI,

OK, I check the FAQ

Here are my simconnect.xml

<!-- Example Local IPv4 Server Configuration-->
<?xml version="1.0" encoding="windows=1252"?>
<SimBase.Document Type="Simconnect" version="1.0">
<Descr>Simconnect.xml>/Filename>
    <SimConnect.Comm>
    <Disabled>False</Disabled>
    <Protocol>IPv4</Protocol>
    <Scope>Global</Scope>
    <MaxClients>64</MaxClients>
    <Address>192.168.0.112</Address>
    <Port>4506</Port>
    <MaxRecvSize>4096<MaxrecvSize>
    <DisableNagel>False<DisableNagel>
    </SimConnect.Comm>
<SimBase.Document>
   
I check my windows log and find this warning that happen when I try to connect Plan-G from the client computer

param1 Peer Networking Grouping
  param2 PNRP (Peer Name Resolution Protocol)
  param3 %%-2140993535

they have a link, and this comes up


Event ID 102 — PNRP Protocol

Updated: January 6, 2009

Applies To: Windows Server 2008 R2
red

The Peer Name Resolution Protocol (PNRP) protocol determines the interaction of the local computer with the PNRP cloud (a grouping of computers that can find each other). The local computer must have a default identity defined and proper permissions assigned in order to interact properly with the cloud.
Event Details
Product:    Windows Operating System
ID:    102
Source:    Microsoft-Windows-PNRPSvc
Version:    6.1
Symbolic Name:    PNRP_CLOUD_NOT_STARTED_ID_CREATION_FAILED
Message:    The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: %1.
-----------------------------------------------------------------------------------

Resolve
Create a default identity or change permissions

You might need to create a default identity or change permissions for the Rivest-Shamir-Adelman (RSA) folder if keys on the corresponding folder are modified by a user or program so that operations for the current security context are not permitted on that folder.

To create a default identity by using Windows Vista:

   1. Click Start, then click All Programs, then click Accessories. Right-click Command prompt, and then click Run as administrator. Acknowledge the user access control (UAC) prompt.
   2. In the command prompt window, type regsvr32 %windir%\system32\rsaenh.dll, and then press Enter.

If, after creating a default identity, access to the RSA folder is still blocked, give "LOCAL SERVICE" full control of C:\ProgramData\Microsoft\Crypto\RSA:

   1. Click Start, click Computer, right-click C:, and then click Explore.
   2. Click ProgramData, click Microsoft, then click Crypto.
   3. Right-click RSA, click Properties, and then click Security.
   4. Click Edit, click Add, type local service, and then click OK.
   5. Click Full Control, and then click OK.

If you are using Windows XP, see http://go.microsoft.com/fwlink/?LinkId=92842.
-------------------------------------------------------------------------------------

Verify

To verify that the Peer Name Resolution Protocol (PNRP) cloud is initialized properly:

   1. Click Start, type cmd in Start Search, and then press Enter.
   2. In Command Prompt, type netsh p2p pnrp cloud show names and then press Enter.
   3. If the state is active for Global_, and the number of cache entries is 10 or greater, then the PNRP cloud is properly initialized.

To verify that the PNRP can resolve names:

   1. Click Start, type cmd in Start Search, and then press Enter.
   2. In Command Prompt, type netsh p2p pnrp peer resolve 0.testingpnrp, and then press Enter.
   3. You should see the IP address. If you do not see the IP address, then PNRP is not resolving names.

I did all the suggestions but it still dont work. I could not add " local Service"

Then I check Service on my computers and the service for
Peer Networking Groupin
Peer Networking Identity Manager
PNRP(Peer name Resolution Protocol)
PNRP Machine Name Publication Service
PnP-X IP Bus Enumerator

They were set to Manual, then I set them to Automatiskt. I reboot and check it again, some have started and some have not, I try to start but it did not work. I check if they were depending on some serive, but all of them I have on Auto.
I'm not so good at this so some help would be nice to have, should I do this on both computer (server & client ?)

LOL, I know I'm a pain in the a**

Pär


tim arnot

I've not heard of this Peer Networking Grouping before, so I don't think I can be much help with it. Maybe someone else knows?

But the simconnect.xml looks fine.

Tim. @TimArnot

TCA2754

OK, THX

I hope someone cane shear some light about this problem.
If I fine out something  on another forum and it work, I tell you.

Pär