Andrew Purdie Posted January 21, 2008 Report Share Posted January 21, 2008 I have tried everything and read whatever i could on google...but nothing is working. I am not able to connect to WideFS. my host PC is using Vista, and my client is using XP. here is the code in my .ini files. WideClient.ini ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerName=FLYING 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+ ; ========================================= -------------------------------------------------------------------------------------------------- WideServer.ini ; PLEASE SEE the documentation for parameter details ; ================================================== [Config] Port=8002 ProtocolPreferred=TCP ; ----------------------------------------------- [user] Log=Errors+ ; =============================================== ---------------------------------------------------------------------------------------------------------- WideClient.txt ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 20/01/08, Time 18:38:38.055: Client name is USER-BC0221EA2D 1002 Attempting to connect now 1012 Trying TCP/IP host "FLYING" port 8002 ... 1012Okay, IP Address = 192.168.1.100 1933 Error on client pre-Connection Select() [Error=10061] Connection refused 1933 Ready to try connection again 2985 Attempting to connect now 6029 ****** End of session performance summary ****** 6029 Total time connected = 0 seconds 6029 Reception maximum: 0 frames/sec, 0 bytes/sec 6029 Transmission maximum: 0 frames/sec, 0 bytes/sec 6029 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 6029 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* ------------------------------------------------------------------------------------------------------------- Thanks for the help Pete!!! Andrew Link to comment Share on other sites More sharing options...
JSkorna Posted January 21, 2008 Report Share Posted January 21, 2008 Make sure the firewalls on both machines are allowing access. Link to comment Share on other sites More sharing options...
Andrew Purdie Posted January 21, 2008 Author Report Share Posted January 21, 2008 yep i did....and nothin Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 21, 2008 Report Share Posted January 21, 2008 I have tried everything and read whatever i could on google...but nothing is working. I am not able to connect to WideFS. my host PC is using Vista, and my client is using XP. here is the code in my .ini files.... ServerName=FLYING Protocol=TCP Why have you entered the ServerName and Protocol parameters? When using all modern Windows versions (XP or Vista), WideFS is self-configuring. You should not need to touch the INI files. ********* WideClient Log [version 6.75] Class=FS98MAIN *********Date (dmy): 20/01/08, Time 18:38:38.055: Client name is USER-BC0221EA2D 1002 Attempting to connect now 1012 Trying TCP/IP host "FLYING" port 8002 ... 1012Okay, IP Address = 192.168.1.100 1933 Error on client pre-Connection Select() [Error=10061] Connection refused The error "connection refused" is from Windows. It is simply refusing to connect to the Server PC. This could be due to any number of reasons, but the usual ones are: 1) FS+WideServer isn't actually running on that PC. 2) The access is blocked by a firewall 3) The two PCs are not in the same WorkGroup Unfortunately you only show here half the story anyway. Where's the WideServer log file from the FS PC please? Regards Pete Link to comment Share on other sites More sharing options...
Andrew Purdie Posted January 21, 2008 Author Report Share Posted January 21, 2008 I'm running fsuipc 4+WideFS, so they are both running. Here is the wideclient.txt from my PC running FS. ********* WideServer.DLL Log [version 7.20] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 20/01/08, Time 23:44:20.102: Server name is FLYING 15678 Initialising TCP/IP server 15693 Initialising IPX/SPX server 15693 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15693 Failed to start IPX/SPX Server 15693 Initialising UDP/IP server 16317 Broadcasting service every 1000 mSecs 321752 Closing down now ... Memory managed: Offset records: 39 alloc, 38 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 ********* ----------------------------------------------------------------------------------------------------- The two PCs are not in the same WorkGroup What does this mean? Sorry im so confused lol :roll: . So i have re-copied the default files from the WideFS.zip. I tried running WideFS on the client and Fsuipc 4 + WideFS on the PC and still nothing is happening. Thank You so much for the help Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 21, 2008 Report Share Posted January 21, 2008 I'm running fsuipc 4+WideFS, so they are both running. Here is the wideclient.txt from my PC running FS. Well, the WideServer log, yes. And that shows things okay too, excepting of course it never sees the Client (I assume you DID try to run the client during the 5 minutes this FSX session was running? If not it might be a good idea to try again and then show me the log). The two PCs are not in the same WorkGroup What does this mean? Sorry im so confused lol :roll: . You need both PCs to be in the same WorkGroup so they can work together. "WorkGroup" = "group for working together". Your WorkGroup name is set in the computer properties -- on Windows XP, right-click on "My Computer" and select Properties then Computer Name. You'll see it. To change it click the "Change" button. For Vista it is somewhere similar I believe. So i have re-copied the default files from the WideFS.zip. I tried running WideFS on the client and Fsuipc 4 + WideFS on the PC and still nothing is happening. Well, it would have helped to show the WideClient log from that attempt too, just so i can make sure the broadcasts from the FS PC are getting through. Please, whenever changing anything,, show BOTH logs, each time. If it isn't due to having the PCs in separate WorkGroups, then it must be a firewall problem. Regards Pete Link to comment Share on other sites More sharing options...
Andrew Purdie Posted January 21, 2008 Author Report Share Posted January 21, 2008 ok, so i set both computers to the same workgroup (flight). now, with EVERYTHING set to default on both computers, here is the message from the wideclient.txt ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 21/01/08, Time 11:50:03.096: Client name is ANDREW 972 Attempting to connect now 1973 Trying to locate server: Need details from Server Broadcast 1973 Failed to connect: waiting to try again ------------------------------------------------------------------------------ i have both firewalls turned off. with the parameters set (ServerName=FLYING and Protocol=TCP) in the WideClient.ini i get this message. ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 21/01/08, Time 11:53:30.354: Client name is ANDREW 992 Attempting to connect now 1002 Trying TCP/IP host "FLYING" port 8002 ... 1002Okay, IP Address = 192.168.1.100 1983 Error on client pre-Connection Select() [Error=10061] Connection refused 1983 Ready to try connection again 3004 Attempting to connect now ------------------------------------------------------------------------------------------------- on the host computer, running FSX, there is no wideserver.txt Thanks Andrew Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 21, 2008 Report Share Posted January 21, 2008 ok, so i set both computers to the same workgroup (flight). now, with EVERYTHING set to default on both computers, here is the message from the wideclient.txt********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 21/01/08, Time 11:50:03.096: Client name is ANDREW 972 Attempting to connect now 1973 Trying to locate server: Need details from Server Broadcast 1973 Failed to connect: waiting to try again It will say that until you have the Server operating -- i.e. FS running and ready to fly. Where's the comparable WideServer log? with the parameters set (ServerName=FLYING and Protocol=TCP) in the WideClient.ini i get this message.********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 21/01/08, Time 11:53:30.354: Client name is ANDREW 992 Attempting to connect now 1002 Trying TCP/IP host "FLYING" port 8002 ... 1002Okay, IP Address = 192.168.1.100 1983 Error on client pre-Connection Select() [Error=10061] Connection refused The same as before. At least these are both consistent. They both say the FS PC is either not running FS + WideServer, or it is not in the same Network. on the host computer, running FSX, there is no wideserver.txt There never is any "wideserver.txt" file anyway (nor a WideClient.txt on the client). The files you want are LOG files. If you do really mean there is no WideServer log file, what on Earth happened to the one you showed me earlier? Did you delete it? And each time you run it it saves the last log too, as WideServer1.log. If no WideServer.Log is being produced when you run FS + FSUIPC4 with WideFS enabled, then WideServer is most certainly not running at all. Please double check. Is there even an FSUIPC4.Log file? If not then FSUIPC4 isn't running either. You seem to have stopped making any sense! If WideServer is running in FSX the title bar of FSX (in Windowed mode) will say so, and will say either that it is waiting for clients or will say how many clients are connected. Everything in this latest message of yours points to a total absence of FSX running or WideFS being enabled in it. This could go on forever if you keep going backwards. :-( Pete Link to comment Share on other sites More sharing options...
Andrew Purdie Posted January 21, 2008 Author Report Share Posted January 21, 2008 ITS WORKING :mrgreen: :mrgreen: :mrgreen: The problem was my FireWall, I downloaded Comodo (a firewall) and its connected!! thank you for your help! Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 21, 2008 Report Share Posted January 21, 2008 ITS WORKING :mrgreen: :mrgreen: :mrgreen: The problem was my FireWall Aha! That's what we thought at the beginning! :roll: Glad you have it sorted now. :D 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