IanR Posted March 16, 2006 Report Posted March 16, 2006 Hi I have a 9 pc network running XPpro using TCP/IP and wide FS . One of the pc's wide FS log file is displayed below can any explain to me why I have so many lost connections also attached is the ini file Thank you Ian ********* WideClient Log [version 6.51] Class=FS98MAIN ********* Date (dmy): 16/03/06, Time 13:18:49.625: Client name is MCDU 1641 Attempting to connect now 1641 Connection made okay! 187391 New Client Application: "sa_wxr" (Id=3532) 251250 New Client Application: "mcdu" (Id=3556) 698187 Timed out response: connection assumed lost! 698266 Ready to try connection again 698266 Timed out response: connection assumed lost! 698266 Attempting to connect now 698297 Connection made okay! 698344 send() done [174 bytes] after 12 retries, request depth is 1 716359 Timed out response: connection assumed lost! 716359 Ready to try connection again 716422 Timed out response: connection assumed lost! 716422 Attempting to connect now 716422 Connection made okay! 734484 Timed out response: connection assumed lost! 734484 Ready to try connection again 734547 Timed out response: connection assumed lost! 734547 Attempting to connect now 734547 Connection made okay! 752641 Timed out response: connection assumed lost! 752641 Ready to try connection again 752703 Timed out response: connection assumed lost! 752703 Attempting to connect now 752703 Connection made okay! 770844 Timed out response: connection assumed lost! 770844 Ready to try connection again 770906 Timed out response: connection assumed lost! 770906 Attempting to connect now 770906 Connection made okay! 789031 Timed out response: connection assumed lost! 789031 Ready to try connection again 789094 Timed out response: connection assumed lost! 789094 Attempting to connect now 789094 Connection made okay! 807219 Timed out response: connection assumed lost! 807219 Ready to try connection again 807281 Timed out response: connection assumed lost! 807281 Attempting to connect now 807281 Connection made okay! 825422 Timed out response: connection assumed lost! 825422 Ready to try connection again 825484 Timed out response: connection assumed lost! 825484 Attempting to connect now 825484 Connection made okay! 843594 Timed out response: connection assumed lost! 843594 Ready to try connection again 843656 Timed out response: connection assumed lost! 843656 Attempting to connect now 843656 Connection made okay! 861719 Timed out response: connection assumed lost! 861719 Ready to try connection again 861781 Timed out response: connection assumed lost! 861781 Attempting to connect now 861781 Connection made okay! 879875 Timed out response: connection assumed lost! 879875 Ready to try connection again 879937 Timed out response: connection assumed lost! 879937 Attempting to connect now 879937 Connection made okay! 898062 Timed out response: connection assumed lost! 898062 Ready to try connection again 898125 Timed out response: connection assumed lost! 898125 Attempting to connect now 898125 Connection made okay! 916219 Timed out response: connection assumed lost! 916219 Ready to try connection again 916281 Timed out response: connection assumed lost! 916281 Attempting to connect now 916281 Connection made okay! 934359 Timed out response: connection assumed lost! 934359 Ready to try connection again 934422 Timed out response: connection assumed lost! 934422 Attempting to connect now 934422 Connection made okay! 952500 Timed out response: connection assumed lost! 952500 Ready to try connection again 952562 Timed out response: connection assumed lost! 952562 Attempting to connect now 952562 Connection made okay! 970687 Timed out response: connection assumed lost! 970687 Ready to try connection again 970750 Timed out response: connection assumed lost! 970750 Attempting to connect now 970750 Connection made okay! 1412312 Timed out response: connection assumed lost! 1412312 Ready to try connection again 1412375 Timed out response: connection assumed lost! 1412375 Attempting to connect now 1412375 Connection made okay! 1499375 Timed out response: connection assumed lost! 1499375 Ready to try connection again 1499437 Timed out response: connection assumed lost! 1499437 Attempting to connect now 1499437 Connection made okay! 1517562 Timed out response: connection assumed lost! 1517562 Ready to try connection again 1517625 Timed out response: connection assumed lost! 1517625 Attempting to connect now 1517625 Connection made okay! 1535750 Timed out response: connection assumed lost! 1535750 Ready to try connection again 1535812 Timed out response: connection assumed lost! 1535812 Attempting to connect now 1535812 Connection made okay! 2621031 Timed out response: connection assumed lost! 2621031 Ready to try connection again 2621094 Timed out response: connection assumed lost! 2621094 Attempting to connect now 2621094 Connection made okay! 3524875 Timed out response: connection assumed lost! 3524875 Ready to try connection again 3524937 Timed out response: connection assumed lost! 3524937 Attempting to connect now 3524937 Connection made okay! 4158250 Error on client post-Connection Select() [Error=10053] Software caused connection abort 4158250 Connection closed by server! 4158250 The connection was terminated due to a time-out or other failure! 4158266 Ready to try connection again 4158312 Attempting to connect now 4179281 Error on client pre-Connection Select() [Error=10060] Connection timed out 4179297 Ready to try connection again 4179328 Attempting to connect now ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] UseTCPIP=Yes ServerIPAddr=192.168.0.888 Window=32000,32000,160,34 Visible=Min WaitForNewData=500 NetworkTiming=5,1 ButtonScanInterval=20 ClassInstance=0 PollInterval=2000 Port=8002 ResponseTime=18 TCPcoalesce=No ApplicationDelay=0 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ; ===============================================
Pete Dowson Posted March 16, 2006 Report Posted March 16, 2006 I have a 9 pc network running XPpro using TCP/IP and wide FS . One of the pc's wide FS log file is displayed below can any explain to me why I have so many lost connections also attached is the ini file The explanation is in the Log: "Timed out response: connection assumed lost!" The poor client is not getting anything from the Server and times out after 18 seconds (the default for this). Is this happening on all Clients? Have you looked at the WideServer Log. Perhaps that shows a problem there? Pete
IanR Posted March 17, 2006 Author Report Posted March 17, 2006 thanx for the quick responce... I have just run another flight and the wide client log file is below ...ummm why the difference with the last log file with all the lost connections... ********* WideClient Log [version 6.51] Class=FS98MAIN ********* Date (dmy): 17/03/06, Time 12:40:23.343: Client name is MCDU 1328 Attempting to connect now 1344 Connection made okay! 29890 New Client Application: "mcdu" (Id=2244) 8383625 ****** End of session performance summary ****** 8383625 Total time connected = 8380 seconds 8383625 Reception maximum: 34 frames/sec, 3055 bytes/sec 8383625 Reception average whilst connected: 17 frames/sec, 342 bytes/sec 8383625 Transmission maximum: 23 frames/sec, 1021 bytes/sec 8383625 Transmission average whilst connected: 9 frames/sec, 389 bytes/sec 8383625 Max receive buffer = 626, Max send depth = 41, Send frames lost = 0 8383625 **************** Individual client application activity **************** 8383625 Client 2244 requests: 72163 (Ave 8/sec), Data: 133056503 bytes (15877/sec), Average 1843 bytes/Process 8383625 ********* Log file closed (Buffers: MaxUsed 41, Alloc 227275 Freed 227275 Refused
Pete Dowson Posted March 17, 2006 Report Posted March 17, 2006 thanx for the quick responce... I have just run another flight and the wide client log file is below ...ummm why the difference with the last log file with all the lost connections... No idea, but the Client log is only half the story -- you never said what the Server log showed, nor whether this was just on one of the Clients or all of them. If all that is happening is simple timeouts then you have something taking time off WideFS for long periods -- 18 seconds is allowed by the Client before it decides the connection is broken. But without any information I cannot tell you any more. Pete
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