TurboFloat - Connection to server failed

Hi!

I'm currently trying to integrate TurboFloat into our app. Unfortunately I encountered some issues with the connection to the TurboFloat server. When I run the TF-Server on my localhost everything works just fine, even if I'm passing any arbitrary IP/Port other than 127.0.0.1 / 13 to TF_SaveServer().

Example:hr = TF_SaveServer(tfHandle, _T("123.123.123.123"), 4848, TF_USER);Works just fine if the TF-Server runs on localhost. Is it meant to be like that?

However, if I'm running the TF-Server on a different computer, TF_SaveServer() returns TF_OK, but TF_RequestLease() returns code 4 - "Connection to the TurboFloat server failed" (of course I used the correct IP/Port in this case). Any ideas?

One more question concerning the xml-config file: since the TF-Server is running on the customer's computer, the customer himself can actually change the "lease length" and the "isgenuine" settings. Doesn't that mean that the customer could use our app for 90+14 more days (worst case) after the license expired?

I hope you can bring some light into these topics.

Many thanks in advance!

Dan

Hey Dan,

Example:hr = TF_SaveServer(tfHandle, _T("123.123.123.123"), 4848, TF_USER);Works just fine if the TF-Server runs on localhost. Is it meant to be like that?

No. Make sure the TF_SaveServer() actually saves the server and not just ignores whatever you input (and thus keeping whatever previous server address/port you input). Look at the return code for the function.

However, if I'm running the TF-Server on a different computer, TF_SaveServer() returns TF_OK, but TF_RequestLease() returns code 4 - "Connection to the TurboFloat server failed" (of course I used the correct IP/Port in this case). Any ideas?

Did you install the TurboFloat Server using the -i commandline switch or are you running it from commandline (-x)?

If you installed it then everything is setup as far as Windows Firewall is concerned (allowing outgoing connections, etc.). However, that doesn't take into account (1) other firewalls on the computer or between the 2 computers (2) firewalls on the "client machine" (3) firewalls / proxies on the routers / switches and (4) general intranet misconfiguration.

Doesn't that mean that the customer could use our app for 90+14 more days (worst case) after the license expired?

No. There are max values: http://wyday.com/limelm/help/turbofloat-server/#config-isgenuine

And the lease length is just how often the app contacts the TurboFloat Server.