simconnect not working on a win7 to win 8 network

[terenceskelton1]

Hi.

 

I know that simconnect is not a Pete Dowson module, but he is very knowledgeable, and I need some help, and somebody else may have also come across my issue and actually has an answer.

 

I used to have a desktop running FSX, and a laptop running REX Essentials + OD, networked. The desktop (server) is running win 7, and the old laptop (client) was also running win 7. Simconnect worked fine.

 

I have upgraded my laptop to a new one, preinstalled with win 8. I cannot get simconnect to work!

 

I have had direct support from REX, and they have also been unable to resolve this issue of simconnect refusing to work between a win7/win8 network!

 

Has anyone else had this issue and been able to resolve it? If you did, how did you do it?

 

WideFs works fine on the win7/win8 network. It is only simconnect that does not work!

 

Rgds.

 

Terry

 

 

[Pete Dowson]

I have had direct support from REX, and they have also been unable to resolve this issue of simconnect refusing to work between a win7/win8 network!

WideFs works fine on the win7/win8 network. It is only simconnect that does not work!

 

Hmm. If WideFS works the I don't understand why SimConnect cannot. I suppose you've checked the SimConnect.xml file on the FS PC, and the SimConnect.cfg file on the other PC?  Both the IP Addresses or PC Names should match the FS PC. Also they need the same port defined.

 

I'm afraid I've been steering clear of Win8. I did install it briefly on a Notebook just to make sure it didn't mess any of my code up, but i was then swiftly back to Win7.

 

Regards

Pete

[terenceskelton1]

Hi Pete.

 

Thanks for replying to my post.

 

Yes, we did try everything (but nothing that I had not already double and triple checked!).

 

I did try and install win 7 on the new laptop (client), but I had issues with an "unknown USB Controller" showing up in the computer management window, which I could not resolve. I did contact acer support for help, but their reply was "we cannot offer you any technical assistance because you have changed the operating system that it came preinstalled with"! LOL!

 

Anyway, REX Essentials + OD worked fine in that win7/win7 network, so I obviously assumed that it was a win8 issue?

 

REX Essentials + OD also work fine standalone in both the win7 (server), and the win8 (client).

 

However, as an experiment, I today downloaded the demo version of Opusfsx. That uses simconnect also, so it was a way to prove whether I had a simconnect issue with win8. It works fine! I did not even touch any simconnect settings, nor did I even run the simconnect.msi installer in Opus! All I did was to point both the fsxserver and fsxclient apps to each computer, and it worked straight away! Weather injected into FSX fine. I am loath to fork out to buy the full version of Opusfsx, as that will also require buying separate textures, etc, as Opusfsx is purely a weather engine!

 

So? It is not a simconnect issue, which you also could not understand, because as you say, widefs works, so simconnect should also!

 

I have let REX know! Let them pick the bones out of that one! LOL! I have now confirmed that REX Essentials + OD will not work on a win7/win8 network! There must be something in their coding that win8 does not like (when linked through a network).

 

Thanks for taking an interest, and for trying to help out.

 

You do have a very good reputation, which is the reason I came to you for some advice. Hope you do not mind.

 

Regards.

 

Terry

[Pete Dowson]

However, as an experiment, I today downloaded the demo version of Opusfsx. That uses simconnect also, so it was a way to prove whether I had a simconnect issue with win8. It works fine! I did not even touch any simconnect settings, nor did I even run the simconnect.msi installer in Opus! All I did was to point both the fsxserver and fsxclient apps to each computer, and it worked straight away! Weather injected into FSX fine. I am loath to fork out to buy the full version of Opusfsx, as that will also require buying separate textures, etc, as Opusfsx is purely a weather engine!

 

I am pretty sure that OpusFSX does its own Networking, same as WideFS. It uses SimConnect from the FSXServer.EXE into FSX, but I am pretty sure that all its Clients only talk to it, as the sefver, not to FSX via SimConnect. I think they must do that because of the networking support for views etc etc, none of which is provided by Simconnect.

 

