Problems with WideFS Server Part

[mvwissen]

Hi Pete,

Hopefully, you can help me with some problems I am facing with WideFS. Unfortunately, I had to reinstall FS9 because of Vista SP1. Performance went down the drain and I clearly identified SP1 as the cause. Now, after reinstalling my entire PC (without SP1), I am facing problems with WideFS. I worked before :?. OK, here is what happens. When I start FS (created a new flight), I get the following message once FS is running for a few seconds: Server bind() failed [Error=10022] Invalid argument. The logs show the following errors:

WiderServer.log

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 05/04/08, Time 22:03:40.269: Server name is FSBOX

28658 Initialising TCP/IP server

29453 Server listen() failed all attempts [Error=0]

29469 Failed to start TCP/IP Server

29469 Initialising IPX/SPX server

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

29469 Failed to start IPX/SPX Server

29469 Initialising UDP/IP server

68297 Server bind() failed [Error=10022] Invalid argument

68297 Failed to start UDP/IP Server

68485 Broadcasting service every 1000 mSecs

77923 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 *********

WideServer0.log

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 05/04/08, Time 22:00:52.785: Server name is FSBOX

59156 Initialising TCP/IP server

59951 Server listen() failed all attempts [Error=0]

59951 Failed to start TCP/IP Server

59951 Initialising IPX/SPX server

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

59967 Failed to start IPX/SPX Server

59967 Initialising UDP/IP server

91822 Server bind() failed [Error=10022] Invalid argument

91822 Failed to start UDP/IP Server

92649 Broadcasting service every 1000 mSecs

145923 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 *********

The WideServer.ini reads the following:

[Config]

AdvertiseService=1

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port=8002

Port2=9002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

Protocol=TCP

ServerIPAddr=192.168.1.11

Any ideas what the problem could be? I really appreciate any help, because this issue starts to drive me bunkers.

Best regards,

Mark

[Pete Dowson]

I get the following message once FS is running for a few seconds: Server bind() failed [Error=10022] Invalid argument.

Actually, that isn't the problem. That's only the UDP server failing to start:

68297 Server bind() failed [Error=10022] Invalid argument

68297 Failed to start UDP/IP Server

Since you are probably using TCP that wouldn't stop it working. What does stop it is this:

29453 Server listen() failed all attempts [Error=0]

29469 Failed to start TCP/IP Server

Now I've never seen either of these errors ever before. WideServer is merely relaying the errors it is getting from Windows. It loooks like you have no network working, possibly no active network adapter, etc. Best to try to get your network really working properly then try again.

Incidentally, why are you putting these parameters into the Server's INI file?

Protocol=TCP

ServerIPAddr=192.168.1.11

The server supports any of the three protocols, the choice is made by the Client. And why would the Server need to be given its own IP address? Are you reading the documentation and making your own mind up about what to do?

If you've been messing with the INI files, best to delete them and let them default again.

Regards

Pete

[mvwissen]

Hi Pete,

Thanks for the ultra quick response. I didn't expect that. Well, I actually read the documentation regarding the ini file. I was just hoping that it might help. BTW. The IP address is the IP address of the client PC. So, basically, I tried it with a default ini as well. No luck. Regarding the proper network connection, I have to say that I can connect to the internet, I can connect to my NAS server and I can even ping my second PC running the WideFS client. So, I am still pretty clueless about what to do. Will do some more research.

Regards,

Mark

[mvwissen]

Hey Pete,

After checking the Firewall, I found the wrong setting :oops:. Thanks for your help anyway. Greatly appreciate it.

Regards,

Mark

[Pete Dowson]

After checking the Firewall, I found the wrong setting

Ah. Glad it wasn't too hard. ;-)

Pete