Jump to content
The simFlight Network Forums

Recommended Posts

Posted (edited)

Peter, I could not delete the post I had on the forum, so am doing so now...I'll update the problem later---I think I have 2 different versions running with Server 6.78 and Client 6.86 (???) Stay tuned ! Thanks

Edited by osage
Posted

I think I have 2 different versions running with Server 6.78 and Client 6.86 (???)

Shouldn't matter, but WideClient is now up to version 6.972. WideServer doesn't change much if at all, but WideClient has gone through a lot of updates because of its support for the developing Lua libraries.

See the Download Links subforum.

Regards

Pete

Posted

Okay, using WClient 6.94 and registered FSCUIPC, 3.999.

Client not connecting; please note that Firewall is inactive, and I'm able to use Aerosoft's avionics package on network...so assuming (ouch) network is ok.

#1 XP with FS and FSUIPC and WideServer

#2 Vista with WClient

Logs below.

Thanks for the look see!

********* WideServer.DLL Log [version 6.94] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 03/07/12, Time 12:56:49.718: Server name is OSU-6B2ELM457MG

74627 Initialising TCP/IP server

74838 Initialising IPX/SPX server

74958 ServerNode=0.0.8448.12079.19109

74968 Initialising UDP/IP server

75268 Broadcasting service every 1000 mSecs

85873 Restarting service due to total lack of use

********* WideClient Log [version 6.94] Class=FS98MAIN *********

Date (dmy): 03/07/12, Time 13:01:55.922: Client name is VISTA

1092 LUA: "C:\Users\omak\Desktop\WideClientJuly\Initial.LUA": not found

1186 Attempting to connect now

2184 Trying to locate server: Need details from Server Broadcast

2184 Failed to connect: waiting to try again

4228 Attempting to connect now

12246 ****** End of session performance summary ******

12246 Total time connected = 0 seconds

12246 Reception maximum: 0 frames/sec, 0 bytes/sec

12246 Transmission maximum: 0 frames/sec, 0 bytes/sec

12246 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

12246 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Posted

#1 XP with FS and FSUIPC and WideServer

#2 Vista with WClient

Logs below.

...

2184 Trying to locate server: Need details from Server Broadcast

Have you changed the workgroup name in one or other of those PCs to make sure they are in the same workgroup, as pointed out early in the network configuring section in the User Guide? That's the part with a RED plea to at least read some of it! Vista and XP default to different workgroup names. The logs simply show that WideClient isn't receiving the broadcasts, and it certainly won't if the workgroup's are different.

An alternative, if you must have different workgroups, is to edit the INI to tell WideClient the name of the server and the protocol. This is also explained in the User Guide. Did you try ANY of the suggestions there at all?

Pete

Posted

Yes, the workgroups are the same name, and I have read the Guide to make sure all was set up properly, ala workgroup.

Posted

Yes, the workgroups are the same name, and I have read the Guide to make sure all was set up properly, ala workgroup.

Nevertheless, the client is not seeing any broadcasts, so you need to double check.

Did you yet try to add the ServerName and Protocol parameters as I suggested and as suggested in the documentation?

Pete

Posted

Yes, I re-read the Guide and yes the WorkGroups were assigned properly....so I thought:

#1: FLITESIM

#2 FLIGHTSIM...changed it!

Voila!!!! :idea:

Onward and Upward!!!

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.