WideFS makes connection, but doesn't send/receive anything

[mverbeke]

Hello!

If I start FS9 (with fsuipc AND WideFS) and wideclient on my laptop. WideClient AND FS9 says there is a connection.

But if I start FSIP200x I get an error: "connection failed - fsip shutdown - check WideFS connected"

Then I was looking if WideClient is actualy recieving AND sending date by setting up the buttonscreen.

If WideClient starts, I see all the programmed buttons, but none of the buttons works!

What could the problem be?

Thanks in Advance

Matthias

WideServer.ini:

; PLEASE SEE the documentation for parameter details

; ==================================================

[Config]

Port=8002

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[ClientNames]

1=LAPTOP

WideClient.ini:

; PLEASE SEE WideFS documentation for parameter details

; =====================================================

[Config]

Port=8002

Window=53,8,600,776

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

ServerName=server

ServerIPAddr=10.0.0.100

Protocol=TCP

; -----------------------------------------------

[user]

Log=Debug

ButtonScreen=Yes

[buttonScreen]

Size=4,5

0=T"Pause"

1=T"Slew"

2=B"Clear\rWeather"

3=B"Toggle\rTraffic"

4=B"Refresh\rScenery"

5=Ba"ESCape"

6=Bt"Cursor\rUp"

7=Ba"Home"

8=B"Reload\rAircraft"

9=Bl"Cursor\rLeft"

10=B"Stop/Clr\r(Num 5)"

11=Br"Cursor\rRight"

12=B"Restart\rFlight"

13=Ba"ALT\r(to get to\rFS menus)"

14=Bb"Cursor\rDown"

15=Ba"End"

16=B"Return"

17=B"Space\rBar"

; ===============================================

[Pete Dowson]

If I start FS9 (with fsuipc AND WideFS) and wideclient on my laptop. WideClient AND FS9 says there is a connection. But if I start FSIP200x I get an error: "connection failed - fsip shutdown - check WideFS connected"

Never heard of FSIP200x. But it doesn't matter. What I need to see (as always) are the Log files. There will be a WideServer.Log on the Server and a WideClient.Log on the client.

I see from your WideClient.INI file you have specified these:

ServerName=server

ServerIPAddr=10.0.0.100

Protocol=TCP

Why? Are you using Windows98, not XP? If you are using Windows XP all round you can let WideFS connect automatically.

Also it is redundant to provide both the IP Address and the Server name -- the Name will be completely ignored. You are best only giving the name, in case the IP address changes.

All these things are explained in the documentation provided.

Additionally, I notice this in the INI:

[user]

Log=Debug

Why are you specifying Debug logging (making a HUGE file) here, yet not even bothering to look at the Log when you have a problem?

In the first instance, I don't want to see Debug logging as it is far too much data to wade through. Please change that back to "Log=Errors+", or simply delete it so that defaults.

Finally, ALWAYS provide version numbers. If you are not using the currently supported version of WideFS (6.75) or later, for both Server and Client, please do so first, and test again.

Oh, I need to see the FSUIPC.Log from the Server too, please. A complete one, after FS has closed.

Regards

Pete

[mverbeke]

Hello Pete,

First, I want to thank you for the fast response!

