FSUIPC waiting for client

[Ropipo]

Peter,

I have once in a while a problem connecting FSUIPC and WideFS. (more less than often)

FSX PC in Windows 7 64 bits, the client in Vista 32 bits.

FSUIPC version 4.60a; WideFS 6.78

The FS saying waiting for client. The client WideFS saying WideClient FS98 Eliminator - Waiting for a connection.

No dialog between them. FScommander failes when turning on GPS.

On the other had ActiveSky ASE has the connection: so Simconnect is O.K.

What troubles me is the title WideClient FS98 !

Do you have an idea what I should do ?

Roger

[Ropipo]

Peter,

I am posting the two log files.

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

Date (dmy): 26/06/10, Time 12:20:43.802: Client name is ROGER-POTIE-NB

468 Attempting to connect now

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

500Okay, IP Address = 192.168.0.2

21497 Error on client pre-Connection Select() [Error=10060] Connection timed out

21497 Ready to try connection again

22527 Attempting to connect now

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

66582Okay, IP Address = 192.168.0.2

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

132710Okay, IP Address = 192.168.0.2

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

198808Okay, IP Address = 192.168.0.2

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

264953Okay, IP Address = 192.168.0.2

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

331019Okay, IP Address = 192.168.0.2

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

397179Okay, IP Address = 192.168.0.2

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

463277Okay, IP Address = 192.168.0.2

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

529405Okay, IP Address = 192.168.0.2

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

595565Okay, IP Address = 192.168.0.2

646999 ****** End of session performance summary ******

646999 Total time connected = 0 seconds

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

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

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

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

and

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 26/06/10, Time 12:20:56.038: Server name is ROGERP

15257 Initialising TCP/IP server

15257 Initialising IPX/SPX server

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

15257 Failed to start IPX/SPX Server

15257 Initialising UDP/IP server

16130 Broadcasting service every 1000 mSecs

635127 Closing down now ...

Memory managed: Offset records: 470 alloc, 468 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 *********

I checked the IP address: O.K. Both PC are in same workgroup (I can read shared files between them).

Roger

[Ropipo]

Peter,

Now the ini files:

FSUIPC.INI

PressureSmoothness=0

TemperatureSmoothness=0

DisconnTrimForAP=No

ZeroElevForAPAlt=No

ThrottleSyncAll=No

WhiteMessages=Yes

ShowPMcontrols=No

SpoilerIncrement=512

MagicBattery=No

RudderSpikeRemoval=No

ElevatorSpikeRemoval=No

AileronSpikeRemoval=No

ReversedElevatorTrim=No

ClockSync=No

ClockSyncMins=5

ClearWeatherDynamics=No

OwnWeatherChanges=No

TimeForSelect=4

LoadFlightMenu=No

LoadPlanMenu=No

PauseAfterCrash=Yes

BrakeReleaseThreshold=75

SaveDataWithFlights=No

ZapSound=firework

ShortAircraftNameOk=No

UseProfiles=No

LogWrites=Yes

LogReads=Yes

LogLua=Yes

[JoyNames]

AutoAssignLetters=No

0=CH PRO PEDALS USB

0.GUID={98CDD9C0-46FA-11DF-8006-444553540000}

1=CH FLIGHT SIM YOKE USB

1.GUID={98CDD9C0-46FA-11DF-8007-444553540000}

[WideServer]

WideFSenabled=Yes

AdvertiseService=1

Port=8002

Port2=9002

[buttons]

ButtonRepeat=20,10

[AutoSave]

AutoSaveEnabled=Yes

Interval=750

Files=10

SaveOnGround=Yes

Next=7

1=Sat 160845

2=Sun 120256

3=Sun 121525

4=Sun 122755

5=Sun 124024

6=Thu 103230

7=Thu 163707

8=Thu 185149

9=Sat 133030

10=Sat 155615

[GPSout]

GPSoutEnabled=No

Port=COM1

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[GPSout2]

GPSoutEnabled=No

Port=

Speed=4800

Interval=2000

PosTo6Decimal=No

Sentences=

[ClientNames]

1=ROGER-POTIE-NB

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=Yes

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

LeftBrake=-7232,0

RightBrake=-7200,-32

------------------------------------------------------------------------------------------------------------------------------

WideFSClient.INI

; PLEASE SEE WideFS documentation for parameter details

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

[Config]

Port=8002

Window=-32000,-32000,160,25

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=RogerP

Protocol=TCP

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

[user]

Log=Errors+

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

[Andydigital]

Just in case you missed it Roger I thought I would bring it to your attention that Pete is away till July 5th as he announced at the top of the forum.

[Ropipo]

Andy,

Yes I missed that.

But I don't think Peter can really help me. Just his opinion is needed. Today FSUIPC and WideFS are communicating !!!!!.

It seems that the failures occur when it is warmer summer days. I still need to check that. Today my tests are conducted in the morning when it is still cool. I am suspecting the Ethernet is too sensible to heat. Then I also have some slow down going over the internet. As I said I need to check this with other warm days.

If this is the case I will need extra fans in the case or buy a dedicated Ethernet card instead of using the Mobo Ethernet. But Peter's opinion will be interresting.

[Ropipo]

Follow up:

I added an Ethernet card. This solved many communication problems. But not the WAITING FOR FSUIPC on the client PC.

Now what I may or may not have is that FSUIPC doesn't show any message, waiting for client or having a connection. And of course there is no communication with WideFS. I must then stop FSX AND the PC then restart the PC.

