Can't get WideClient to not use the WIFI connection

[IceMan II]

Hi Pete,

I know nothing about Computers so your manual regarding setting up a client computer to a server was a little over the top for me. I'm trying to set up PFE & AS2012 on the client computer. I followed the instructions for the AS2012 setup via simconnect and although I had no idea what I was doing, like magic it works. Same with WideClient but the setup was easier and work fine until I disconnected the wireless network and realized WideClient was using the WIFI not the cable.

I have W7 on both computers using a crossover cable to connect. Both are computers ared connected to the internet via my home WIFI system as well.

I read your bit in the manual about "Gotchas" and the possibility for WideClient to favour WIFI over cable but I did Not fully understand the FIX.

If I disable the internet from one of the computers I loose the WideClient connection. Is it possible that I cannot use AS2012 via simconnect and PFE via WideClient down the same crossover cable at the same time.

I know PFE wont use Simconnect but for some reason I couldnt get AS2012 to use WideClient hence the simconnect option.

thanks in advance

ICM 2

[Pete Dowson]

I know nothing about Computers so your manual regarding setting up a client computer to a server was a little over the top for me

I think you must be a little confused. There's really nothing about such setting up in any manual of mine -- only the important provision of EITHER making sure both PCs were in the same Workgroup, OR, if not, then instead providing the Client program with the name of the Server so it can find it, plus the protocol to be used.

WideFS works "out of the box" on a working network with those provisos only. There's nothing else to know really, and certainly I'm not able to teach anything about setting up networks, a subject I know very little of myself.

I'm trying to set up PFE & AS2012 on the client computer. I followed the instructions for the AS2012 setup via simconnect and although I had no idea what I was doing, like magic it works. Same with WideClient but the setup was easier and work fine until I disconnected the wireless network and realized WideClient was using the WIFI not the cable.

WideFS has no way of distinguishing the route Windows chooses for its interconnections. Not by itself in any case. Having both routes enabled is most unusual in any case, and can result in data getting jumbled as it has two routes it can follow at different speeds!

I read your bit in the manual about "Gotchas" and the possibility for WideClient to favour WIFI over cable but I did Not fully understand the FIX.

Is there a bit about that? If so it isn't by me -- must be in the section where I collected advice from others, such as in messages in this Forum. Can you point out the FIX, in case I can understand it any better?

If I disable the internet from one of the computers I loose the WideClient connection. Is it possible that I cannot use AS2012 via simconnect and PFE via WideClient down the same crossover cable at the same time.

It should be possible, but I have no idea how you make Windows choose one over the other. WideClient simply asks Windows to connect it to the Server. One thought is that perhaps the wired connection in the Server has a different IP address to the wireless connection. I think that this must be the case unless you explicitly "bridged" them to the same IP address. Didn't you have to specify an IP address for Simconnect? If so, try setting the same IP address in the Client's INI file, plus "Protocol=TCP".

I know PFE wont use Simconnect but for some reason I couldnt get AS2012 to use WideClient hence the simconnect option.[/CODE]

Active Sky uses WidFS for FS9 and SimConnect for FSX. With ASE you could fool it into using WideFS by telling it that it was connecting to FS9. I don't think AS 2012 supports FS9, does it?

Regards

Pete

[IceMan II]

Thanks for the reply.

I'm cuna try starting the two computers without the wireless internet connection and see if windows will get WidFS to use the cable..

I went FSX flying for the first time today using the client/server setup with good results until I got the CTD & ATC.dll error. Maybe due to data getting jumbled as you put it.

Yes I did need to enter an IP address to setup the crossover cable network and added this to the Simconnect INI. As you say the WideClient just works with windows behind the scene, which is the beauty of the product.

Thanks for your input and I'll go away and try a few things.

IM2

[Pete Dowson]

I went FSX flying for the first time today using the client/server setup with good results until I got the CTD & ATC.dll error. Maybe due to data getting jumbled as you put it.

Data won't get jumbled using TCP protocol, only UDP -- Windows explorer uses UDP for file transfers.

What is this "CTD & ATC.DLL" error? I'm not aware of any such error in FSX.

Yes I did need to enter an IP address to setup the crossover cable network and added this to the Simconnect INI. As you say the WideClient just works with windows behind the scene, which is the beauty of the product.

Use the same IP address in the WideClient INI. Add both "ServerIPAddr= ..." and "Protocol=TCP" parameters to the [Config] section of the WideClient.INI file.

Regards

Pete

[IceMan II]

Thanks for your time Pete, I know you've got better things to do..

That did the trick thanks, I was not sure what to type in until you spelled it out and adding that bit to the config saves me having to start up wideclient without the internet connection then reconnect after it has found the path thu the crossover.

Sounds odd but since I've done this and all data going via the same route I have had no more SIM crashes showing an ATC.dll fault. (which I assume is from PFE but makes no sense to me)

thanks again Peter

all is perfect now!!

IM