FSIP200x is a instructor panel (http://www.fsip200x.com)...

I'm working with VISTA on the server side and XP on the client side!

The WideFS version is 6.75 (on both server and client!)

I made the changes to the ini-files, but even then it doesn't work.

Here you have the log files:

fsuipc.log:

********* FSUIPC, Version 3.75 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "D:\Vista programs\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004(original release)

User Name="ronny naeyaert"

User Addr="ronny.naeyaert@fulladsl.be"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=40003605[40003605]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

1406 System time = 12:21:59

1406 D:\Vista programs\Microsoft Games\Flight Simulator 9\

1406 System time = 12:21:59, FS2004 time = 12:00:00 (00:00Z)

2640 C:\Users\Matthias\Documents\Flight Simulator Files\eigen panel.flt

2656 AIRCRAFT\c172\Cessna172SP.air

3375 Aircraft="Cessna Skyhawk 172SP eigen panel2"

8781 C:\Users\Matthias\Documents\Flight Simulator Files\eigen panel.flt

8937 Clear All Weather requested: external weather discarded

9703 Advanced Weather Interface Enabled

88109 System time = 12:23:26, FS2004 time = 12:30:24 (11:30Z)

88109 *** FSUIPC log file being closed

Memory managed: 0 Allocs, 1086 Freed

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

The wideserver.log:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 28/10/07, Time 12:22:00.063: Server name is SERVER

18016 Initialising TCP/IP server

18031 Initialising IPX/SPX server

18031 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

18031 Failed to start IPX/SPX Server

18031 Initialising UDP/IP server

18156 Broadcasting service every 1000 mSecs

18360 Incoming connection Accepted ok (skt=2848) TCP

18641 Connected to computer "LAPTOP" running WideClient version 6.750 (skt=2848) TCP

91797 Close signalled to clients

92891 Closing down now ...

Memory managed: Offset records: 65 alloc, 65 free

Read buffer usage: 40 alloc, 40 free, max in session: 1

Write buffer usage: 828 alloc, 828 free, max in session: 1

Throughput maximum achieved: 10 frames/sec, 1612 bytes/sec

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

Average receive rate from "LAPTOP": 0 frames/sec, 20 bytes/sec

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

The wideclient.log:

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

Date (dmy): 28/10/07, Time 12:22:15.719: Client name is LAPTOP

451 Attempting to connect now

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

491Okay, IP Address = 10.0.0.200

1463 Error on client pre-Connection Select() [Error=10061] Connection refused

1473 Ready to try connection again

2514 Attempting to connect now

4517 Connection made okay!

72455 Received shutdown offset code = ADBC

72455 FS closing down (param=ADBC), disconnecting

72455 ********* Interim performance summary *********

72455 Total time connected so far = 68 seconds

72455 Reception maximum so far: 10 frames/sec, 1642 bytes/sec

72455 Reception average whilst connected so far: 8 frames/sec, 961 bytes/sec

72455 Transmission maximum so far: 1 frames/sec, 98 bytes/sec

72455 Transmission average whilst connected so far: 0 frames/sec, 25 bytes/sec

72455 Max receive buffer = 807, Max send depth = 2, Send frames lost = 0

72455 ***********************************************

72555 Received shutdown offset code = ADBC

76480 ****** End of session performance summary ******

76480 Total time connected = 68 seconds

76480 Reception maximum: 10 frames/sec, 1642 bytes/sec

76480 Reception average whilst connected: 8 frames/sec, 961 bytes/sec

76480 Transmission maximum: 1 frames/sec, 98 bytes/sec

76480 Transmission average whilst connected: 0 frames/sec, 25 bytes/sec

76480 Max receive buffer = 807, Max send depth = 2, Send frames lost = 0

76480 ********* Log file closed (Buffers: MaxUsed 2, Alloc 628 Freed 628 Refused 0) *********

[Pete Dowson]

I'm working with VISTA on the server side and XP on the client side!

The WideFS version is 6.75 (on both server and client!)

I made the changes to the ini-files, but even then it doesn't work.

In that case it sounds like the two PCs are not in the same Workgroup. You should put them in the same workgroup, then connection is less hassle and can be automatic. The Server broadcasting doesn't work across different workgroups.

I'm not sure where you change it in Vista, but in XP right-click "My Computer", select Properties then Computer Name. You'll see the Workgroup name, which can be changed by pressing the "Change" button. You'll probably have to re-boot.

Here you have the log files:

Okay. I see. One or both of the keys you are using is invalid. It is either pirated, or it has expired, or it was issued AFTER the current date set in your Server PC. The last is plainly not the case because WideServer reports:

Date (dmy): 28/10/07, Time 12:22:00.063: Server name is SERVER

Everything else is fine. WideFS is working, but FSUIPC is refusing to cooperate with any applications because it believes it is being used with invalid keys.

If you think your keys are valid, please ZIP the Key file, along with any prof of purchase you can find, and send them to me at petedowson@btconnect.com.

Regards

Pete

[atrailblazer7]

I'm having the same problem. I'm trying to get FS Commander9 and VAFS to work w/Wide FS Client on laptop, which has Vista on it.

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

Date (dmy): 10/02/11, Time 09:55:48.401: Client name is TRACIEANDALE-PC

265 Attempting to connect now

811 Server = FLIGHT-7245DFB2

842 Trying TCP/IP host "FLIGHT-7245DFB2" port 8002 ...

842 ... Okay, IP Address = 192.168.254.

842 Connection made okay!

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

Date (dmy): 10/02/11, Time 09:23:09.653: Client name is TRACIEANDALE-PC

327 Attempting to connect now

811 Server = FLIGHT-7245DFB2

842 Trying TCP/IP host "FLIGHT-7245DFB2" port 8002 ...

842 ... Okay, IP Address = 192.168.254.106

842 Connection made okay!

1911028 ****** End of session performance summary ******

1911028 Total time connected = 1908 seconds

1911028 Reception maximum: 1 frames/sec, 122 bytes/sec

1911028 Reception average whilst connected: 1 frames/sec, 41 bytes/sec

1911028 Transmission maximum: 0 frames/sec, 21 bytes/sec

1911028 Transmission average whilst connected: 0 frames/sec, 19 bytes/sec

1911028 Max receive buffer = 403, Max send depth = 1, Send frames lost = 0

1911028 ********* Log file closed (Buffers: MaxUsed 2, Alloc 3386 Freed 3386 Refused 0) *********

; =====================================================

[Config]

Port=8002

Window=8,8,1280,786

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

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

This info is from the laptop running WideFS

On my PC that has Flight Sim 9 on it, it has XP Professional, Wide Server on it.

Both computers show connected (Wide Server shows 1 connected, Wide FS shows connected)...FS Commander and VAFS isn't detecting Flight Sim 9

The computers are showing in the same network group

Both have FSUPIC (regiestered). Both have version 3.984.

I have dropped the firewalls on both to get the info to go between them, no luck. Computers still show connected, but VAFS and FS Commander9 not connecting to Flight sim

I am not a computer pro, I drive a truck for a living. So please be patience as I try to understand

Thank you for your help

[atrailblazer7]

Figured out what the problem was......have to run as admin. Thought since I was signed on as admin on whole computer, it would work. But when requesting a program to run, had to right click, select run as admin, and it all works

[Pete Dowson]

Figured out what the problem was......have to run as admin. Thought since I was signed on as admin on whole computer, it would work. But when requesting a program to run, had to right click, select run as admin, and it all works

You most certainly should not have to run anything "as admin". That gives the program "elevated administrator" privileges, which are the those which only installers need.

If you run any part of your setup "as admin" you have to run all of the programs which need to talk to each other "as admin", because windows prevents programs of different privilege levels talking to each other.

However, there should be no reason you have to run any of it like that.

BTW it is not a good idea to append a new message to a 3.5 year old thread which ended with the diagnosis that the person was using an illegal (pirated) key, and saying you have the same problem! :blink:

Regards

Pete