Clients can't get data from the FS 2004.

[Elisio Cruz]

Hi !

I have three computers connected in a smae network. Each of them with a fixed IP. They are:

PC 1- FS 2004 ( with FSUIPC and wide FS, last version );

PC 2- Project Magenta Reginal Jet Panel (with WideClient last version);

PC 3- Project Magenta Instructor Station (with WideClient last version).

the FSUIPC and the Wide FS are registered and have always worked very well. Suddenly, the PCs clients stopped receiving data from the FS 2004. I have already updated the versions of the Wide FS, Wide client and FSUIPC but the problem remains. I checked the network and it is OK. In the FS 2004 there is the information that the client is connected. In the Wide FS of the clients there is also the information they are connected but in practice, the clients can't get data from the FS 2004.

As a test in the server, we ran FS Metar. The FS Metar can download the new Metar but it can't conect to the FS.

What do you advise ? What shall I do to the clients get the information from the server as happened before ?

Thanks,

Elisio Cruz

[Pete Dowson]

PC 1- FS 2004 ( with FSUIPC and wide FS, last version );

PC 2- Project Magenta Reginal Jet Panel (with WideClient last version);

PC 3- Project Magenta Instructor Station (with WideClient last version).

I really do always need VERSION NUMBERS. The term "last version" is meaningless. I've had folks saying they're using the "latest" version and it turned out to be a year old, but was the "latest version they'd seen". It isn't hard to find the version numbers -- they are displayed in the options, in the logs, in the documentation and even in the File Properties Version tab!

the FSUIPC and the Wide FS are registered and have always worked very well. Suddenly, the PCs clients stopped receiving data from the FS 2004.

Unchanged, and with no other changes, software doesn't suddenly stop working or change its behaviour. You need to try to think what you changed then. Something you changed did it -- or else a hardware fault has developed.

In the Wide FS of the clients there is also the information they are connected but in practice, the clients can't get data from the FS 2004.

Show me the WideClient, WideServer and FSUIPC Log files. Make sure everything is closed down first, though.

Regards

Pete

[Elisio Cruz]

Thanks, Pete !

The only one new software installed was NERO 8.

Please see attached the LOGS.

Thanks,

Elisio

********* FSUIPC, Version 3.90 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "C:\Arquivos de programas\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

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

User Name="Elisio Cruz"

User Addr="elisio.cruz@uol.com.br"

FSUIPC Key is provided

WideFS Key is provided

Module base=61000000

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

WeatherOptions(Orig)=40153625[40153625]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=255

7984 System time = 00:38:14

7984 \\FS\C\Arquivos de programas\Microsoft Games\Flight Simulator 9\

7984 System time = 00:38:14, FS2004 time = 12:00:00 (00:00Z)

24766 \\FS\C\DOCUME~1\MICROXP\MEUSDO~1\FLIGHT~1\LEARJE~1.flt

24969 AIRCRAFT\lear45XR\Lear45.air

24969 Aircraft="8"

100016 Advanced Weather Interface Enabled

110859 System time = 00:39:57, FS2004 time = 12:30:33 (14:30Z)

110859 *** FSUIPC log file being closed

Memory managed: 0 Allocs, 40 Freed

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

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

Date (dmy): 12/05/09, Time 14:27:19.836: Client name is MICRO-XP

671 C:\WideFS

671 c:/pmrj3/piloto.exe

671 C:\WideFS

671 c:/pmrj/eicas.exe

671 C:\WideFS

671 c:/pmrj2/copiloto.exe

671 C:\WideFS

671 c:/PMSounds/pmSounds.exe

751 Attempting to connect now

1242 New Client Application: "GFRemote" (Id=1520)

1973 New Client Application: "FS2Phidget" (Id=1776)

3074 Trying TCP/IP host "fs" port 80 ...

3074 Error on client gethostbyname() [Error=11001] Host not found

9383 New Client Application: "MCLink" (Id=1732)

