Sauviat Posted August 1, 2009 Report Share Posted August 1, 2009 Hello Pete: Being a long time user of FSUIPC and Wide Client, I have never had a real problem using them (sometimes I don't understand something!). I have now installed FS Commander on both client and server. Brilliant, no problem running on server. Client goes like this: FS Commander installation no problem and the FS9 (database manager) update ran smoothly, I can get VATSIM, et al. When I come to connect FS Commander to FS9, with Wide Client waiting for a connection, I get the 'Msg#14' error code and cannot connect to FS9. I get the same when I press the GPS button also. FS Commander forum response is that the error number idetifies the problem, but not what the problem is! From your point of view is this a Wide Client configuration problem? Regards Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 1, 2009 Report Share Posted August 1, 2009 When I come to connect FS Commander to FS9, with Wide Client waiting for a connection ... If Wideclient is "waiting for a connection", there's no point in trying to "connect" any other application, unless it is a tolerant type which sits and waits for FSUIPC to be accessible, retying now and then. The title bar message "wait for a connection" does NOT mean "waiting for an application", but waiting for a connection to WideServer, in the FS PC. FS Commander forum response is that the error number idetifies the problem, but not what the problem is! Hmm. I wonder what the point of the message number is, then? Is that meaningless? Surely the author knows what the message means in terms of what it is finding wrong? Anyway, if FS isn't yet running, or it is but FSUIPC + WideServer are not yet servicing Clients (and they won't be until you are "ready to fly"), then no client program will connect. Maybe that's all the message means? From your point of view is this a Wide Client configuration problem? All the information about what WideFS is doing is put into the Log files -- WideClient.log on the client, WideServer.log on the Server. You say you're a "long time user of FSUIPC and Wide Client", so surely you recognise by now whether WideFS is connecting? (It will actually say "connected", to help! ;-) ). If you cannot get WideFS connected, please check those log files. Show me, if you like. Also think what you have changed since you had it working ("for a long time"?). Incidentally, a monor matter, but I assume you mean FSUIPC 3.916, not 3.169? Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 1, 2009 Author Report Share Posted August 1, 2009 Hi Pete: The order in which these programs are started - 1/ FS is running (waiting for clients) on the server 2/ Wide Client 3.916 runs (waiting for connection) on the client 3/ Then FS Commander is started and that is when I get the Msg#14 Log: ********* WideClient Log [version 6.786] Class=FS98MAIN ********* Date (dmy): 01/08/09, Time 15:03:58.309: Client name is HAMISH 1211 Attempting to connect now 1522 Server = CORBIERE 1552 Trying TCP/IP host "CORBIERE" port 8002 ... 1552Okay, IP Address = 192.168.100.2 22502 Error on client pre-Connection Select() [Error=10060] Connection timed out 22522 Ready to try connection again 24555 Attempting to connect now 24555 Giving up server, looking for another! 24785 Server = CORBIERE 24785 Trying TCP/IP host "CORBIERE" port 8002 ... 24785Okay, IP Address = 192.168.100.2 44864 New Client Application: "FSC85" (Id=2424) 48149 Server = CORBIERE 48149 Trying TCP/IP host "CORBIERE" port 8002 ... 48149Okay, IP Address = 192.168.100.2 71172 Giving up server, looking for another! 71602 Server = CORBIERE 71602 Trying TCP/IP host "CORBIERE" port 8002 ... 71602Okay, IP Address = 192.168.100.2 80015 ****** End of session performance summary ****** 80015 Total time connected = 0 seconds 80015 Reception maximum: 0 frames/sec, 0 bytes/sec 80015 Transmission maximum: 0 frames/sec, 0 bytes/sec 80015 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 80015 **************** Individual client application activity **************** 80015 Client 2424 requests: 10 (Ave 10/sec), Data: 540 bytes (540/sec), Average 54 bytes/Process 80015 ********* Log file closed (Buffers: MaxUsed 1, Alloc 10 Freed 10 Refused 0) ********* Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 1, 2009 Report Share Posted August 1, 2009 1/ FS is running (waiting for clients) on the server 2/ Wide Client 3.916 runs (waiting for connection) on the client 3/ Then FS Commander is started and that is when I get the Msg#14 Apparently FSCommander shouldn't be started until WideFS connects. Best to start it from Wideclient.INI using the "RunReady" facilities. The problem is you aren't getting a connection. Have you EVER had a connection? I understood from your last message that you were a "long-time user". All this time and no connection? Your WideClient log 1552 Trying TCP/IP host "CORBIERE" port 8002 ... 1552Okay, IP Address = 192.168.100.2 22502 Error on client pre-Connection Select() [Error=10060] Connection timed out only shows something wrong on the Server -- assuming, that is, you've not messed around with any timing parameters in the WideClient.INI file. You forget to show the Server log, so I can't say any more. Tell me, please, HAVE you actually used WideFS before? If so, if it connected, what have you changed? Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 1, 2009 Author Report Share Posted August 1, 2009 Pete: Yes, I used to run SB and SB3, but not in the past few months. The parameters of WideClient have not been touched since the initial installation, whenever that purchase was (details not here). WideServer Log: ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 01/08/09, Time 13:43:37.265: Server name is CORBIERE 86296 Initialising TCP/IP server 86296 Initialising IPX/SPX server 86296 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 86296 Failed to start IPX/SPX Server 86296 Initialising UDP/IP server 88109 Broadcasting service every 1000 mSecs 122390 Restarting service due to total lack of use 122406 Failed to start IPX/SPX Server 522484 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 ********* ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=78,169,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== "RunReady"- do you mean Run1? Would it look something like Run1=C:Programs\FSC Regards Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 1, 2009 Report Share Posted August 1, 2009 WideServer Log Assuming you tried to run WideClient on the client PC during this WideServer session, the WideServer log shows nothing ever got through. this suggests your network is simply not set up to allow such communication. Perhaps you have an active firewall preventing it? "RunReady"- do you mean Run1? Would it look something like Run1=C:Programs\FSC No. "Run1" would run it as soon as WideClient started. When I say "RunReady" I actually do mean "RunReady". Please refer to the WideFS documentation which clearly shows these methods load starting (and stopping) application programs! Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 2, 2009 Author Report Share Posted August 2, 2009 Hello Pete: While I still have no joy, the info of this morning is below. The server log, as you can see, is still showing yesterday's date and info! I use COMODO and have specifically allowed permissions for WideClient and FSCommander and for Port: 8002. Is there anything within the respective ini files where the parameters need to be changed? Wide Server Info: ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 01/08/09, Time 21:45:04.718: Server name is CORBIERE 119734 Initialising TCP/IP server 119750 Initialising IPX/SPX server 119750 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 119750 Failed to start IPX/SPX Server 119750 Initialising UDP/IP server 120156 Broadcasting service every 1000 mSecs 131531 Restarting service due to total lack of use 131547 Failed to start IPX/SPX Server 4383515 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 ********* Wide Client Info: ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=100,152,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 RunReady1=C:\Program Files\FSC\FSC85.exe CloseReady1=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ********* WideClient Log [version 6.786] Class=FS98MAIN ********* Date (dmy): 02/08/09, Time 13:24:38.112: Client name is HAMISH 881 Attempting to connect now 881 Server = CORBIERE 971 Trying TCP/IP host "CORBIERE" port 8002 ... 971Okay, IP Address = 192.168.100.2 21881 Error on client pre-Connection Select() [Error=10060] Connection timed out 21881 Ready to try connection again 23884 Attempting to connect now 23884 Giving up server, looking for another! 24705 Server = CORBIERE 24705 Trying TCP/IP host "CORBIERE" port 8002 ... 24705Okay, IP Address = 192.168.100.2 48409 Server = CORBIERE 48419 Trying TCP/IP host "CORBIERE" port 8002 ... 48419Okay, IP Address = 192.168.100.2 58524 New Client Application: "FSC85" (Id=708) 71362 Giving up server, looking for another! 71953 Server = CORBIERE 71953 Trying TCP/IP host "CORBIERE" port 8002 ... 71953Okay, IP Address = 192.168.100.2 83690 ****** End of session performance summary ****** 83690 Total time connected = 0 seconds 83690 Reception maximum: 0 frames/sec, 0 bytes/sec 83690 Transmission maximum: 0 frames/sec, 0 bytes/sec 83690 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 83690 **************** Individual client application activity **************** 83690 Client 708 requests: 10 (Ave 10/sec), Data: 540 bytes (540/sec), Average 54 bytes/Process 83690 ********* Log file closed (Buffers: MaxUsed 1, Alloc 10 Freed 10 Refused 0) ********* Regards Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 2, 2009 Report Share Posted August 2, 2009 While I still have no joy, the info of this morning is below. The server log, as you can see, is still showing yesterday's date and info! In that case one of the following MUST apply: * Your Server has the wrong date/time set, OR * You've not got WideServer installed, so it isn't running, OR * You've got hold of the wrong file! There are no other possibilities! I use COMODO and have specifically allowed permissions for WideClient and FSCommander and for Port: 8002. Is there anything within the respective ini files where the parameters need to be changed? No. But is the IP address returned by Windows correct? 881 Server = CORBIERE 971 Trying TCP/IP host "CORBIERE" port 8002 ... 971Okay, IP Address = 192.168.100.2 On the test you did yesterday (or at least the date and time shown), WideServer never saw anything: 131531 Restarting service due to total lack of use Since you either didn't run WideServer today, or got the wrong log file, i couldn't comment on this mornig's test. What I don't understand, and you still haven't gotten around to explaining, is that, as "a long time user of FSUIPC and Wide Client", where you said you never had a problem, how is it that you now suddenly have no connection whatsoever between the Server and Client? What have you changed? That might be a clue, don't you think? Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 2, 2009 Author Report Share Posted August 2, 2009 Pete: I very much understand and appreciate your questions and am working through all possible scenarios to resolve this issue. As far as the network here goes and the security that is in place, all computers have to communicate with each other internally and to third parties. The computer with Wide Client running on it has specific corporate tasks and I have requested permission to disable the firewall, in order to eliminate that aspect as a problem in this context. For some time I had squawkbox running using WideClient, on this same computer and with no problems, but now I prefer to use SB on the same computer as FS9. The only change to this computer is that the whole system was changed to COMODO's firewall. In response to your questions the time and date is correct accross the network, which includes the server. Wide Server is installed. "You've got hold of the wrong file!", which you mean the log file and if so it is below. Should there be two log files? The IP address is correct by both name and numerical. I use FSNav, SSTSIM and actigate amongst others where I happily dispensed cash to purchase FSUIPC. At one stage I was with BAW virtual and decided to use SB on the computer where I have located WideClient. The original date that I registered on this site was to get WideClient operating on the same machine. That is why that nothing has changed as it was working fine. I am looking at FSC as the alternate to FSNav, only because it is now not being updated and there is no likelyhood that it will. Sad, but FSNav was a very good module for FS9. Server log: (Both the sever log and the wide client log have two logs the second one respectively has a 0 (zero) after it!) ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 02/08/09, Time 12:45:40.218: Server name is CORBIERE 213703 Initialising TCP/IP server 213781 Initialising IPX/SPX server 213781 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 213781 Failed to start IPX/SPX Server 213781 Initialising UDP/IP server 215094 Broadcasting service every 1000 mSecs 225891 Restarting service due to total lack of use 225891 Failed to start IPX/SPX Server 2591203 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 ********* Regards Martin Link to comment Share on other sites More sharing options...
Sauviat Posted August 2, 2009 Author Report Share Posted August 2, 2009 Pete, I have now had the firewall completely disabled and still no luck. The logs and ini's are below: ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] Port=8002 AdvertiseService=1 AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port2=9002 RestartTime=10 SendTimeout=15 TCPcoalesce=No ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ********* WideServer.DLL Log [version 6.78] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 02/08/09, Time 14:50:15.468: Server name is CORBIERE 147641 Initialising TCP/IP server 147656 Initialising IPX/SPX server 147656 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 147656 Failed to start IPX/SPX Server 147656 Initialising UDP/IP server 148156 Broadcasting service every 1000 mSecs 158813 Restarting service due to total lack of use 158813 Failed to start IPX/SPX Server ********* WideClient Log [version 6.786] Class=FS98MAIN ********* Date (dmy): 02/08/09, Time 14:53:38.509: Client name is HAMISH 591 Attempting to connect now 1072 Server = CORBIERE 1112 Trying TCP/IP host "CORBIERE" port 8002 ... 1112Okay, IP Address = 192.168.100.2 22082 Error on client pre-Connection Select() [Error=10060] Connection timed out 22082 Ready to try connection again 24125 Attempting to connect now 24125 Giving up server, looking for another! 24365 Server = CORBIERE 24365 Trying TCP/IP host "CORBIERE" port 8002 ... 24365Okay, IP Address = 192.168.100.2 47589 Server = CORBIERE 47849 Trying TCP/IP host "CORBIERE" port 8002 ... 47849Okay, IP Address = 192.168.100.2 55330 New Client Application: "FSC85" (Id=1464) 70882 Giving up server, looking for another! 71774 Server = CORBIERE 71774 Trying TCP/IP host "CORBIERE" port 8002 ... 71774Okay, IP Address = 192.168.100.2 79465 ****** End of session performance summary ****** 79465 Total time connected = 0 seconds 79465 Reception maximum: 0 frames/sec, 0 bytes/sec 79465 Transmission maximum: 0 frames/sec, 0 bytes/sec 79465 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 79465 **************** Individual client application activity **************** 79465 Client 1464 requests: 10 (Ave 10/sec), Data: 540 bytes (540/sec), Average 54 bytes/Process 79465 ********* Log file closed (Buffers: MaxUsed 1, Alloc 10 Freed 10 Refused 0) ********* ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] Port=8002 Window=100,154,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 RunReady1=C:\Program Files\FSC\FSC85.exe CloseReady1=Yes ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== Regards Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 2, 2009 Report Share Posted August 2, 2009 The only change to this computer is that the whole system was changed to COMODO's firewall. That's the prime suspect them. It is probably blocking access to the server by WideClient. "You've got hold of the wrong file!", which you mean the log file and if so it is below. Since the whole set of 3 possibilities was concerned with how the Log file had yesterday's date and time on it, it is obvious surely that it was the log file I was referring to? What else? :-( Should there be two log files? Only one named WideClient.log and WideServer.log -- those are the current or most recent. The previous one is saved with a numerical character included in its filename. This is done so that folks with a problem or a need to close the Client to change a parameter can do so, and get it back up straight-away, without losing any information from the previous effort. Server log: (Both the sever log and the wide client log have two logs the second one respectively has a 0 (zero) after it!) Yes, see above. 225891 Restarting service due to total lack of use The Server is never seeing hide nor hair of any Client attempts, I'm afraid. The Client is definitely being blocked at the Client end, or at the Server end, or both. Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 2, 2009 Author Report Share Posted August 2, 2009 :D :D :D Hello Pete: Process of elimination, very much so. The computer with WideClient installed, having had the firewall disabled, indicated that the firewall on there was not the issue. Having checked the firewall and the respective access permissions for FS9, right down to Wide Client I noted that the module folder where FSUIPC, etc is found was a possible 'grey' area. Whilst the FS9 folder had access, I thought that I would give the module folder it's own access and, yes, it works! What are your thoughts on this? It had been my understanding that if permissions have been given for a particular folder, everything within that folder would have permission. Suffice to say that network access and file sharing works like this. Going back to when I last excessively used SB with WideClient, no specific permissions were given, except normal network ones, etc. I would like to thank you for giving me and the forum the time to deal with this. Now that Microsoft has brought the curtain down on their flight simulation activities, with the closure of the Aces Team, I think we all must wait to see what the future of flight simulation will bring from the community as a whole: it is a very proactive community. Regards and thanks again Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 2, 2009 Report Share Posted August 2, 2009 Process of elimination, very much so. The computer with WideClient installed, having had the firewall disabled, indicated that the firewall on there was not the issue. Having checked the firewall and the respective access permissions for FS9, right down to Wide Client I noted that the module folder where FSUIPC, etc is found was a possible 'grey' area. Whilst the FS9 folder had access, I thought that I would give the module folder it's own access and, yes, it works! What are your thoughts on this? It had been my understanding that if permissions have been given for a particular folder, everything within that folder would have permission. Suffice to say that network access and file sharing works like this. There are no folder sharing permissions needed for WidefS (other than to be able to write its own logs, which it obviously can do), so I really don't understand what you are talking about. Folder permissions only really come into play in FSX on Vista and Windows 7 installations, if FSX has been installed into its default of Program Files. This is because "Program Files" is protected as a whole -- but (a) this only affects Vista-aware programs, as Vista makes provision via Aliasses for older programs, and (b) the FSUIPC4 installer makes the Modules folder read/write accessible to all. There's nothing at all that I am aware of that involves any folder permissions for WideFS. All of its exchanges are on Ethernet, there is nothing at all via folders! If you are able and have time, could you explain, please, what it is you think you have found out? Regards Pete Link to comment Share on other sites More sharing options...
Sauviat Posted August 2, 2009 Author Report Share Posted August 2, 2009 Pete: I think you have hit the nail on the head, when you say "All the exchanges are on Ethernet, there is nothing via folders!" In abstract not the folders, but here the whole operation runs via a router and sub-router and each computer must give permissions to third parties. I only have a certain amount of technical knowledge and the process of elimination prevailed. Agreed, when COMODO was put in place, all known entities were given their respective permissions, but alas not WideClient. However, I have now gone on to reinstalled SB(v4) when all was running well and no other actions were required as all is normal. Nothingelse was altered other than giving permission to the modules folder. Again, thank you for your help Regards Martin Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 2, 2009 Report Share Posted August 2, 2009 Pete: I think you have hit the nail on the head, when you say "All the exchanges are on Ethernet, there is nothing via folders!" In abstract not the folders, but here the whole operation runs via a router and sub-router and each computer must give permissions to third parties.... Nothing else was altered other than giving permission to the modules folder. Well, I'm really glad you solved it, but I'm afraid i still don't understand. To me the above two parts of your explanation are contradictory. I just can't imagine where the modules folder comes into it at all. But it doesn't matter, now you have it working. I only hope i don't meet else anyone using the same protection system as yours! ;-0 Regards Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 2, 2009 Report Share Posted August 2, 2009 Again, thank you for your help I just received your PM, sent via the simFlight boss. Perhaps you did not see the little "PM" button on my messages here, which can be used for confidential matters? I understand why you cannot explain further how the folder protection affects the Ethernet interaction -- I only wanted to understand this odd effect in case others had the same problem, and this is why I lastly expressed my hope that no one else does -- precisely because I don't understand. However, I don't understand why you think my responses here are "curt". If you mean "short and to the point", then I would take that as a compliment, as I always try to be, but then you added something about not taking offense, which does rather confuse me I'm afraid. How would I have offended you? I've looked back over the entire interaction and can see nothing to warrant this. :-( 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