WFH Posted October 26, 2008 Report Posted October 26, 2008 Peforming full reinstall of Server to relieve pressure. Registered version of FSUIPC for FSX on XP - latest version installed, registration details inserted, confirmed and rebooted. Port 8002 for WideFS opened in Windows firewall on both server and client. They just do not connect. Both computers access internet through home hub without any problem but not 'chatting' to each other. Searched on 24093 Error on client pre-Connection Select() [Error=10060] Connection timed out and turned up one or two threads non e of which helped. Having been trying to sort this for 6 hours am now running out of ideas. Any help appreciated. ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 26/10/08, Time 13:44:29.734: Client name is CLIENT 3109 Attempting to connect now 3125 Trying TCP/IP host "SERVER" port 8002 ... 3125Okay, IP Address = 192.168.1.65 24093 Error on client pre-Connection Select() [Error=10060] Connection timed out 24093 Ready to try connection again 25093 Attempting to connect now 69093 Trying TCP/IP host "SERVER" port 8002 ... 69093Okay, IP Address = 192.168.1.65 135343 Trying TCP/IP host "SERVER" port 8002 ... 135343Okay, IP Address = 192.168.1.65 201531 Trying TCP/IP host "SERVER" port 8002 ... 201531Okay, IP Address = 192.168.1.65 267468 Trying TCP/IP host "SERVER" port 8002 ... 267468Okay, IP Address = 192.168.1.65 333781 Trying TCP/IP host "SERVER" port 8002 ... 333781Okay, IP Address = 192.168.1.65 399968 Trying TCP/IP host "SERVER" port 8002 ... 399968Okay, IP Address = 192.168.1.65 466031 Trying TCP/IP host "SERVER" port 8002 ... 466031Okay, IP Address = 192.168.1.65 532156 Trying TCP/IP host "SERVER" port 8002 ... 532156Okay, IP Address = 192.168.1.65 598468 Trying TCP/IP host "SERVER" port 8002 ... 598468Okay, IP Address = 192.168.1.65 600984 ****** End of session performance summary ****** 600984 Total time connected = 0 seconds 600984 Reception maximum: 0 frames/sec, 0 bytes/sec 600984 Transmission maximum: 0 frames/sec, 0 bytes/sec 600984 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 600984 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* ********* WideServer.DLL Log [version 7.30] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 26/10/08, Time 13:17:41.156: Server name is SERVER 15188 Initialising TCP/IP server 15188 Initialising IPX/SPX server 15188 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15188 Failed to start IPX/SPX Server 15188 Initialising UDP/IP server 16156 Broadcasting service every 1000 mSecs 2200422 Closing down now ... Memory managed: Offset records: 1070 alloc, 1069 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 WideFS documentation for parameter details ; ===================================================== [Config] ServerIPAddr=192.168.1.65 ServerName=SERVER Protocol=TCP Port=8002 Window=43,44,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+ ; ===============================================
Pete Dowson Posted October 26, 2008 Report Posted October 26, 2008 Port 8002 for WideFS opened in Windows firewall on both server and client. They just do not connect. Both computers access internet through home hub without any problem but not 'chatting' to each other. Searched on 24093 Error on client pre-Connection Select() [Error=10060] Connection timed out and turned up one or two threads non e of which helped. Having been trying to sort this for 6 hours am now running out of ideas. Any help appreciated. Try turning off the firewall altogether, just as a test. I've never had to "open" Port 8002 -- if Windows tells me Wideclient wants to use the network and should I allow it, I say "yes" with the "don't ask me again" option checked. I wouldn't even know how to enable specific "ports", nor what most programs use for their ports. By the way, you are specifying both the Server IP address AND the name (and protocol) explicitly. Don't provide name AND IPaddress, that's a waste of time. Just use the name. Or better, please note that this message: 16156 Broadcasting service every 1000 mSecs indicates that WideServer is actually sending that information out regularly (on port 9002 by default). If both of your systems are in the same WorkGroup, and both running at least XP, why not let WideFS sort itself out automatically, as intended? Otherwise, sorry, but there's nothing in the logs to indicate anything other than either an incorrect IP address or a firewall blockage. Regards 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