steveellis Posted December 4, 2004 Report Share Posted December 4, 2004 Hi everyone, I really do not know where to start on this one but here goes. I run 4 PCs running Wide Fs ( Peter - the test version on PM ) using TCPIP with each CPU with its own IP address I am running the PM CDU, GC on 1, GC on another 1 and on my admin cpu I am running Radar Contact, Activesky2004 and the BAV software. My network setup is Wireless using the Linksys WAG54G and occasionally this network is dropping out. I cannot pinpoint the frequency of these drop outs, sometimes I get no problems but this morning for example, it dropped out 5 times which was quite frustrating. Peter, are running the deafults on wideserver and client doing the job or can you tell me of any possible tweaks to any initializing log that may improve my situation. I have called linksys and they have given me the best possible settings for the ADSL Gateway/Router. Now it may be Active sky when it is updating and the amount of traffic that the network is passing through and it may be bottlenecking somewhere. Any help would be most grateful, even if a certain setting might do the trick. If you need any more info, please let me know. Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 4, 2004 Report Share Posted December 4, 2004 My network setup is Wireless using the Linksys WAG54G and occasionally this network is dropping out. I cannot pinpoint the frequency of these drop outs, sometimes I get no problems but this morning for example, it dropped out 5 times which was quite frustrating. What does "dropping out" actually mean? It is not exactly a tehnical term :wink: . Are there error messages on screen, do the WideClient and WideServer LOG files show anything? Peter, are running the deafults on wideserver and client doing the job or can you tell me of any possible tweaks to any initializing log that may improve my situation. No, not really. There are no "tweaks" to stop a Network "dropping out". But let me see the Server and Client log files. If they are large, ZIP them up and send them to me at petedowson@btconnect.com. I have called linksys and they have given me the best possible settings for the ADSL Gateway/Router. The router shouldn't have anything to do with it unless you are connecting to your clients via the Internet! :) . Is it acting as a Hub or a Switch, or do you have a separate Hub/Switch? Now it may be Active sky when it is updating and the amount of traffic that the network is passing through and it may be bottlenecking somewhere. What speed is the Network operating at? The router number (WAG54G) implies its a 54 Mbit G-level WiFi. Are all the individual receivers matching this? Certainly 54mbit should be enough, even for ActiveSky. And even if it is bottlenecking it should be transient, yet the term "dropping out" seems to imply a complete stop. I have USRobotics Wifi in 54mbit G-mode, but with all USR units it supports "turbo" mode which goes at 100mbit (same as my wired Network) -- or even more, apparently, if I apply firmware updates (to 125 mBit). However, the speed does drop quite a bit with distance and obstacles. Thick walls, metal cabinets etc. I wouldn't have thought your Clients were too far from your FS PC and the Access Point, though. Or are they all a long way from the Access Point, with obstacles? Regards, Pete Link to comment Share on other sites More sharing options...
steveellis Posted December 4, 2004 Author Report Share Posted December 4, 2004 Hello Peter, Thank you for your reply, this is the log for the PC that has the router on and is running AS, e.t.c. If you need some more info, I will be back on forums in 2 hrs.. ********* WideClient Log [version 6.414] Class=FS98MAIN ********* Date (dmy): 04/12/04, Time 10:14:08.671: Client name is SERVER 187 Attempting to connect now 203 Connection made okay! 3140 New Client Application: "PMFileCheck" (Id=228) 176328 New Client Application: "BAVSchedule" (Id=1080) 200953 New Client Application: "AS2004" (Id=828) 258515 New Client Application: "RCV31" (Id=476) 4936437 Timed out response: connection assumed lost! 4936484 Ready to try connection again 4936500 Attempting to connect now 4956515 Timed out response: connection assumed lost! 4956515 Ready to try connection again 4956515 Error on client pre-Connection Select() [Error=10038] Socket operation on nonsocket 4956515 Attempting to connect now 4977578 Error on client pre-Connection Select() [Error=10060] Connection timed out 4977578 Ready to try connection again 4977609 Attempting to connect now 5008672 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 5008672 Ready to try connection again 5008734 Attempting to connect now 5008859 Error on client pre-Connection Select() [Error=10065] No route to host 5008859 Ready to try connection again 5008922 Attempting to connect now 5059828 Error on client pre-Connection Select() [Error=10060] Connection timed out 5059828 Ready to try connection again 5059859 Attempting to connect now 5071015 Connection made okay! 5129890 Timed out response: connection assumed lost! 5129890 Ready to try connection again 5129922 Attempting to connect now 5133656 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 5133656 Ready to try connection again 5133672 Attempting to connect now 5133672 Error on client pre-Connection Select() [Error=10065] No route to host 5133687 Ready to try connection again 5133734 Attempting to connect now 5184734 Error on client pre-Connection Select() [Error=10060] Connection timed out 5184734 Ready to try connection again 5184797 Attempting to connect now 5196000 Connection made okay! 5280984 Error on client post-Connection Select() [Error=10053] Software caused connection abort 5280984 Ready to try connection again 5281015 Attempting to connect now 5283656 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 5283656 Ready to try connection again 5283703 Attempting to connect now 5283703 Error on client pre-Connection Select() [Error=10065] No route to host 5283703 Ready to try connection again 5283765 Attempting to connect now 5334797 Error on client pre-Connection Select() [Error=10060] Connection timed out 5334797 Ready to try connection again 5334828 Attempting to connect now 5356953 Connection made okay! 6971953 Timed out response: connection assumed lost! 6971953 Ready to try connection again 6971984 Attempting to connect now 7018672 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 7018687 Ready to try connection again 7018734 Attempting to connect now 7018734 Error on client pre-Connection Select() [Error=10065] No route to host 7018750 Ready to try connection again 7018797 Attempting to connect now 7069843 Error on client pre-Connection Select() [Error=10060] Connection timed out 7069843 Ready to try connection again 7069859 Attempting to connect now 7213672 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 7213672 Ready to try connection again 7213687 Attempting to connect now 7213687 Error on client pre-Connection Select() [Error=10065] No route to host 7213687 Ready to try connection again 7213734 Attempting to connect now 7264984 Error on client pre-Connection Select() [Error=10060] Connection timed out 7264984 Ready to try connection again 7265000 Attempting to connect now 7265000 Connection made okay! 7400000 Timed out response: connection assumed lost! 7400000 Ready to try connection again 7400062 Attempting to connect now 7436312 Reception maximum achieved: 39 frames/sec, 5237 bytes/sec 7436312 Reception average achieved whilst connected: 21 frames/sec, 500 bytes/sec 7436312 Max receive buffer = 4165, Max send depth = 4 7436312 ********* Log file closed (Buffers: MaxUsed 5, Alloc 717392 Freed 717392 Refused 0) ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 4, 2004 Report Share Posted December 4, 2004 Thank you for your reply, this is the log for the PC that has the router on and is running AS, e.t.c. Er"PC that has the router on"? You mean this PC is hard-wired whilst the others are wireless? That probably isn't that relevant, except that with AS2004 getting its Internet weather through that, the hard-wiring should give you better capacity -- I assume your Nework card in that PC is 100 mbps capable, at least? Unfortunately, the Client log is only half the story. Where's the Server log? I need that to see what the Server thinks is going on. Just looking at this end for now, although all the programs are loaded up straight away it was a good 1hr 18 minutes before the first errors appeared. What might have been different then? AS2004 would be pretty busy dowloading weather and sending it to FS soon after FS was started. 4956515 Error on client pre-Connection Select() [Error=10038] Socket operation on nonsocket 4977578 Error on client pre-Connection Select() [Error=10060] Connection timed out 5008672 Error on client pre-Connection Select() [Error=10053] Software caused connection abort 5008859 Error on client pre-Connection Select() [Error=10065] No route to host Four completely different errors reported by Windows, one after the otherone of which seems quite astounding. "no route to host" means that the router or whatever lost track of what was connected to it completely. After all that kerfuffle, things settled down again: 5356953 Connection made okay! 6971953 Timed out response: connection assumed lost! until exactly the same problems occurred. This time the good part lasted 27 minutes. It seems rather odd how things can be perfect for long periods then go haywire. What is likely to be happening in those times when it does? Anything you notice? Really, there's nothing you can do in WideFS which will fix errors like this reported by Windows. You could try using the IPX/SPX protocol, which is a little more efficient and may avoid clashes with AS2004's internet access for weather. To see if those Internet accesses are causing a problem you could try running AS2004 in an off-line mode, without auto-updates. I think it can be set that way. This is just to try to identify the problem, mind. I'm not suggesting keeping it like that. You didn't say whether all these devices run at 54 mbps. Trying to squeeze AS2004 operations AND RCV31 operations through the router may "overload it", but it isn't a very good design if it isn't coping. Apert from some process of elimination, trying things one way and another, I can't really see how I can help further. I'll look at the Server LOG to see if that throws any other light on it. But you might be better seeking Network configuring help from an expert like Katy Pluta, over in the FS2004 Forum (on the PM support site). Are the other two clients also Wireless? Don't they have problems at the same or different times? Regards, Pete Link to comment Share on other sites More sharing options...
steveellis Posted December 4, 2004 Author Report Share Posted December 4, 2004 Hi Peter, Many thanks so far, here is my server log, but a strange thing happened whilst pulling this log from my PCs which are upstairs, the connection dropped, and the WAG54G needed a reboot, the PCs upstairs had also dropped out of the network. I am starting to think if an overload problem has caused this to happen. My connection downstairs is low and I know about this For a lilttle info the PC running the WAG54G is wired to the PC, and the other 4 PCs are wireless and about 3 feet away and the connection speed is 54MBPS ********* WideServer.DLL Log [version 6.414] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 04/12/04, Time 10:11:20.171: Server name is FLIGHTSIM 111813 Initialising TCP/IP server 111828 Initialising IPX/SPX server 111844 ServerNode=21139.43674.0.0.256 122891 Restarting service due to total lack of use 127219 Incoming connection Accepted ok (skt=3408) 127219 Connected to computer "SERVER" (skt=3408) 156250 Incoming connection Accepted ok (skt=3288) 156266 Connected to computer "FLIGHTSIM2" (skt=3288) 222141 Incoming connection Accepted ok (skt=3436) 222141 Connected to computer "FLIGHTSIM3" (skt=3436) 5050485 Retried 20 times: sends blocked for over 5 secs! (0 of 558 sent), Error=10035 (skt=3288) 5050657 Retried 20 times: sends blocked for over 5 secs! (0 of 547 sent), Error=10035 (skt=3408) 5050750 Retried 20 times: sends blocked for over 5 secs! (0 of 422 sent), Error=10035 (skt=3436) 5055500 Retried 19 times: sends blocked for over 5 secs! (0 of 548 sent), Error=10035 (skt=3288) 5055719 Retried 19 times: sends blocked for over 5 secs! (0 of 557 sent), Error=10035 (skt=3408) 5055766 Retried 19 times: sends blocked for over 5 secs! (0 of 427 sent), Error=10035 (skt=3436) 5060532 Retried 19 times: sends blocked for over 5 secs! (0 of 579 sent), Error=10035 (skt=3288) 5060532 Error 10035: sends blocked for too long! Removing client (skt=3288) 5060750 Retried 19 times: sends blocked for over 5 secs! (0 of 570 sent), Error=10035 (skt=3408) 5060750 Error 10035: sends blocked for too long! Removing client (skt=3408) 5060797 Retried 19 times: sends blocked for over 5 secs! (0 of 442 sent), Error=10035 (skt=3436) 5060797 Error 10035: sends blocked for too long! Removing client (skt=3436) 5197891 Incoming connection Accepted ok (skt=2636) 5197938 Connected to computer "SERVER" (skt=2636) 5197938 Incoming connection Accepted ok (skt=4024) 5197985 Connected to computer "FLIGHTSIM3" (skt=4024) 5202141 Incoming connection Accepted ok (skt=3716) 5202141 Connected to computer "FLIGHTSIM2" (skt=3716) 5216203 Send ok but needed 6 attempts! (533 of 533 sent) (skt=3716) 5221907 Send ok but needed 3 attempts! (341 of 341 sent) (skt=4024) 5222469 Send ok but needed 3 attempts! (334 of 334 sent) (skt=4024) 5227313 Send ok but needed 5 attempts! (505 of 505 sent) (skt=3716) 5230828 Send ok but needed 4 attempts! (392 of 392 sent) (skt=4024) 5232032 Send ok but needed 3 attempts! (348 of 348 sent) (skt=4024) 5237438 Retried 20 times: sends blocked for over 5 secs! (0 of 426 sent), Error=10035 (skt=4024) 5240235 Retried 20 times: sends blocked for over 5 secs! (0 of 550 sent), Error=10035 (skt=3716) 5242532 Retried 19 times: sends blocked for over 5 secs! (0 of 451 sent), Error=10035 (skt=4024) 5243610 Retried 20 times: sends blocked for over 5 secs! (0 of 205 sent), Error=10035 (skt=2636) 5245360 Retried 19 times: sends blocked for over 5 secs! (0 of 552 sent), Error=10035 (skt=3716) 5247610 Retried 19 times: sends blocked for over 5 secs! (0 of 451 sent), Error=10035 (skt=4024) 5247610 Error 10035: sends blocked for too long! Removing client (skt=4024) 5248672 Retried 19 times: sends blocked for over 5 secs! (0 of 215 sent), Error=10035 (skt=2636) 5250391 Retried 19 times: sends blocked for over 5 secs! (0 of 565 sent), Error=10035 (skt=3716) 5250391 Error 10035: sends blocked for too long! Removing client (skt=3716) 5252922 Error 10054: client socket disconnected at Client: removing (skt=2636) 5322907 Incoming connection Accepted ok (skt=3420) 5322907 Incoming connection Accepted ok (skt=3452) 5322907 Connected to computer "SERVER" (skt=3420) 5322907 Connected to computer "FLIGHTSIM3" (skt=3452) 5323094 Incoming connection Accepted ok (skt=4568) 5323141 Connected to computer "FLIGHTSIM2" (skt=4568) 5395266 Retried 20 times: sends blocked for over 5 secs! (0 of 655 sent), Error=10035 (skt=4568) 5395485 Retried 20 times: sends blocked for over 5 secs! (0 of 394 sent), Error=10035 (skt=3452) 5399157 Retried 20 times: sends blocked for over 5 secs! (0 of 102 sent), Error=10035 (skt=3420) 5400500 Retried 20 times: sends blocked for over 5 secs! (0 of 731 sent), Error=10035 (skt=4568) 5400719 Retried 20 times: sends blocked for over 5 secs! (0 of 427 sent), Error=10035 (skt=3452) 5404375 Retried 20 times: sends blocked for over 5 secs! (0 of 112 sent), Error=10035 (skt=3420) 5405469 Error 10035: sends blocked for too long! Removing client (skt=4568) 5405672 Error 10035: sends blocked for too long! Removing client (skt=3452) 5408047 Error 10054: client socket disconnected at Client: removing (skt=3420) 5477907 Incoming connection Accepted ok (skt=4248) 5477907 Connected to computer "FLIGHTSIM3" (skt=4248) 5482250 Incoming connection Accepted ok (skt=3692) 5482297 Connected to computer "FLIGHTSIM2" (skt=3692) 5483813 Incoming connection Accepted ok (skt=3304) 5483860 Connected to computer "SERVER" (skt=3304) 7087282 Retried 20 times: sends blocked for over 5 secs! (0 of 784 sent), Error=10035 (skt=3692) 7087578 Retried 20 times: sends blocked for over 5 secs! (0 of 492 sent), Error=10035 (skt=4248) 7090391 Retried 20 times: sends blocked for over 5 secs! (0 of 1143 sent), Error=10035 (skt=3304) 7092328 Retried 19 times: sends blocked for over 5 secs! (0 of 914 sent), Error=10035 (skt=3692) 7092641 Retried 19 times: sends blocked for over 5 secs! (0 of 532 sent), Error=10035 (skt=4248) 7095516 Retried 18 times: sends blocked for over 5 secs! (0 of 1706 sent), Error=10035 (skt=3304) 7097313 Error 10035: sends blocked for too long! Removing client (skt=4248) 7097313 Error 10035: sends blocked for too long! Removing client (skt=3692) 7097922 Error 10054: client socket disconnected at Client: removing (skt=3304) 7232860 Incoming connection Accepted ok (skt=5828) 7232907 Connected to computer "FLIGHTSIM2" (skt=5828) 7244782 Retried 20 times: sends blocked for over 5 secs! (0 of 193 sent), Error=10035 (skt=5828) 7250047 Retried 20 times: sends blocked for over 5 secs! (0 of 248 sent), Error=10035 (skt=5828) 7253000 Error 10054: client socket disconnected at Client: removing (skt=5828) 7387891 Incoming connection Accepted ok (skt=5012) 7387891 Connected to computer "FLIGHTSIM2" (skt=5012) 7388907 Incoming connection Accepted ok (skt=5384) 7388953 Connected to computer "FLIGHTSIM3" (skt=5384) 7391797 Incoming connection Accepted ok (skt=5728) 7391844 Connected to computer "SERVER" (skt=5728) 7515547 Retried 20 times: sends blocked for over 5 secs! (0 of 874 sent), Error=10035 (skt=5728) 7516766 Retried 20 times: sends blocked for over 5 secs! (0 of 152 sent), Error=10035 (skt=5012) 7516813 Retried 20 times: sends blocked for over 5 secs! (0 of 152 sent), Error=10035 (skt=5384) 7520766 Retried 20 times: sends blocked for over 5 secs! (0 of 880 sent), Error=10035 (skt=5728) 7521985 Retried 20 times: sends blocked for over 5 secs! (0 of 153 sent), Error=10035 (skt=5012) 7522032 Retried 20 times: sends blocked for over 5 secs! (0 of 152 sent), Error=10035 (skt=5384) 7522828 Error 10054: client socket disconnected at Client: removing (skt=5384) 7522875 Error 10054: client socket disconnected at Client: removing (skt=5728) 7523063 Error 10054: client socket disconnected at Client: removing (skt=5012) 7730891 Incoming connection Accepted ok (skt=4740) 7730938 Connected to computer "FLIGHTSIM2" (skt=4740) 7733641 Incoming connection Accepted ok (skt=4580) 7733672 Connected to computer "FLIGHTSIM3" (skt=4580) 7827672 Closing down now ... Memory managed: Offset records: 4214 alloc, 4214 free Internal LAN buffers, maximum used: 1, refused: 0 Throughput maximum achieved: 120 frames/sec, 20619 bytes/sec Throughput average achieved for complete session: 28 frames/sec, 4683 bytes/sec ********* Log file closed ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 4, 2004 Report Share Posted December 4, 2004 but a strange thing happened whilst pulling this log from my PCs which are upstairs, the connection dropped, and the WAG54G needed a reboot, the PCs upstairs had also dropped out of the network. I am starting to think if an overload problem has caused this to happen. No, that's not right. It's starting to look like a faulty router, if you ask me. But that would be difficult to prove without having another to try. Of course, it could be buggy firmware in the router, so another one of the same make wouldn't prove it either. Have you checked to see if there are any updates? The only time I've ever had to re-boot (reset really -- power off, count to 10, power on) any of my Network thingies (ADSL modem/router, two wureless access points, one 8 way and two 4 way switches) was after a load of power surges/cuts during a bad storm. Even then it was only one access point and one switch needing power cycling to get them out of a coma! Anyway, I see from your log (I won't repeat bits of it here, it all looks bad) that the whole Network gets blocked, not just the one with ActiveSky on. This just shouldn't happen with decent hardware and connections. The suspicions must lie with the router and/or the wireless card in the FS PC. They are the only two parts which are common for all clients. Sorry, but I think I've reached about the limit of my knowledge here. Whilst it may well be something about the set-up in your Windows machines (FS PC?), I'm really inclined to think it may be hardware/firmware. But see if you can get more expert opinion. Some way of eliminating things would be useful. I suppose you could swap over the Wireless card/adapter from one of the Clients to the FS PC? If the Router has another Ethernet socket, perhaps you could try a hard-wired connection to the FS PC -- you'd need a cheap PCI Network Card for that. It might be worth hardwiring at least the FS PC anyway. That's the "hub" of all the activity after all. Regards, Pete Link to comment Share on other sites More sharing options...
steveellis Posted December 4, 2004 Author Report Share Posted December 4, 2004 Hi Peter, Its the first time I have contacted you on the forum and I would like to thank you for your quick response, time and possible workarounds. The support you give is phenomenal, I will try some things out as you have suggested. 8) Link to comment Share on other sites More sharing options...
steveellis Posted December 5, 2004 Author Report Share Posted December 5, 2004 I followed Pete's advice and hardwired the FS PC to the WAG54G and left the other 2 PCS on wireless networking. Ran to Frankfurt and did not experience any problems whatsoever. It looks like ( in my case, anyway ) that the linksys hardware may be prone to overload, might be an interesting tip for anyone else that goes down this wireless route. For info, the "Instructor Station" as I call it was running : Active Sky 2004, Radar Contact and British Airways Virtual Software which basically is a flight monitor with moving map. Thanks again Pete for the suggestion, :D :D Link to comment Share on other sites More sharing options...
Pete Dowson Posted December 6, 2004 Report Share Posted December 6, 2004 I followed Pete's advice and hardwired the FS PC to the WAG54G and left the other 2 PCS on wireless networking.Ran to Frankfurt and did not experience any problems whatsoever. Great! Glad it was so easy to resolve. But I must say that it does not speak highly of that particular router -- not that you can overload it, but that it fails in such a way when you do. It should be able to fend off traffic it cannot cope with rather than apparently give up and do nothing! Regards, 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