So, I would still bet on a Simconnect configuration issue. Maybe you should paste your SimConnect.xml file (from the same folder as your FSX.CFG), and the SimConnect.CFG (from the client PCs "Documents" folder, or in the same folder as the program (REX) you are trying to use. If there is one in both I suspect the one next to the program being run takes precedence.

 

Regards

Pete

[terenceskelton1]

Hi Pete.

 

Ah! I had thought that because the simconnect.msi application was included with Opusfsx, I had assumed that it used simconnect!

 

My client .cfg is

 

[simConnect.1]
Protocol=IPv4
Address=hidden (but it is identical to the .xml)
Port=6600
MaxReceiveSize=8192
DisableNagle=1

 

My server .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>local</Scope>
    <Address>hidden</Address>
    <MaxClients>10</MaxClients>
    <Port>6600</Port>
    <MaxRecvSize>8192</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
</SimBase.Document>

 

I did not want to post my server address, so I have typed hidden in there! I did try the standard port 500 also!

 

Part of the session with REX was to make sure that all other simconnect.xml, and simconnect.cfg entries were deleted from everywhere other than where they are meant to be!

 

I still keep coming back to the same question though? Same laptop, same programs, same simconnect settings, but it worked fine with a win 7 setup?

 

So I am back to square one! There is something in win8 that is preventing simconnect from "talking" to the win 7 computer?

 

Thanks for the info though.

 

Regards

 

Terry

[Pete Dowson]

Ah! I had thought that because the simconnect.msi application was included with Opusfsx, I had assumed that it used simconnect!

 

Yes, the Server certainly does. I think they provide the SimConnect install in case you don't have that version installed -- there are three valid versions of Simconnect for FSX.

 

My client .cfg is

 

[simConnect.1]

Protocol=IPv4

Address=hidden (but it is identical to the .xml)

Port=6600

MaxReceiveSize=8192

DisableNagle=1

 

 

Okay -- that's fine as long as the Address is either your FS computer name, or its IP address. No reason to hide it. Local IP addresses are not usable outside your network. Most folks have the same ones in any case.

 

My server .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>local</Scope>

    <Address>hidden</Address>

    <MaxClients>10</MaxClients>

    <Port>6600</Port>

    <MaxRecvSize>8192</MaxRecvSize>

    <DisableNagle>False</DisableNagle>

  </SimConnect.Comm>

</SimBase.Document>

 

 

That's okay for a local Simconnect connection, as used by OpusFSX's server, except that you do not specify Address or Port for the local connection.  See where it says "Local" for the Scope?

 

It's no good for anything over a network. Surely the documentation for networking REX tells you that you need addition to the SimConnect.xml?

 

The file should read:

<?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>local</Scope>
    <Address></Address>
    <MaxClients>10</MaxClients>
    <Port></Port>
    <MaxRecvSize>8192</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
 <SimConnect.Comm>
    <Disabled>False</Disabled>
    <Protocol>IPv4</Protocol>
    <Scope>global</Scope>
    <Address>your FS PC's IP address </Address>
    <MaxClients>64</MaxClients>
    <Port>6600</Port>
    <MaxRecvSize>4096</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
</SimBase.Document>

See the Global support section added? You need to fill in the Address field.

 

Pete

[terenceskelton1]

Hi Pete.

 

Sorry for the delayed response. I was busy talking with my girlfriend!

 

Back to business!

 

I only hid my username on this post, because there are some clever computer hackers around! This is an open forum! I did not want my computer username to be displayed on an open forum!

 

I would actually have pm'd it to you, but I do not see that option on this site?

 

Going back though! I have always used that exact same .xml file, in win 7, and it worked perfectly. It never needed the global addition. Is the addition of the global support section peculiar to win 8?

 

Do you see what I am getting at? With 2 win 7 computers, networked in exactly the same way, with exactly the same .cfg and .xml files, it works perfect! So the question has to be asked, what is different in win 8 networking/simconnect?

 

But I will give it a try! I can't at the moment though, because I am upgrading to win 8.1 at the moment, and that takes a day or so, but I will get back to you as soon as possible.

 

I am unfortunate in that the supplied win 8 is the basic win 8. It lacks things like being able to actually show the network map! In win 7, the option is at the top of the screen to view the network map. In basic win 8, it is missing. According to Microsoft, the view network map is only available in win 8 pro!

 

Nevertheless, I can see the ip address of the laptop from the win 7 map, and both computers do see each other, and I can copy and paste between the shared files on both. I have user, fsx, Rex, all shared, with full control.

 

I would like to go back to something that you pointed out previously. Widefs works fine. You were surprised when I said that simconnect does not work, when widefs does? So, the win8/win7 network is fine. The laptop (client), is connected to the internet through the router connected to the server. I do not have wi-fi turned on! Basically, everything works, apart from REX!

 

Anyway, I made the decision to stick with REX, because of the included textures, but I will use it standalone on the server. Yes there is a frame rate hit when it is running on the server, and I do lose the weather map! I run fsx in full screen, on 4 monitors! If I try to use fsx in windowed mode, the frame rate loss is drammatic! Obviously, I cannot pull up the weather map in full screen mode. Not a great loss, but not the full functionality that I wanted!

 

Thanks for the support Pete, and for your time.

 

This one has got us all baffled! LOL!

 

Even Reed, who you will probably know, could not come up with a solution. He was really baffled why REX would not work! Everything was set up exactly as he has expected.

 

To answer your question about "Surely the documentation for networking REX tells you that you need addition to the SimConnect.xml?". No it is not mentioned. It only shows the one I pasted! No global support section, nor any mention of it..

 

Actually, I was a bit surprised that Reed did not ask me to attach my .cfg and .xml files, during our chat session. The option was there to attach files.

 

As things stand, REX does not work networked between a win8 and win 7 computer. I will try the global addition, and if that works, then our communication will have been a complete successI

 

I will be the very 1st one to sing lots of praises to you on this particular issue, if we can solve it.

 

As I said earlier, you have a fantastic reputation, and you have helped so many people. You are definitely a guru in the flight sim community, and we all respect you.Even if we cannot resolve this communication problem with simconnect on a win7/win8 network, your reputation will remain intact in my eyes.

 

FSUIPC and WideFs are a wonderful addition to our experiences, and we are all beholding to you for that.

 

Regards.

 

Terry

[terenceskelton1]

Hi Pete.

 

Just to clarify.

 

The "hidden" IP/username shown under local, is as I had explained. I did not want to post my actual username there either!

 

Regards

 

Terry

[Pete Dowson]

Going back though! I have always used that exact same .xml file, in win 7, and it worked perfectly. It never needed the global addition. Is the addition of the global support section peculiar to win 8?

 

I don't see how a purely local declaration in SimConnect.xml can provide any networked support. It is, as it implies, Local. It does not use the Address. So if you had it working before, it m

ust have got changed.

 

I would like to go back to something that you pointed out previously. Widefs works fine. You were surprised when I said that simconnect does not work, when widefs does?

 

Yes, because I assumed you had SimConnect configured correctly, which was evidently not true.

 

 

The "hidden" IP/username shown under local, is as I had explained. I did not want to post my actual username there either!

 

Why would your username be there? The address is simply the name of the computer, not you, OR its ip address, like 192.168.1.1. The computer name and its IP address are synonymous. Your user name is not involved.

 

Pete

[terenceskelton1]

Hi Pete.

 

I did not actually mean my username. I meant my computer name! For example Henry1-PC? I actually always used the IP address, but I have been playing around with switching between computer name and the IP address! Just trying anything and everything to get it to work! I saw posts where people had changed the IP address to the computer name, and then it worked, in different scenarios, but they probably had the wrong IPv4 address wrong in the 1st place!

 

I am sorry to have to disagree with you, but all I know is that this is a copy of the old .xml file that was fully working in win 7. I deliberately made sure that I made a copy, before I even changed anything. This is the copy from the old laptop!

 

<?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>local</Scope>
    <Address>192.168.0.102</Address>
    <MaxClients>10</MaxClients>
    <Port>6600</Port>
    <MaxRecvSize>8192</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
</SimBase.Document>

 

No global!

 

I assure you, I have never seen the addition of a global addition, and REX 2.0, REX essentials, REX essentials + OD, active sky, ASE, all worked perfectly with the basic .xml file that is included with all packages, with the appropriate IP address of course under local! I have never seen the global addition, nor ever had to use it!

 

 

Yes, because I assumed you had SimConnect configured correctly, which was evidently not true.

 

 

Evidently not true? I absolutely assure you that simconnect worked perfectly as posted above! It worked on my old laptop, (which that .xml file is directly copied from, but the IP address has now changed!), and it worked when I installed win 7 on the new laptop!

 

Pete, I hope that you do not get the wrong idea. I am not questioning your expertise. I am merely stating a fact! The fact is that REX, ASE and all other add ons that I have used over the years, have never had the global addition to the .xml file, and they all worked!

 

I very seldom have to resort to asking questions on support forums, because any issues that I have had, have always been posted/answered before.

 

This post has never been posted before.

 

I am very aware of the pitfalls of people overlooking the simple things, like making sure that the .cfg and .xml files are actually in the right place, same IP address, same port! I am very aware of the fact that people do not check the actual IP address of the client and server, although the client IP adress is not actually required (except for Opus!)!

 

Pete, please do not treat me as a dunce!

 

I will try the new global .xml addition, but I can't do that yet! I am downloading the latest win 8.1 update, and that takes all night!

 

I very much doubt that it will make any difference though, but I will try it! I never needed it before though.

 

Just in case you are thinking, no I have not added any new hardware/router or anything! I changed the laptop, and that is when my problems started!

 

As I said before. With that exact same .xml file, and the same .cfg file, located in the same place (.xml in the user//appdata/roaming/microsoft/fsx, on the server, and the .cfg file placed in the my documents folder on the client), in a win7 to win7 network, it worked fine (with the appropriate changes to the IP address). That was with both the old laptop, and the new one!

 

You are questioning my setup, when I assure you, that it always worked before, without the global addition?

 

Maybe you are not familiar with the way REX works? Maybe REX does not require a global addition? Maybe it automatically embeds a global IP address, based on the local address?

 

I don't know!

 

All I can tell you is that it always worked without the global addition.

 

All my other programs, FSC and PFE use widefs, and they both work fine on the new win8.1 laptop!

 

Internet, shared folders are all working fine.

 

This is a new phenomonen to all of us! REX themselves cannot figure it out! From my extensive search on the internet, I have not seen any posts about simconnect not working between a win7/win8 setup.

 

Pete, when I get win 8.1 installed, I will try out the global addition and I will report back to you.

 

In the meantime, please do not treat me as a "beginner".

 

I am not as knowledgable as you, but I can assure you that I never needed the global addition to my .xml file before!

 

Regards.

 

Terry

[Pete Dowson]

I am not as knowledgable as you

 

Evidently not true, it seems.

 

, but I can assure you that I never needed the global addition to my .xml file before!

 

Well, sorry, then. Evidently I don't have a clue. I've always had the Global section in, and absolutely thought that necessary. But if it still doesn't work for you, obviously I'm wrong. Sorry.

 

Oh, and I never tried treating you as a "dunce" or a "beginner". I wasn't treating you as anything at all, only trying to be as helpful as possible on a matter which is really nothing to do with me. I find to your attitude rather insulting and will not respond again, as obviously any advice I give is unwanted as well as possibly incorrect..

 

Goodnight.

 

Pete

[terenceskelton1]

Hi Pete.

 

My apologies if I sounded sarcastic. It was not intended.

 

I am merely sticking to the facts.

 

After the 8.1 upgrade, I used the .xml file that you posted (copy and paste), and changed the IPv4 address accordingly. It did not work. I still had exactly the same problem.

 

Thanks anyway for trying to help out.

 

It was appreciated.

 

Regards.

 

Terry

[terenceskelton1]

Hi Pete.

 

I know that you and I got off on the wrong foot, and we seemed to have misinterpreted the "meaning" behind our communication. Believe me, it was not intentional to "sound" sarcastic.

 

I am also on various forums, to discuss our FSX problems, for the good of the community.

 

Just to put the record straight though, and for the sake of those people who may come across this problem and see this post.

 

This is NOT being sarcastic, nor is it anything to do with attitude. Let us get that straight!

 

I do not want to put people off track by trying things out that are not necessary!

 

I wanted to be sure that I was absolutely correct in saying that simconnect did not need the global addition to the simconnect.xml file.

 

I actually tried both, with global and local, with the double entries (as per your post), and without double entries.

 

To clarify this to everyone. Simconnect does not need the global addition.

 

This is my simconnect.xml file, and it works perfectly!

 

<?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>local</Scope>
    <Address>192.168.0.102</Address>
    <MaxClients>100</MaxClients>
    <Port>6600</Port>
    <MaxRecvSize>8192</MaxRecvSize>
    <DisableNagle>False</DisableNagle>
  </SimConnect.Comm>
</SimBase.Document>

 

No double entries, no global "scope".

 

Local or global both work fine, so you can use either!

 

I have still not been able to resolve my problem of simconnect not working on a win 7/ win 8 network though!

 

REX also works fine standalone in win 8, so it is not an REX compatability issue.

 

If anyone has any ideas, I would welcome any input.

 

Finally, I would like to say that I still have a high regard for Pete Dowson. He has done a wonderful job with FSUIPC, and I applaud him for that.

 

Regards

 

Terry

[alaxus]

I have still not been able to resolve my problem of simconnect not working on a win 7/ win 8 network though!

 

You could try resetting the network stack https://www.google.com.au/webhp?hl=en&tab=ii#hl=en&q=windows+8+network+stack+issues&spell=1

[Luke Kolin]

Before you reset the network stack have you checked that a) the IP address for the server is correct, and b) the firewall isn't blocking the port for SimConnect?

 