10155 New Client Application: "pmSounds" (Id=1844)

12798 New Client Application: "Copiloto" (Id=1836)

13790 New Client Application: "Piloto" (Id=1820)

15182 New Client Application: "EICAS" (Id=1828)

65444 Trying TCP/IP host "fs" port 80 ...

65444 Error on client gethostbyname() [Error=11001] Host not found

127974 Trying TCP/IP host "fs" port 80 ...

127974 Error on client gethostbyname() [Error=11001] Host not found

190163 Trying TCP/IP host "fs" port 80 ...

190163 Error on client gethostbyname() [Error=11001] Host not found

202551 ****** End of session performance summary ******

202551 Total time connected = 0 seconds

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

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

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

202551 **************** Individual client application activity ****************

202551 Client 1520 requests: 392 (Ave 392/sec), Data: 22321 bytes (22321/sec), Average 56 bytes/Process

202551 Client 1776 requests: 781 (Ave 781/sec), Data: 42174 bytes (42174/sec), Average 54 bytes/Process

202551 Client 1732 requests: 479 (Ave 479/sec), Data: 238307 bytes (238307/sec), Average 497 bytes/Process

202551 Client 1844 requests: 238 (Ave 238/sec), Data: 254422 bytes (254422/sec), Average 1069 bytes/Process

202551 Client 1836 requests: 1043 (Ave 1043/sec), Data: 2696093 bytes (2696093/sec), Average 2584 bytes/Process

202551 Client 1820 requests: 787 (Ave 787/sec), Data: 1867859 bytes (1867859/sec), Average 2373 bytes/Process

202551 Client 1828 requests: 814 (Ave 814/sec), Data: 1980307 bytes (1980307/sec), Average 2432 bytes/Process

202551 ********* Log file closed (Buffers: MaxUsed 1, Alloc 4531 Freed 4531 Refused 0) *********

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 01/01/02, Time 00:38:15.625: Server name is FS

90672 Initialising TCP/IP server

90687 Initialising IPX/SPX server

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

90687 Failed to start IPX/SPX Server

90687 Initialising UDP/IP server

92062 Broadcasting service every 1000 mSecs

104656 Closing down now ...

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

[Pete Dowson]

Please see attached the LOGS.

Okay. The main problem is that either your FSUIPC or your WideFS key is invalid. Was one or the other a time-limited one for evaluation? Project Magenta customers are often afforded that luxury, one which I don't subscribe to.

Otherwise, there are only two possibilities: either one or both of the keys are invalid by reason of being generated by an illegal pirate key generator, or the date on your FS PC is incorrect, making it look as if one or both keys were issued later than today's date (according to Windows). This latter can happen if the little battery maintaining your PC's CMOS memory settings has expired.

There's a further problem in that the name of your server PC. "fs" is not being resolved on your client PC:

3074 Trying TCP/IP host "fs" port 80 ...

3074 Error on client gethostbyname() [Error=11001] Host not found

What concerns me here is that mention of Port 80. Why have you set WideFS to use port 80? The default is port 8002 -- port 80 is normally reserved for regular internet or email activities as far as I'm aware. The default of 8002 was chosen deliberately well away from any default ports.

The fact that WideClient is searching for a specific server by name is a little odd too. By default, as supplied, WideFS should be self-configuring. You only need to mess about with servername parameters and the like if you are using mixed systems (win98/NT/2000 with XP/Vista) or you have your PCs in different workgroups (unusual and not recommended).

[LATER]

I just noticed! The WideServer log shows the date as "01/01/02". That's your first and main problem, I think!

I'll need to start logging the PC's system date in the FSUIPC log I think. There have been several cases like this -- usually folks with a new PC which they've not bothered to set up correctly yet!

Regards

Pete

[Elisio Cruz]

Pete, you were right. The date of the server was wrong. I only had to correct it and everything worked normally again. It's incredible that something of such little importance in appearance can have caused so many problems.

Thanks,

Elisio