WideFS - Keeps waiting for a connection

[Egbert Drenth]

Hi,

I'm a long time user of WideFS but now I encounter a problem.

Recently I reinstalled my FS2004 PC, migrating from WinXP x32 to Win7 X64.

In the past I have reinstalled several times my OS/FS2004 and all I had to do was to change the IP address in the Wideclient.ini

Somehow now I encounter a problem, causing WideFS not to connect to FSUIPC anymore.

I don't have a clue why...

WideClient PC: Win7 X64, Fixed IP: 192.168.1.79

FS2004 PC: Win7 X64, Fixed IP: 192.168.1.76

On both systems the Windows firewall is turned off.

I can ping on both systems to the other PC, they find each other.

If I recall correctly in the FS2004 title bar there should be a message 'Waiting for Clients' (or something)

In my current FS2004 this line is not showing.

Please advice

Here my Wideclient.ini

[Config]

Port=8002

Window=32000,32000,160,38

Visible=Min

ServerName=192.168.1.76

Protocol=TCP

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

Wideclient.log

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

Date (dmy): 16/09/10, Time 13:45:52.415: Client name is I7-MAIN

250 Attempting to connect now

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

250Okay, IP Address = 192.168.1.76

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

1295 Ready to try connection again

2324 Attempting to connect now

5132 New Client Application: "ASv6" (Id=4840)

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

61823Okay, IP Address = 192.168.1.76

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

123381Okay, IP Address = 192.168.1.76

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

184924Okay, IP Address = 192.168.1.76

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

246638Okay, IP Address = 192.168.1.76

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

308289Okay, IP Address = 192.168.1.76

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

369847Okay, IP Address = 192.168.1.76

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

431499Okay, IP Address = 192.168.1.76

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

493197Okay, IP Address = 192.168.1.76

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

554755Okay, IP Address = 192.168.1.76

FSUIPC.log

********* FSUIPC, Version 3.98a by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\FS2004\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Egbert Drenth"

User Addr="egbert.drenth@not-relevant.nl"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

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

WeatherOptions(Orig)=6000B78F[6000B78F]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

1919 System time = 16/09/2010 13:44:07

1919 \\TROSA\C\FS2004\

1919 System time = 16/09/2010 13:44:07, FS2004 time = 12:00:00 (00:00Z)

3791 \\TROSA\C\Users\DRE\Documents\Flight Simulator Files\ESSA_Gate10_C172.flt

3806 AIRCRAFT\c172\Cessna172SP.air

3806 Aircraft="Cessna Skyhawk 172SP"

7098 Advanced Weather Interface Enabled

9703 \\TROSA\C\Users\DRE\Documents\Flight Simulator Files\UI generated flight.flt

9875 Clear All Weather requested: external weather discarded

[Pete Dowson]

In the past I have reinstalled several times my OS/FS2004 and all I had to do was to change the IP address in the Wideclient.ini

You shouldn't even need to do that provided both PCs are in the same WorkGroup. For many years now the Server has sent out identification messages so that the Client can find it automatically.

If I recall correctly in the FS2004 title bar there should be a message 'Waiting for Clients' (or something)

In my current FS2004 this line is not showing.

If it is not showing, then WideServer is not running. Did you remember to put WideServer.DLL into the FS Modules folder?

It seems significant that you show the Client log and the FSUIPC log, but no WideServer log!?

Regards

Pete

[Egbert Drenth]

Did you remember to put WideServer.DLL into the FS Modules folder?

Pete

Wideserver.dll ?? What Wideserver.dll? :D

Indeed I had forgotten to install it, all is OK now.

Thanks for your prompt reply Pete.