Cheers!

 

Luke

[terenceskelton1]

Hi Luke.

 

Thanks for the input.

 

I had doubts that resetting the network stack would have made any difference, but I did try it and it made no difference.

 

Yes, I did double and triple check the IPv4 address. Firewall is turned off. In win 8 there is actually a hidden "domain" firewall, which is not turned off when you turn off the main firewall. I did turn that off as well! I also disabled the antivirus.

 

REX still refuses to connect in a win 7/ win 8 network.

 

I actually may have a slight apology to make to Pete Dowson! After a bit of research, I found that the global scope that he insisted was necessary is actually related to whether you have FSX SDK SP1 or SP2 installed. FSX SP2 SDK does appear to need the global scope, and not local scope. It has nothing to do with FSX SP2. They are 2 different animals, and that is where Pete may have got confused! I can assure anyone who has FSX SP2 intalled, you do not require to have the global scope! Do not confuse FSX with SP2, with simconnect SDK SP2! Any add ons that you may install will have their own simconnect.msi installer. Some require simconnect local scope, and some require global, and some don't care! REX works fine with either local or global scope.

 

I hope I have cleared that up!

 

I did try tracert, and that showed that both computers recognized each other on the network, so the IP adresses are correct. I knew that anyway, because I have full control between both computers on the network, on the shared folders.WideFs aslo works fine. Mapped folder access also works fine!

 

