Hi.I have 1PC running FSX and a Laptop running FSC, ASE, RC, etc..... Both pc's are connected to the internet via a wireless router and together via a crossover ethernet cable. ASE etc. runs fine on the laptop but will only communicate via the wireless connection. If I disable the wireless connection ASE, FSC etc. will stop communicating with FSX on my main PC. However I can still transfer files and folders via the Ethernet link.I Wish to use the Ethernet connection as it is faster than the wirless connection.I hope that explains things!!!! Any help much appreciated.Martin.

I'm not a network pro, but I have one or another idea about it. Built my homenetwork with two routers, one wireless, myself.I don't believe the setup you are wishing for is possible - someone correct me please if I'm wrong.The problem is that via crossover cable your router is bypassed, so is any TCP/IP communication I think.And there is no way to tell windows what you want to do. I guess you want to transfer files between computers and wireless is too slow.You should do what I do: get a 2nd router in the network, connect your two computers over that router. There are routers which can connect to other wireless router wirelessly... eg. client mode, WDS...Only my routers are connected by the cable through the complete home network, since my main router in the basement, two floors down (no connection per wireless).

Thanks for your reply Word Not Allowed.I can transfer files both wirelessly and if I disconnect 1 machine from the router (by clicking the strengh icon and disconnecting) and via the crossover cable. WideFS and SimConnect will only connect wirelessly.Your suggesting I get another router and conenect the 2 pc's via a cable to that and that should work???Surely there must be a way to have wideFS and Simconnect communicate via the crossover cable the way I have it set up at the moment???Martin.

Of course - all networking programs rely on TCP/IP protocols, and crossover cable doesn't provide that.No, I suggest you get a 2nd router and WIRELESSLY connect it, as a client to the first router, and your two computer with a cable to the 2nd router - thus providing a fast connection between two computers, but also a tcp/ip support.EDIT: I was wrong. I googled crossover cable and found out that TCP/IP is indeed used.But still, I see a problem: let's say your WLAN adapter has an IP 192.168.1.100, you set your NIC on that puter to 101, both can't have the same IP, and the laptop same, WLAN is 102 and RJ45 is 103. So, how would you configure WideFS or Simconnect to use TWO IPs? You can try forcing it to the IP of the network NIC, but still, no way to communicate to the internet then.

Thanks for your reply Word Not Allowed.I can transfer files both wirelessly and if I disconnect 1 machine from the router (by clicking the strengh icon and disconnecting) and via the crossover cable. WideFS and SimConnect will only connect wirelessly.Your suggesting I get another router and conenect the 2 pc's via a cable to that and that should work???Surely there must be a way to have wideFS and Simconnect communicate via the crossover cable the way I have it set up at the moment???Martin.

Your wired LAN connections made via the crossover cable should have a different set of IP addresses than your wireless connections. You'll need to change the server IP addresses specified in the simconnect.cfg (client), simconnect.xml (server), and WideClient.cfg (client) files to reflect the IP address and port number of the wired connection to the server, not the IP of the 802.11 wireless connection.

Thanks Bob. In the WideClient.cfg and the Simconnect.xml files I have the name of the server, not the ip addresses. I will try changing them to reflect the ip addresses of the wired connection.Thanks, Martin.

Hello again Bob.Just tried changing the ip addresses of wideclient and simconnect. No luck.Do I need to change the port numbers as well?? What port numbers should I use???Martin.

You shouldn't have to change the ports around. I'd double-check the firewall settings.

Just tried changing the ip addresses of wideclient and simconnect. No luck.

Can you say what you did exactly? Like what machine is what ip and what are both wideclient.cfg and simconnect.cfg set.

Hello again Word Not Allowed.My ipconfig on my fsx pc is this: My WideClient.ini file on my laptop looks like this: My Simconnect.XML file (when in edit mode) is this: All I did was to change the wideclient.ini file to read ServerIPAddress=169.254.164.99 instead of ServerName=And the simconnect.xml.file to address 169.254.164.99 in the local IPv4 server section at the bottom.Once again Chaps, thanks' for your help!!!!!Martin.

Your somconnect.xml is in the same folder as fsx.cfg, right?And if yes, then I wouldn't know where to begin with it.My simconnect.xml is way shorter, yours apparently lists all adapters - not really sure if it's needed.Anyway, in the simconnect.xml you have to specify the IP address of the simconnect server, eg. your main machine, I guess that would be 169.254.164.99.Also, I'm not really sure about the subnet mask, which is in this case different for WLAN and for direct connection (255.255.255.0 vs 255.255.0.0). I know my two routers need the same subnet mask.2nd, the IP on the local NIC is a windows generated one when no DHCP is provided. You could try setting it to 192.168... whatever your computers are called, a number in the row.But really, I'm very much only guessing here. I hope there is someone who can really help you.This is my 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.1.100</Address> <MaxClients>64</MaxClients> <Port>1040</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm><SimConnect.Comm><Disabled>False</Disabled><Protocol>Auto</Protocol><Scope>local</Scope></SimConnect.Comm></SimBase.Document>WideClient has never had any IP settings. This thing has always worked without anything, and connected as soon as a valid network connection existed.Maybe a network bridge would help in this case? Never really played with it, nor I know how it really functions, but hey... trying to help a bit :)

Thanks for your suggestions. I will try changing the ethernet address tomorrow. Do I need to change the ethernet address on the remote pc (laptop) as well????Martin.

Well, I don't know about the crossover cable, but with a router, as you already noticed a network is built - with assigned network addresses 192.168...etc. So if you change on the fixed NIC on the PC, you have to change on the laptop too.That would be a place where I would start at least.It should work though, as I have looked up: basically between two PCs the only downside is non-existance of DHCP and automatical assigning. So if you assign manually, it should be the *same* as with a router in between.Actually, it has been bugging me lately that my laptop is hanging on the 54g WLAN with my main PC, installing some textures is really slow - that would be for the only reason for connecting them together.What do you need it for really? If you have ASE, then you have no textures... and rest can be easily done over WLAN. File transfer is working also you say.

BINGO!!!!! Well sort of!!!With both pc's disconnected from the wireless router it works fine. connect the laptop to the wireless router it falls over. Something to do with my homegroup settings i'm sure (both pc's running windows 7).With a bit of fiddling I can get it to work though. I shall experiment further.The reason I want Simconnect and WideClient on the wired connection is that I was getting the occasional stutter in FS, and RC was sometimes slow to respond. I put it down to a (relatively) slow wireless connection between the 2 pc's. We shall see.Anyway. Thankyou for all your help in this matter, much appreciated. I owe you a virtual pint!!!!Cheers!!! Martin.

The reason I want Simconnect and WideClient on the wired connection is that I was getting the occasional stutter in FS, and RC was sometimes slow to respond. I put it down to a (relatively) slow wireless connection between the 2 pc's. We shall see.

You might want to try setting the connection protocol to UDP (broadcast mode) rather than TCP/IP...it will eliminate any delays due to handshaking, but at risk of possibly dropping the occasional packet if the connection isn't solid. That said, a decent modern wireless connection at 11Mbps or better should be more than fast enough.

Edited February 2, 201214 yr by w6kd