Jump to content
The simFlight Network Forums

project747

Members
  • Posts

    1
  • Joined

  • Last visited

About project747

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    So. Cal. USA

project747's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hello Peter, I'm having a problem connecting my client to my server using FS9.1. Before I continue, let me tell you that I have no problem connecting to FS2k2 on my same server and client?!? Below is my log files for you to check out. ********* WideClient.DLL Log [version 6.41] Class=FS98MAIN ********* Date (dmy): 14/12/04, Time 04:36:36.234: Client name is PC2 46 Attempting to connect now 93 Trying TCP/IP host "Home" port 8002 ... 93Okay, IP Address = 192.168.1.100 1015 Error on client pre-Connection Select() [Error=10061] Connection refused 1031 Ready to try connection again 1031 Attempting to connect now 53562 Connection made okay! 53890 Error on client post-Connection Select() [Error=10053] Software caused connection abort 53890 Ready to try connection again 53937 Attempting to connect now 54390 Connection made okay! 54437 Error on client post-Connection Select() [Error=10053] Software caused connection abort 54437 Ready to try connection again 54500 Attempting to connect now 54500 Connection made okay! 75187 Error on client post-Connection Select() [Error=10053] Software caused connection abort 75203 Ready to try connection again 75250 Attempting to connect now 75250 Connection made okay! 75281 Connection closed by server! 75296 Ready to try connection again 75312 Attempting to connect now 75828 Connection made okay! 75828 Connection closed by server! 75828 Ready to try connection again 75875 Attempting to connect now 75875 Connection made okay! 75875 Connection closed by server! 75875 Ready to try connection again 75937 Attempting to connect now 76187 Connection made okay! 76625 Connection closed by server! 76625 Ready to try connection again 76687 Attempting to connect now 76687 Connection made okay! 80140 Error on client post-Connection Select() [Error=10053] Software caused connection abort 80140 Ready to try connection again 80187 Attempting to connect now 80593 Reception maximum achieved: 0 frames/sec, 0 bytes/sec 80593 Reception average achieved whilst connected: 0 frames/sec, 0 bytes/sec 80593 Max receive buffer = 0, Max send depth = 0 80593 ********* Log file closed (Buffers: MaxUsed 1, Alloc 19 Freed 19 Refused 0) ********* And now for the server: ********* WideServer.DLL Log [version 6.41] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 14/12/04, Time 16:06:00.343: Server name is HOME 1696172 Initialising TCP/IP server 1696172 Initialising IPX/SPX server 1696172 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 1696172 Failed to start IPX/SPX Server 1697672 Incoming connection Accepted ok (skt=14) 1697672 AsyncSelect() failed! [Error=10038] Socket operation on nonsocket (skt=14) 1697672 Initialising TCP/IP server 1697672 Initialising IPX/SPX server 1697672 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 1698156 Incoming connection Accepted ok (skt=14) 1720172 Initialising TCP/IP server 1720172 Initialising IPX/SPX server 1720172 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 1720172 Closing down now ... Memory managed: Offset records: 0 alloc, 0 free Throughput maximum achieved: 0 frames/sec, 0 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec ********* Log file closed ********* While all this is happening the status of the connection on the window bar is continuously flashing "waiting for clients" and "connected" Only in fs9.1. FS2K2 is normal and works great!! Please help! :cry: I have the same modules in both fs2k2 and fs9.1.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.