There is something weird in the coding of simconnect that windows 8 does not like sharing with windows 7? That is a question, because I do not know! All I know is that the same laptop, with the same configuration, running the same program, running the same simconnect version, works fine in win 7/ win 7 network but not in a win 7/ win 8 network!

 

Anyway. I have given up now. I will leave to REX to sort it out. In the meantime, I am going back to win 7 on the new laptop!

 

I just want to fly!

 

Regards.

 

Terry

[Luke Kolin]

Can you telnet to the server using port 6600? That should test whether it can work or not - if you can't either FSX isn't running or something is blocking the connection.

 

Cheers!

Luke

[terenceskelton1]

Hi.

 

Too late!

 

I have already reformatted and loaded win 7!

 

I did actually try telnet, on someone elses advice, but there were no instructions! I fumbled with it and got a fail. Nothing was said about having FSX running when I did the telnet cmd line test though!

 

I also got a fail when I tried it on the old win 7 laptop, which was working, but the fact was that I did not have FSX running on that at the time either! That explains why it failed on both systems!

 

Even if it had failed, It was then suggested that I have to find out what was blocking the port, and which ports were available! Then I was lost! LOL!

 

Thanks anyway for trying to help out! Much appreciated

 

Regards.

 

Terry

[terenceskelton1]

