Two Licenses on two systems: Trouble

[FSVisions]

Today I bought a second license for FSUIPC and WideFS. My intention was to use this license on a second system with a second FSX installation, not to connect two clients to one server.
Both systems ar on the same Wifi network. All licenses do have the same name and e-mail used for registration. Of course they have different keys.

Installation went well but when starting wideFS, it connects to one server. This means I have 2 clients connected to one server, not being able to connect each client to a different server. Both servers will take the two connections, depending on which one is taking the first client connecting. The second one will connect to this server too. So one server has two clients and one servers doesn't have a client at all.

I went through this forum using the search function but could no find a topic which is explaining how to solve this. Is someone able to help?

Thanks in advantage.

 

Tino Broekstra
www.fsvisions.nl

[Pete Dowson]

Installation went well but when starting wideFS, it connects to one server. This means I have 2 clients connected to one server, not being able to connect each client to a different server. Both servers will take the two connections, depending on which one is taking the first client connecting. The second one will connect to this server too. So one server has two clients and one servers doesn't have a client at all.

 

Didn't you read any of the WideFS user guide? The part on configuring your network, with a RED BOLD message asking that you be sure to read some of it at least?

 

All you need to do is provide the Server PC name or its IP address to Wideclient, in its INI file.

 

I went through this forum using the search function but could no find a topic which is explaining how to solve this.

 

You never even thought of looking at the documentation? :-(

 

Regards

Pete

[FSVisions]

Thanks for your clear answer Pete,

As a long time user I was assuming I was able to install FSUIPC and WideFS onto my second setup, without the need to read the manual again. I did it once before so a second time should be a piece of cake.

 

Unfortunate it wasn't.

I will read the manual again and won't border the forum again with questions. 

 

Thanks!

[Pete Dowson]

As a long time user I was assuming I was able to install FSUIPC and WideFS onto my second setup, without the need to read the manual again. I did it once before so a second time should be a piece of cake.

 

Yes, but the automatic linking of the Client to the Server is based on seeing something to connect to. It seems pretty obvious, doesn't it, that if you need to direct a specific client to a specific server some additional action is needed. how else can it know which of multiple servers is the one you want it to deal with?

 

That's all this is about.

 

 

I will read the manual again and won't border the forum again with questions. 

 

No, don't be like that. I'm sorry if I've put you off answering questions -- it was just the thought of you searching all the way through the Forum for a solution rather than look at the manual seemed, er, a bit odd. That was all. And in this case you don't actually have to read all of the manual, only look up the bit about configuring the network I mentioned. It will tell you the format of the parameter you need in each WideClient.INI file.

 

I always try to answer questions properly, even if it is by reference to the manuals. I can't help emphasising documentation --  it is, for me, the worst part of developing software and so, having done it, it is a little frustrating when folks don't use it! ;-)

 

Regards

Pete

[FSVisions]

Thanks for your reply Pete,

I went through the manual now, now my Wide Client ini is showing this:

[Config]

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

ServerIPAddr=192.168.2.5

Protocol=TCP

 

Setup system 2: SIPKE-PC with IP address 192.168.2.11

Tried both name and IP number.

[Config]

Port=8002

Window=75,81,601,494

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 

ServerIPAddr=192.168.2.11

Protocol=TCP

 

When trying to connect my client to the server Tino-FSPC, it keeps connecting to Sipke-PC. So however I am pointing the client to 192.168.2.5, it is still connecting to 192.168.2.11.

 

Never mind, got it working!
I deleted the client name from the FSUIPC ini file and started FSX again. Now it is connecting to the correct client. 
 

Edited May 8, 2014 by FSVisions

[Pete Dowson]

Never mind, got it working!

 

 

Well, I'm pleased for you, but i must clarify some points here, mainly for the benefit of others who may read this thread.

 

First of all there's no way a WideClient can connect to a different server if the ServerIPAddr or ServerName parameters and a Protocol parameter are correctly provided and actually seen in the INI file at the time WideClient is started. This is because it then ignores the Server ID broadcasts, the little once-per-second messages sent to all PCs in the workgroup which identify the Server name, IP address and preferred protocol.

 

Second, the only use of the Client name list in the FSUIPC INI file is to enable button inputs to the Server from joystick or other devices on clients to be uniquely identified for assignment purposes. There is no other use for them, and the Server only knows about them when a client succeeds in connecting and then sending its Name. The names are NEVER used by the Server to contact clients. There's just no way the protocol allows server-initiated connections.

 

The client list in my own INI files on the assorted PCs I have are very long indeed, actually featuring PCs I no longer have or ones which rarely connect. But every client can always be directed to a specific server, should this be what I want.

 

Regards

Pete