Roger

[Pete Dowson]

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

500Okay, IP Address = 192.168.0.2

This appears to indicate that you are providing the IP address (is it correct? The Servers never sees any attempts at all).

********* WideServer.DLL Log [version 7.60a] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 26/06/10, Time 12:20:56.038: Server name is ROGERP

That shows the server name to be "ROGERP".

You supplied what you called:

WideFSClient.INI

but if it is really called that, it isn't the WideClient.INI file being used, as you can see by the name.

If you really meant WideClient.INI then:

ServerName=RogerP

Protocol=TCP

this is okay, but should really result in the connection reading:

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

not the IP address, so something in the data you supply simply does not match correctly.

BTW why are you specifying the server details? Doesn't the broadcast work? It ceretainly should do if your PCs are in the same workgroup.

The other thing to check is your firewall, especially the one on the Server as that never sees anything from the client. It's rather odd, though, that nothing is reported back to the Client if Widows cannot connect.

Now what I may or may not have is that FSUIPC doesn't show any message, waiting for client or having a connection. And of course there is no communication with WideFS. I must then stop FSX AND the PC then restart the PC.

Sorry, you need to explain that a little clearer: "may or may not "? And why "stop FSX AND the PC then restart the PC."? What good is that?

Regards

Pete

[Ropipo]

Pete,

May or may not means that sometimes the warning that FSX waits for WideFS connection is posted above FSX screen and other times it does not mention any waiting (or if the client is on line).

But MAYBE I found the reason for this intermitent problem. Reviewing every parameter I realized that the server was connected to WORKGOUP and the client to FSNETWORK.

It took me some time to figure out how to correct this. Now it is O.K. I just need to wait and see it the connection is successful each time or again sometimes yes, sometimes no.

I do not have the time to check more in detail your message. I will examine it tomorrow morning.

I hope you had a good holiday !

More in the next few days.

Roger

[Pete Dowson]

May or may not means that sometimes the warning that FSX waits for WideFS connection is posted above FSX screen and other times it does not mention any waiting (or if the client is on line).

If there's nothing in the title bar from WideServer then it isn't running. It always posts an additive there once it is started -- but don't forget it only starts once FS is "ready to fly".

Pete

[Ropipo]

Pete,

I have fixed 95 % of the problem. I think it was a definition problem in the network groups.

But I still have one intermitent problem: WideFS for the server doens't start.

I use Windows 7 on the server. From time to time a random application will not respond to the W7. To overcome that problem I must reboot the server.

I think it is the same problem with WideFS for the server. When there is no message in the server bar I believe FSX/FSUIPC are waiting for WideFS. Maybe it is there but if there is no dialog to establish a connection between FSX and WideFS for server we can just wait for centuries. To overcome the problem I must reboot the server. Stoping and restarting FSX will not solve the problem.

Conclusion: this must be a W7 problem. Checking with Google I find several sites where people are complaining for the same problem with W7 but nobody has yet found an answer. The problem is annoying but as I get it sometimes far a part I can live with it. But I would be happy if somebody could help or point to me to the correct site where I can find help.

Roger

[Pete Dowson]

But I still have one intermitent problem: WideFS for the server doens't start.

How is this indicated? Is FSUIPC running? What is reported in the Logs? (FSUIPC and WideServer logs in the FS Modules folder)?

Conclusion: this must be a W7 problem.

Strange. I'm using Win7 on three PCs and have done since its Beta days in early 2009. I find it easily the best operating system Microsoft has ever built.

Could it simply be a boot-up problem, that the hardware drivers are somehow getting loaded in the wrong order, or there's some BIOS timing glitch during hardware initialisation? I'd check the BIOS settings and possibly investigate whether your motherboard has a BIOS update available. To my mind, given what you say about having to re-boot, this is a much more likely area for investigation.

Also, before re-booting you could try going to the Windows device manager and see what it says about your network adapter. Maybe it isn't listed, or is listed with a problem. A hardware re-scan there (on of the menu options) might even fix it without re-booting.

Please post again if you find out more.

Regards

Pete

[Ropipo]

Pete,

Thank you for your answer. For the moment I have no problem but I am also less flying the usual flights. I am following the Missions and therefore not needing the client PC. But I will check what you suggest and will report as soon I find something or have a log.

To answer you first question

>> Ropipo wrote:

But I still have one intermitent problem: WideFS for the server doens't start.>>

<

FSUIPC is active but no WideFS for the server starts. I will sent you a log as soon I get the problem again.

Roger

[Pete Dowson]

FSUIPC is active but no WideFS for the server starts.

Yes, as you said before, but I asked how you knew thiswhat is the indication that WideServer isn't starting?

Regards

Pete

[Ropipo]

Pete,

I assume it as no message appears above the menu bar of FSX when I am in window mode. No message saying it is waiting or is connected. On the client side the WideFS says it is waiting for a communication.

Roger

[Pete Dowson]

I assume it as no message appears above the menu bar of FSX when I am in window mode. No message saying it is waiting or is connected.

That appears quite late on, when "ready to fly", and there are other variations. The WideServer Log file is the true indication of whether it is running and it will show any problems.

Regards

Pete

[Ropipo]

Pete,

Since the last post I have no more problem. So for the time being I consider the problem solved. I think the source of the problem was the different definitions of the workgroup in both PCs.

If the problem comes back I will check as you suggested.

Roger