Hi guys.

 

To anyone who is following this post!

 

I finally got to the bottom of the problem! Not solved, but found the problem!

 

I did a lot of digging and experimenting! I saw a suggestion of using currports! That gave me a lot of info about what was going on!

I have finally pinned it down! It is not the laptop, nor the router, nor firewall, nor my simconnect settings!

REX Essentials + OD does not open the port, when running in win 8!

It has got to be something within the program that does not use win 8 networking protocols properly?

The program makers have told me that they have not tried a win 8/ win 7 network.

How did I come to that conclusion? Easy really! I loaded FSX onto the new laptop, running win 8, and it opened port 6600 when it was loaded! REX did not open the port! It did not show up at all!

I also did try running REX on the desktop (server) with FSX running on the new laptop (client), and REX opened the port 6600 in win 7 and injected the weather fine into FSX running on the laptop, which was also showing receiving port 6600! So the port was opening, but only on a win 7 to win 8 network, but not the other way round? REX was opening port 6600 on both the desktop and the laptop running in win 7, but in win 8 REX will not open the port! It is not a simconnect problem, because FSX was opening port 6600 on the laptop, running win 8!

That also explains why the old laptop, running the same setup, but running win 7, worked fine!

Finally, I can get some sleep! LOL!

I hope this had been of some help to anyone who has the same problem, and to help anyone who is considering getting REX, and has a win 7/ win 8 network. REX will not work if it is run on a client running under win 8, networked to a win 7 or win 8 server! Yes I did actually install win 8 on the server, and tried a win 8 to win 8 REX simconnect setup. Same thing! Both ways, REX would not open the port running in win 8, neither on the server or the client!

