Jump to content
The simFlight Network Forums

Address family not supported by protocol family


Recommended Posts

Good day Peter

WideFS was working fine then after a few days away I get no connection:

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 09/06/10, Time 10:40:54.109: Server name is SERVER

100546 Initialising TCP/IP server

100562 Initialising IPX/SPX server

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

100562 Failed to start IPX/SPX Server

100562 Initialising UDP/IP server

102078 Broadcasting service every 1000 mSecs

111625 Restarting service due to total lack of use

111625 Failed to start IPX/SPX Server

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

Date (dmy): 09/06/10, Time 10:43:02.468: Client name is LAPTOP

266 Attempting to connect now

1266 Trying to locate server: Need details from Server Broadcast

1266 Failed to connect: waiting to try again

3313 Attempting to connect now

3469 Server = SERVER

3516 Trying TCP/IP host "SERVER" port 8002 ...

3516Okay, IP Address = 192.168.1.100

20563 ****** End of session performance summary ******

20563 Total time connected = 0 seconds

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

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

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

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

I have not knowingly made any changes to my settings on either pc.

Thank you

Nicholas

Link to comment
Share on other sites

WideFS was working fine then after a few days away I get no connection

You've changed something then.

Why is your heading "Address family not supported by protocol family"? You aren't using the IPX protocol are you? In current Microsoft operating systems that protocol is optional. You'd need to explicitly install it if you wanted to use it.

The Server and Client logs show everything is normal, though you are using an out of date WideClient. There are no errors, but you only ran the Server for 10 seconds and didn't terminate FS before showing the log, so there's innformation missing, and you only ran WideClient for 20 seconds before terminating it. Possibly they weren't actually running at the same time, or long enough to establish themselves? 10 seconds for FS seems woefully short to do anything and terminating the Client after just 20 seconds seems to show a slight lack of patience?

Please update to a supported version of the Client.

I have not knowingly made any changes to my settings on either pc.

And there's no errors indicated, yet.

Pete

Link to comment
Share on other sites

The reason for the short runtime is that this was the third time I had not gained a connection and I ran it in order to produce the logs - nothing else - so yes, I was impatient and jolly cross.

"Why is your heading "Address family not supported by protocol family"? You aren't using the IPX protocol are you? In current Microsoft operating systems that protocol is optional. You'd need to explicitly install it if you wanted to use it."

I have no idea "why". I recently had an OS reinstall by a qualified tech so perhaps he put it there unbeknownst to me. Is it wrong, or just unnecessary?

That being said I have had WideFS running correctly since that OS reinstall.

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 09/06/10, Time 15:38:27.625: Server name is SERVER

114500 Initialising TCP/IP server

114500 Initialising IPX/SPX server

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

114500 Failed to start IPX/SPX Server

114500 Initialising UDP/IP server

116031 Broadcasting service every 1000 mSecs

125656 Restarting service due to total lack of use

125656 Failed to start IPX/SPX Server

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

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

Date (dmy): 09/06/10, Time 15:42:08.375: Client name is LAPTOP

234 Attempting to connect now

1140 Server = SERVER

1187 Trying TCP/IP host "SERVER" port 8002 ...

1187Okay, IP Address = 192.168.1.100

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

22140 Ready to try connection again

24156 Attempting to connect now

24156 Giving up server, looking for another!

25140 Server = SERVER

25140 Trying TCP/IP host "SERVER" port 8002 ...

25140Okay, IP Address = 192.168.1.100

48140 Server = SERVER

48140 Trying TCP/IP host "SERVER" port 8002 ...

48140Okay, IP Address = 192.168.1.100

71031 Giving up server, looking for another!

71156 Server = SERVER

71156 Trying TCP/IP host "SERVER" port 8002 ...

71156Okay, IP Address = 192.168.1.100

95187 Trying to locate server: Need details from Server Broadcast

96078 ****** End of session performance summary ******

96078 Total time connected = 0 seconds

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

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

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

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

Link to comment
Share on other sites

"Why is your heading "Address family not supported by protocol family"? You aren't using the IPX protocol are you? In current Microsoft operating systems that protocol is optional. You'd need to explicitly install it if you wanted to use it."

I have no idea "why". I recently had an OS reinstall by a qualified tech so perhaps he put it there unbeknownst to me. Is it wrong, or just unnecessary?

Sorry, I think you have become mixed up? Surely your qualified tech did not insert the title into your message here?

My point was only that you entitled this thread with a passing comment from the log which was only pointing out that WideServer could not support IPC/SPX because it isn't installed. If you are not intending to use IPX/SPX, that does not matter. This is why I asked why you used it as your title?

116031 Broadcasting service every 1000 mSecs

125656 Restarting service due to total lack of use

125656 Failed to start IPX/SPX Server

281734 Closing down now ...

Okay, now you left WideServer running for over two minutes and no connection seen.

1187 Trying TCP/IP host "SERVER" port 8002 ...

1187Okay, IP Address = 192.168.1.100

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

And this time you ran long enough for WideClient to report an error.

It appears that your Server is not seeing the client and the client cannot get through to the Server. Assuming it is getting the IP address correctly (192.168.1.100 looks normal), there is either no true network connection to the Server or, probably more likely, you have a firewall stopping it -- either stopping WideClient sending out to the Server, or the Server stopping incoming connections.

There's really nothing else I can tell from here. You need to allow your two PCs to talk freely, or at least make exceptions for FS and WideClient.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.