Jump to content
The simFlight Network Forums

Tutorial: Connection over a network


jahman
 Share

Recommended Posts

Just thought I would share these tips for getting your FSCommander to

connecto to FSX over a network:

1. Make sure Client and Server are on the same "Network Group".

With Vista, go to "Control Panel/System and Maintenance/System"

and under "Computer Name, Domain and Workgroup Settings/Workgroup"

you will see the name of your workgroup. Again Client and Server

*must* be on the same workgroup else WideFS Client will FAIL to

connect to WideServer, so do check the two workgroups are *exactly*

the same.

2. Use UIPCHello on both Client and Server to make sure WideClient

and WideServer are running properly.

See: viewtopic.php?f=155&t=78663#p478936

Or: download/file.php?id=81503

3. Delete FSCommander desktop icon and re-create from FSC folder

as installer-created icon is incomplete (not all fields filled).

4. Make sure FSUIPC v. 4.57 is paired with WideClient v. 6.791

(or check p. 1 of the WideFS User Guide if working with different

versions.

5. Both MS-FSX on the Server and WideClient ("FS Eliminator for

FSUIPC client applications") must be listed under Firewall

Exceptions. In Vista, go to "Control Panel/Security" and under

"Windows Firewall" clock on "Allow a program through Windows

Firewall". This will open the window "Windows Firewall Settings"

at the "Exceptions" tab. On the server verify "Microsoft Flight

Simulator" is checked. On the client do the same for "FS Eliminator

for FSUIPC client applications".

6. In FSUIPC.ini must have:

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

7. FSUIPC4.log must show:

FSUIPC4 Key is provided

WideFS7 Key is provided

8. WideServer.DLL log must show:

Broadcasting service every 1000 mSecs

indicating the server is active.

9. WideClient.log must have:

[Config]

Port=8002

Port2=9002

Window=810,960,470,34

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

10. WideClient.log must show:

Server =

Trying TCP/IP host "" port 8002 ...

Okay, IP Address =

Connection made okay!

New Client Application: "FSC86" (Id=2076)

11. Once you get your setup working, you can easily automate starting

WideFS client, FSCommander and GPS tracking as follows:

a. Add WideFS client shortcut to your client PC Startup menu

directory for auto-starting when booting. In Vista the Startup

directory is:

"c:\Users\\AppData\Roaming\Microsoft\Windows

\Start Menu\Programs\Startup".

b. Set FSCommander v. 8.6 "Window/Options/Display/Direct Connection

with FS" to "checked".

c. To hide the WideFS client window, in WideClient.ini, change:

[Config]

Visible=Yes

to:

Visible=No

Have fun!

- jahman.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.