eefields Posted May 31, 2009 Report Posted May 31, 2009 Hello, All of a sudden, Wideclient on my laptop has stopped connecting to the FSX PC. I recently installed a new version of Capt Sim 757 and that is the only change that has been made to my computer. Currently, I have it set up to run TCP in the ini fil using my computer name. I am using Windows Vista on both computers. Any thoughts or ideas to what may be causing my system to not connect? Thanks, Eric Fields VP, Events American Virtual Airlines
Pete Dowson Posted May 31, 2009 Report Posted May 31, 2009 All of a sudden, Wideclient on my laptop has stopped connecting to the FSX PC. I recently installed a new version of Capt Sim 757 and that is the only change that has been made to my computer. Currently, I have it set up to run TCP in the ini fil using my computer name. I doubt that installing an aircraft will affect your network settings. And WideFS doesn't change itself. If your WideClient is being told (via an edited INI file) to specifically select the Server by IP Address and you aren't using fixed IP addresses, then maybe your IP addresses have changed. If not, then either you've changed something and don't remember, or something on your network is corrupted, or has developed a fault. I am using Windows Vista on both computers. Any thoughts or ideas to what may be causing my system to not connect? Not with only the information you've provided. There are always log files produced by WideServer and WideClient. Both are relevant and are always the first place to look on any sort of problem. The FSUIPC4.INI file may also be relevant. By all means paste the text from them here if you don't spot the problem yourself. I also always need VERSION numbers -- FS, FSUIPC, and WideFS. Regards Pete
eefields Posted May 31, 2009 Author Report Posted May 31, 2009 Pete, Sorry about that! Here are some more details. FSX WideclientFS98 FSUIPC4 Here is the log from Wideclient ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 31/05/09, Time 09:23:30.384: Client name is VISTA-U8PSHC4 2403 Attempting to connect now 2419 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 2419Okay, IP Address = 64.30.160.130 3479 Error on client pre-Connection Select() [Error=10061] Connection refused 3479 Ready to try connection again 4509 Attempting to connect now 63337 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 63353Okay, IP Address = 64.30.160.130 124271 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 124271Okay, IP Address = 64.30.160.130 185220 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 185220Okay, IP Address = 64.30.160.130 246186 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 246186Okay, IP Address = 64.30.160.130 307166 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 307166Okay, IP Address = 64.30.160.130 368085 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 368100Okay, IP Address = 64.30.160.130 429066 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 429066Okay, IP Address = 64.30.160.130 490046 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 490046Okay, IP Address = 64.30.160.130 550965 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 550980Okay, IP Address = 64.30.160.130 612226 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 612226Okay, IP Address = 64.30.160.130 673145 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 673145Okay, IP Address = 64.30.160.130 736590 Error on client pre-Connection Select() [Error=10060] Connection timed out 736590 Ready to try connection again 737604 Attempting to connect now 737604 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 737604Okay, IP Address = 64.30.160.130 738665 Error on client pre-Connection Select() [Error=10061] Connection refused 738665 Ready to try connection again 739695 Attempting to connect now 798507 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 798507Okay, IP Address = 64.30.160.130 859410 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 859410Okay, IP Address = 64.30.160.130 920406 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 920406Okay, IP Address = 64.30.160.130 981294 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 981294Okay, IP Address = 64.30.160.130 1041448 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1041448Okay, IP Address = 64.30.160.130 1102460 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1102460Okay, IP Address = 64.30.160.130 1163362 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1163362Okay, IP Address = 64.30.160.130 1224593 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1224593Okay, IP Address = 64.30.160.130 1285527 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1285527Okay, IP Address = 64.30.160.130 1351921 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1351921Okay, IP Address = 64.30.160.130 1412839 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1412839Okay, IP Address = 64.30.160.130 1473024 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1473024Okay, IP Address = 64.30.160.130 1533958 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 1533958Okay, IP Address = 64.30.160.130
eefields Posted May 31, 2009 Author Report Posted May 31, 2009 What do you need from FSUIPC? I tried doing a log in FSUIPC the log in only 1 line long: 1013538 Ready Flags: Read-To-Fly=Y, In Menu=N, In Dlg=N Let me know if this is helpful. Eric
eefields Posted May 31, 2009 Author Report Posted May 31, 2009 I checked my IP addresses. They are the same on both computers. 70.149.17.121 Thanks, Eric
Pete Dowson Posted May 31, 2009 Report Posted May 31, 2009 Here is the log from Wideclient That IP address looks suspicious: 2419 Trying TCP/IP host "ERICFIELDS-PC" port 8002 ... 2419Okay, IP Address = 64.30.160.130 Local IP addresses are normally somerthing like 192.168...... Please check your FSX PC. I suspect your router or switch is fooling Windows on the cleimt into getting a wrong IP address. Let's see the Server log. If you can find your FSX PCs IP address you could give that in the Client INI (via "ServerIPaddr= ..." instead of "ServerName="). Alternatively, if your two PCs are both in the same WorkGroup, you shouldn't need to tell WideClient the Server details at all -- by default WideFS doesn't use such details but connects automatically. Regards Pete
Pete Dowson Posted May 31, 2009 Report Posted May 31, 2009 I tried doing a log in FSUIPC the log in only 1 line long: You don't need to "do" an FSUIPC log -- a log is ALWAYS produced! And it is impossible for an FSUIPC4.LOG file to contain only one line. There are headings and all sorts even before anythingfrom the session is logged! Pete
Pete Dowson Posted May 31, 2009 Report Posted May 31, 2009 I checked my IP addresses. They are the same on both computers. 70.149.17.121 I have no idea where you are looking, but if both PCs have the same IP address then they are not distinguishable on the network and cannot communicate with each other. Furthermore, the IP address which the client is looking for is completely different again -- not only not in the same network, but not in the same network group! I suspect you have a complete network b***s up which you need to sort out. Can you tell me why you edited the WideClient INI file and what you changed? Something most certainly is really out of whack! Pete
Poppa Bear Posted June 16, 2009 Report Posted June 16, 2009 I, too, am having a problem where widefs simply quit connecting. As far as I can tell, there have been no significant network or OS changes to cause this. The client and FS side can ping each other, they see shares on each other and there are no AV restrictions. Both connect to the 'Net as before. For kicks and giggles, I even added the .exe to my wife's computer (don't tell her!) and it, too, was unable to connect to the FS box. I "reinstalled" the widefs components on both sides, without effect. I had recently completely reinstalled widoze onto the FS box but, again, everything was working after that up until this weekend. Thanks for your help. V/r, Ken
Poppa Bear Posted June 19, 2009 Report Posted June 19, 2009 UPDATE: After RTFM'ing, I tried the IPX protocol, lmhosts, ServerName and ServerIPAddr procedures and was successful with only the ServerIPAddr statement. I'm happy that WideFS is now working but am puzzled as to how was it working before and what caused it to stop working. Regardless, hope you had a satisfactory holiday. Cheers!!
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