Jump to content
The simFlight Network Forums

WideClient does´nt connect - Connect refused


 Share

Recommended Posts

Hi Pete,

1. sorry for my English (i+m from Austria and my English is´nt perfekt at all)

2. I have 2 PC

Server=psbrm

Client=travel-ps

Installation on Server:

FS2004

FSUIPC V 3.5.0.0 and registered (although there is shown V 3.40, when you open it in the FS Menu)

WideServer.dll V 6.5.0.0 and registered

WideServer.Ini

Installation on Client

WideClient.exe V 6.5.0.0

WideClient.Ini

You will see the logfile error

Error on client pre-Connection Select() [Error=10061] Connection refused

I hope you can help me

Thanks

Peter

WideFs Zip.zip

Link to comment
Share on other sites

FSUIPC V 3.5.0.0 and registered (although there is shown V 3.40, when you open it in the FS Menu)

If it says it is 3.40 it is 3.40. Please update to 3.50 (or wait till tomorrow (Friday) when 3.51 will be released).

I cannot support version 3.40. You must update!

I would also need to see the WideServer Log, but at first glance "connection refused" is most likely to be due to a firewall.

Pete

Link to comment
Share on other sites

1. the FSUIPC.dll is V3.5 (see atteched file WideFS 2)

2. see the screenshot, whre it shows V 3.4.0 (see atteched file WideFS 3 in the next mail)

The FSUIPC you supplied in your ZIP is certainly version 3.50, but the version you have installed in FS is most certainly 3.40!

You either have two FS installations and you are looking in the wrong one, or you are not following the very clear installation instructions for FS modules and placing them in the FS Modules folder!

3. Firewalls on both PC´s are inaktive

Well, you must look to find what is blocking WideClient access to your server then.

4. there is no WideServer logfile

If there is no WideServer LOG file in the FS modules folder, then you have NOT installed WideServer -- that would certainly prevent WideClient connecting!

PLEASE PLEASE READ the installation instructions for my programs. They are very short. They predominantly consist of "copy the DLL into the FS Modules folder". You have evidently not done this simple one-step procedure!

Regards,

Pete

Link to comment
Share on other sites

Hi Pete,

I´m really sorry - you´re absolutly right.

I did´nt recogognize that "module" is a folder - I just thought module means folder - so I just did the dll´s in the wrong folder.

NOW IT WORKS

Thanks a lot - and sorry you wasted your time with my "English problems"

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.