Have yourself a Merry Xmas.

Regards.

Terry

[terenceskelton1]

Hi.

Well I will be darned!

I have been struggling with this issue with both REX and AS2012 not connecting via simconnect in a win 7 (server) to win 8 (client) network, on a new laptop, for 6weeks now. I have double

and triple checked the simconnect.xml and simconnect.cfg files, made sure they were in the right place, and double checked that the files were identical to the original win 7 to win 7

network I have on another laptop, which worked fine! I followed exactly, all the setup instructions.

Today, I tried something new. I downloaded and installed the simconnect config tool, ran it on both the server and the client, and hey presto, it all works fine now! I have had a look at

the simconnect.xml file, and it is different to any examples I have seen, and been given, and different to the original one that worked on the win 7 old laptop!

For the record, this is the simconnect.xml file.

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="SimConnect" version="1,0">

<Descr>SimConnect Server Configuration</Descr>

<Filename>SimConnect.xml</Filename>

<Disabled>False</Disabled>

<SimConnect.Comm>

<Disabled>False</Disabled>

<Protocol>IPv4</Protocol>

<Scope>Global</Scope>

<MaxClients>64</MaxClients>

<Address>192.168.0.100</Address>

<Port>6600</Port>

</SimConnect.Comm>

</SimBase.Document>

For some reason, this works! Note the exclusion of the <MaxRecvSize<8192<MaxRecvSize>, and the exclusion of the <DisableNagle>False</DisableNagle>, which exists in a normal simconnect.xml

file!

The simconnect.cfg file is,

[simConnect]

Protocol=Ipv4

Address=192.168.0.100

Port=6600

MaxReceiveSize=8192

DisableNagle=1

I do not know how or why this works, but it does! It is something peculiar to win 8! The standard simconnect.xml and .cfg files will not work in win 8! How the simconnect config tool sorted it out, I have no idea!

Anyway, the problem is now resolved and I am posting this in order to help anyone else out who may come across the same problem.

Regards, and Happy New Year.

Terry

[Shomideep Rio Maulik]

Hey Terry,

 

I did as shown but with my IP of course and it does not work. Could you please maybe upload a video or screen shot on exactly what you did.

Thanks

[terenceskelton1]

Hi.

 

No video or screen shot necessary.

 

I am sorry that my fix does not work in your case.

 

Have you downloaded and run the simconnect config tool from http//simconnectconfigtool.codeplex.com, on both the client and the server, and adjusted the IP addresses for your system?

 

I gather that you read the whole post? There are a number of other things that could stop simconnect from working.

 

Have you tried currports to check whether the computers are opening the same port?

 

Firewall maybe? I have tried with both windows firewall turned on and off, and antivirus firewall on and off, and none of them interfered with simconnect though.

 

I am sorry that I cannot be of much help, but maybe some others who are more knowledgeable than I am on networking maybe able to shed some light on your particular problem.

 

Cheers.

 

Terry