Jump to content
The simFlight Network Forums

FSUIPC 4.70 (b) & WideFS 6.86 don't get connected


Recommended Posts

Peter,

FSX was running with an older FSUIPC on Win7-64 and the 2nd PC on WinXP-32 with an old version of WideFS. Yesterday I upgraded to FSUIPC 4.70 (B) and WideFS 6.86 and since that time I do not get any connection anymore. The WideFS.log shows the following information:

********* WideClient Log [version 6.86] Class=FS98MAIN *********

Date (dmy): 30/04/11, Time 13:58:17.937: Client name is MARS

391 Attempting to connect now

407 LUA: "C:\Programme\WideFS\Initial.LUA": not found

625 Server = JUPITER

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

641 ... Okay, IP Address = 192.168.0.100

641 Client connect() failed [Error=10013] Permission denied

2641 Trying to locate server: Need details from Server Broadcast

5625 Server = JUPITER

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

5625 ... Okay, IP Address = 192.168.0.100

5625 Client connect() failed [Error=10013] Permission denied

8625 Server = JUPITER

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

8625 ... Okay, IP Address = 192.168.0.100

8625 Client connect() failed [Error=10013] Permission denied

10641 Giving up server, looking for another!

11625 Server = JUPITER

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

11641 ... Okay, IP Address = 192.168.0.100

11641 Client connect() failed [Error=10013] Permission denied

13282 ****** End of session performance summary ******

13282 Total time connected = 0 seconds

13282 Reception maximum: 0 frames/sec, 0 bytes/sec

13282 Transmission maximum: 0 frames/sec, 0 bytes/sec

13282 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

13282 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

As WideFS is able to determine the host name it looks to me that the IP connection is available. I reinstalled already WideFS and FSUIPC many times but can not figure out the issue. Therefore I do require your support.

Thank you in advance.

Kind regards

Christian

Link to comment
Share on other sites

FSX was running with an older FSUIPC on Win7-64 and the 2nd PC on WinXP-32 with an old version of WideFS. Yesterday I upgraded to FSUIPC 4.70 (B) and WideFS 6.86 and since that time I do not get any connection anymore.

There#s been absolutely no change in anything to do with WideFS connections for many years. Something else must have changed too.

The WideFS.log shows the following information:

That's just the WideClient log. There should also be a WideServer.Log and FSUIPC4.log, in the FSX Modules folder. What do they show?

641 Client connect() failed [Error=10013] Permission denied

Permission denied seems to imply a firewall blockage. Maybe you allowed the old WideClient access through the firewall, and for some reason the update isn't seen as the same progam? Maybe a different folder, or perhaps the firewall does version checking? (I don't really know anything about firewalls as I've never used one).

As WideFS is able to determine the host name it looks to me that the IP connection is available.

It is obviously available as WideClient is receiving the host name and IP address okay.

I reinstalled already WideFS and FSUIPC many times but can not figure out the issue.

I've never ever known reinstalling to solve any problem with any of my programs as all you are doing is replacing on binary file with the exact same binary file.

Regards

Pete

Link to comment
Share on other sites

Even I am shutting down both firewalls the problem still exist.

WideFSServer.log shows:

********* WideServer.DLL Log [version 7.703] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 30/04/11, Time 16:10:13.805: Server name is JUPITER

15943 Initialising TCP/IP server

15943 Initialising IPX/SPX server

15943 IPX/SPX socket() failed [Error=10044] Socket type not supported

15943 Failed to start IPX/SPX Server

15943 Initialising UDP/IP server

16099 Broadcasting service every 1000 mSecs

142881 Closing down now ...

Memory managed: Offset records: 62 alloc, 61 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

FSUIPC.log:

********* FSUIPC4, Version 4.703 by Pete Dowson *********

Reading options from "E:\FSX\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Christian Kaack"

User Addr="christian.kaack@gmx.de"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

172 System time = 30/04/2011 16:09:47

172 FLT UNC path = "\\JUPITER\Dateien\"

172 FS UNC path = "\\JUPITER\FSX\"

515 LogOptions=00000000 00000001

515 SimConnect_Open succeeded: waiting to check version okay

5694 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

5694 Initialising SimConnect data requests now

5694 FSUIPC Menu entry added

5725 \\JUPITER\Dateien\Standardflug.FLT

5725 D:\Documents\Flight Simulator X-Dateien\EDHIEDDF.PLN

5725 \\JUPITER\FSX\SimObjects\Airplanes\Project Airbus PIC A319\FeelThere_A319CFM.AIR

5725 D:\Documents\Flight Simulator X-Dateien\EDHIEDDF.PLN

26052 System time = 30/04/2011 16:10:13, Simulator time = 16:09:54 (14:09Z)

26052 Aircraft="PA A319 CFM SkyAir"

26255 Starting everything now ...

27378 Advanced Weather Interface Enabled

163333 Sim stopped: average frame rate for last 138 secs = 85.7 fps

171492 System time = 30/04/2011 16:12:39, Simulator time = 16:12:11 (14:12Z)

171492 *** FSUIPC log file being closed

Average frame rate for running time of 138 secs = 85.7 fps

Memory managed: 62 Allocs, 62 Freed

********* FSUIPC Log file closed ***********

I am lost at this point.

Link to comment
Share on other sites

Even I am shutting down both firewalls the problem still exist.

Well, Error=10013, "Permission denied" could also mean that the port used by WideFS (8002) is already in use by something else. Here;s the Microsoft explanation i just googled:

Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).

Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Have you got anything else using that port (on either PC)? 9002 is obviously okay -- that is used for the Broadcasting which is working. Check, for example, the SimConnect.xml file. If you set SimConnect to use that port it will get it long before WideServer does.

You could also try a different port by changing the parameter in both WideClient.INI and the [wideServer] section of FSUIPC4.INI.

What I don't understand is how things have changed since you had it working. There's certainly nothing different this area in any versions of FSUIPC or WideClient for years.

Regards

Pete

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.