timtaylor1 Posted December 6, 2012 Report Posted December 6, 2012 I am havibg trouble communicating with my other computer using WideFS and linking to FS9. Client computer is windows XP and FS computer is windows7
Pete Dowson Posted December 6, 2012 Report Posted December 6, 2012 I am havibg trouble communicating with my other computer using WideFS and linking to FS9. Client computer is windows XP and FS computer is windows7 Without any real information I can't really help much. there are logs produced by both WirdServer and Wideclient, and these will probably show why. The most usual problem is that those two operating systems default to using different Workgrops, so broadcasts don't get through. If you please refer to the section in the WideFS user guide there is help there to sort it out. Read the section on configuring your network, especially the part with the bold red heading telling you to read it. Regards Pete
timtaylor1 Posted December 9, 2012 Author Report Posted December 9, 2012 Thought I would add these logs ********* WideClient Log [version 6.987] Class=FS98MAIN ********* Date (dmy): 09/12/12, Time 14:01:44.046: Client name is TAYLOR-1 9750 Attempting to connect now 9813 Trying TCP/IP host "Taylor-1" port 8002 ... 9813 ... Okay, IP Address = 192.168.1.5 9875 LUA: "\\Taylor-1\WideClient X\Initial.LUA": not found 10719 Error on client pre-Connection Select() [Error=10061] Connection refused 10719 Ready to try connection again 11734 Attempting to connect now 15922 ****** End of session performance summary ****** 15938 Total time connected = 0 seconds 15938 Reception maximum: 0 frames/sec, 0 bytes/sec 15938 Transmission maximum: 0 frames/sec, 0 bytes/sec 15938 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 15938 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* ********* WideServer.DLL Log [version 6.94] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 09/12/12, Time 11:31:31.599: Server name is TAYLOR-2 100589 Initialising TCP/IP server 100589 Initialising IPX/SPX server 100589 IPX/SPX socket() failed [Error=10044] Socket type not supported 100589 Failed to start IPX/SPX Server 100589 Initialising UDP/IP server 100667 Broadcasting service every 1000 mSecs 111993 Restarting service due to total lack of use 111993 Failed to start IPX/SPX Server 1873525 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 ********* Tried everything you have suggested. Would having windows 7 on the server computer resolve the problem? Tim
Luke Kolin Posted December 9, 2012 Report Posted December 9, 2012 10719 Error on client pre-Connection Select() [Error=10061] Connection refused 10719 Ready to try connection again That looks like the problem there - either WideServer wasn't started at that time or the firewall was blocking it. Cheers! Luke
timtaylor1 Posted December 10, 2012 Author Report Posted December 10, 2012 I turned off both firewalls on both computers and wideserver (Flight simulator) was started.
Pete Dowson Posted December 10, 2012 Report Posted December 10, 2012 I turned off both firewalls on both computers and wideserver (Flight simulator) was started. Nevertheless, something is blocking the access. Maybe you have a firewall you don't know about? The "connection refused" failure means simply that the connection was refused. That's all Windows tells you in such circumstances. There's nothing WideFS or I can do about it. 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