bumblebee Posted January 25, 2008 Report Share Posted January 25, 2008 Hi. I have been using WideFS for a couple of months without any problems at all, until today. For some reason the Flight simulator top line just displays "waiting for clients" and the client PC shows "waiting for a connection." WideServer and WideClient don't seem able to see each other. I have changed absolutely nothing between yesterday and today. The two PC's seem to be able to see each other over the network, and can share files etc. I have tried disabling firewalls and antivirus on both with no effect. I have tried deleting and re-installing WideFS from a fresh download, but it made no difference. Any help would be greatly appreciated. Server PC FS9.1 FSUIPC 3.75 Windows XP MCE with all current updates Client PC Windows XP Home with all current updates ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 25/01/08, Time 19:18:54.120: Client name is HOMEPC 1192 Attempting to connect now 1352 Server = 127019600301 1462 Trying TCP/IP host "127019600301" port 8002 ... 1462Okay, IP Address = 212.68.205.86 2654 Error on client pre-Connection Select() [Error=10061] Connection refused 2664 Ready to try connection again 4677 Attempting to connect now 5358 Server = 127019600301 5358 Trying TCP/IP host "127019600301" port 8002 ... 5358Okay, IP Address = 212.68.205.86 9353 Server = 127019600301 9353 Trying TCP/IP host "127019600301" port 8002 ... 9353Okay, IP Address = 212.68.205.86 12608 Giving up server, looking for another! 13359 Server = 127019600301 13359 Trying TCP/IP host "127019600301" port 8002 ... 13359Okay, IP Address = 212.68.205.86 17355 Server = 127019600301 17365 Trying TCP/IP host "127019600301" port 8002 ... 17365Okay, IP Address = 212.68.205.86 21361 Server = 127019600301 21361 Trying TCP/IP host "127019600301" port 8002 ... 21361Okay, IP Address = 212.68.205.86 25366 Server = 127019600301 25366 Trying TCP/IP host "127019600301" port 8002 ... 25366Okay, IP Address = 212.68.205.86 28561 Giving up server, looking for another! 29362 Server = 127019600301 29362 Trying TCP/IP host "127019600301" port 8002 ... 29362Okay, IP Address = 212.68.205.86 33368 Server = 127019600301 33368 Trying TCP/IP host "127019600301" port 8002 ... 33368Okay, IP Address = 212.68.205.86 37374 Server = 127019600301 37374 Trying TCP/IP host "127019600301" port 8002 ... 37374Okay, IP Address = 212.68.205.86 41370 Server = 127019600301 41370 Trying TCP/IP host "127019600301" port 8002 ... 41370Okay, IP Address = 212.68.205.86 44684 Giving up server, looking for another! 45375 Server = 127019600301 45375 Trying TCP/IP host "127019600301" port 8002 ... 45375Okay, IP Address = 212.68.205.86 51374 Server = 127019600301 51374 Trying TCP/IP host "127019600301" port 8002 ... 51374Okay, IP Address = 212.68.205.86 60377 Server = 127019600301 60377 Trying TCP/IP host "127019600301" port 8002 ... 60377Okay, IP Address = 212.68.205.86 63712 Giving up server, looking for another! 64383 Server = 127019600301 64383 Trying TCP/IP host "127019600301" port 8002 ... 64383Okay, IP Address = 212.68.205.86 68378 Server = 127019600301 68378 Trying TCP/IP host "127019600301" port 8002 ... 68378Okay, IP Address = 212.68.205.86 72384 Server = 127019600301 72384 Trying TCP/IP host "127019600301" port 8002 ... 72384Okay, IP Address = 212.68.205.86 76380 Server = 127019600301 76390 Trying TCP/IP host "127019600301" port 8002 ... 76390Okay, IP Address = 212.68.205.86 79614 Giving up server, looking for another! 80386 Server = 127019600301 80386 Trying TCP/IP host "127019600301" port 8002 ... 80386Okay, IP Address = 212.68.205.86 81577 New Client Application: "rcv4" (Id=4044) 84391 Server = 127019600301 84391 Trying TCP/IP host "127019600301" port 8002 ... 84391Okay, IP Address = 212.68.205.86 88387 Server = 127019600301 88397 Trying TCP/IP host "127019600301" port 8002 ... 88397Okay, IP Address = 212.68.205.86 92393 Server = 127019600301 92393 Trying TCP/IP host "127019600301" port 8002 ... 92393Okay, IP Address = 212.68.205.86 93384 ****** End of session performance summary ****** 93384 Total time connected = 0 seconds 93384 Reception maximum: 0 frames/sec, 0 bytes/sec 93384 Transmission maximum: 0 frames/sec, 0 bytes/sec 93384 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 93384 **************** Individual client application activity **************** 93384 Client 4044 requests: 5 (Ave 5/sec), Data: 214 bytes (214/sec), Average 42 bytes/Process 93384 ********* Log file closed (Buffers: MaxUsed 1, Alloc 5 Freed 5 Refused 0) ********* Wideclient0 log ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 25/01/08, Time 19:11:40.572: Client name is HOMEPC 671 Attempting to connect now 1092 Server = 127019600301 1102 Trying TCP/IP host "127019600301" port 8002 ... 1102Okay, IP Address = 212.68.205.86 2383 Error on client pre-Connection Select() [Error=10061] Connection refused 2393 Ready to try connection again 4396 Attempting to connect now 5097 Server = 127019600301 5097 Trying TCP/IP host "127019600301" port 8002 ... 5097Okay, IP Address = 212.68.205.86 6730 ****** End of session performance summary ****** 6730 Total time connected = 0 seconds 6730 Reception maximum: 0 frames/sec, 0 bytes/sec 6750 Transmission maximum: 0 frames/sec, 0 bytes/sec 6750 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 6750 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* WideServer log ********* WideServer.DLL Log [version 6.75] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 25/01/08, Time 19:06:08.562: Server name is 127019600301 237219 Initialising TCP/IP server 237250 Initialising IPX/SPX server 237250 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 237250 Failed to start IPX/SPX Server 237250 Initialising UDP/IP server 238484 Broadcasting service every 1000 mSecs 248406 Restarting service due to total lack of use 248437 Failed to start IPX/SPX Server 1045844 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): 25/01/08, Time 18:11:33.671: Server name is 127019600301 400328 Initialising TCP/IP server 400344 Initialising IPX/SPX server 400344 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 400344 Failed to start IPX/SPX Server 400344 Initialising UDP/IP server 400344 Broadcasting service every 1000 mSecs 413313 Restarting service due to total lack of use 413344 Failed to start IPX/SPX Server 1926000 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 ********* Thank in advance Philip Dawson Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 25, 2008 Report Share Posted January 25, 2008 For some reason the Flight simulator top line just displays "waiting for clients" and the client PC shows "waiting for a connection." WideServer and WideClient don't seem able to see each other. Windows is blocking the access. That's what "connection refused" means. WideClient is simply relaying the error it is being told by Windows. I have tried disabling firewalls and antivirus on both with no effect. Well, I'm pretty sure the answer lies in that direction (firewalls, that is). I have tried deleting and re-installing WideFS from a fresh download, but it made no difference. Well, it won't do -- replacing a program with an identical copy of the same program changes nothing. Sorry, you need to find what is preventing access. It could be something stopping Wideclient seeing out or the Server receiving the connection, so double check firewalls both ends. Not anti-virus programs, they aren't relevant. Regards Pete Link to comment Share on other sites More sharing options...
bumblebee Posted January 26, 2008 Author Report Share Posted January 26, 2008 Thanks for yor reply, Pete. One thing I noticed was the IP address that keeps getting mentioned in my log files - 212.68.205.86 (I have also seen a slightly different version at other times - 212.68.205.66). Both of my PC's have addresses assigned by the router starting 192.168.X.X. I wondered if it might be possible for WideServer to be sending out the wrong address, or if windows might be giving it the wrong address? Or am I barking up the wrong tree with this? I have also tried connecting after completely uninstalling the firewalls on both machines, and ensuring that windows firewall is off, but to no avail. I know it is not up to you to solve network issues, but if you are able to shed any light on this I would be most grateful. Thanks, Philip. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 26, 2008 Report Share Posted January 26, 2008 One thing I noticed was the IP address that keeps getting mentioned in my log files - 212.68.205.86 (I have also seen a slightly different version at other times - 212.68.205.66). Both of my PC's have addresses assigned by the router starting 192.168.X.X. I wondered if it might be possible for WideServer to be sending out the wrong address, or if windows might be giving it the wrong address? Or am I barking up the wrong tree with this? No, obviously it is getting the wrong address. I have seen such a thing before, someplace, but I can't remember what the cause was. Something to do with Network card drivers I think. You are providing the Server name, I see. (A rather complicated one too, "127019600301"). All WideClient does with that is ask Windows to convert it to an IP address. That's the one you are then seeing it try. Windows should of course provide the correct IP address. Are you using WinXP or later on both PCs? If so you could simply allow WideFS to connect automatically. Do this by removing both the ServerName and Protocol parameters from the WideClient.INI file. The default installation as supplied from the WideFS downloads should work this way in any case. If you aren't using WinXP or later on both, then just try specifying the correct IP address yourself, as "ServerIPAddr=n.n.n.n", and remove the ServerName. For this, though, you will really need to set fixed IP addresses for each PC, not allow the router to set them, as they may not be the same each time if you do. Fixed addresses tend to be more efficient in any case (I've always used them), as it saves extra traffic, asking the name server (your router) for a translation each time something wants to start a fresh transaction. Regards Pete Link to comment Share on other sites More sharing options...
bumblebee Posted January 29, 2008 Author Report Share Posted January 29, 2008 I hope I'm not speaking too soon, but... success! I am not sure what made the difference, but I tried various combinations of the things you suggested, even the ones that should not apply to XP. I also re-loaded my ethernet connection driver (on both) in case this was corrupt in some way, after what you said about network card drivers. The FS9 PC runs Media Centre and the WideClient PC runs XP Home. At first I had limited success - it would only connect about half the time and took about six seconds to do so when it did connect. But I also fiddled about a bit with the router. Again, I'm sure I put everything back to the same settings as before, but I also used saved backup settings from months ago. The IP addresses are assigned by the router when each PC is added for the first time, but then remain static indefinitely after that, even after the router and PCs are disconnected and the power is off. Somehow through all of it, it started working properly again. Connection is now consistent and virtually instantaneous. I have the feeling that the router was at the centre of the problem, so I might spend a few quid on a new one soon. I have also been told that less-than-perfect cables can interfere with network connections in unexpected ways, so they might need replacing. But all’s well and good for the time being! Thanks for your help! Philip. Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 29, 2008 Report Share Posted January 29, 2008 Connection is now consistent and virtually instantaneous. I have the feeling that the router was at the centre of the problem, so I might spend a few quid on a new one soon. I have also been told that less-than-perfect cables can interfere with network connections in unexpected ways, so they might need replacing. But all’s well and good for the time being! Good! Thanks for letting us know! Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now