Recovering from one-way socket setting?

[Neale]

I had a situation where a client user on OS-X had to disable two-way sockets: http://forum.servoy.com/viewtopic.php?t=3478 Subsequently this user upgraded to ADSL with the new router doing NAT, so effectively they are "behind a firewall" (for suitably liberal definitions of "firewall"). For this, they (obviously) require two-way sockets enabled.

This is where our troubles started: with two-way sockets set false and the client machine "behind a firewall" we couldn't start Servoy client. Attempts to do so resulted in an error dialog complaining about licences; acknowledging or dismissing this dialog resulted in Servoy Client terminating.

What we needed to be able to do was to change the preferences - difficult when we couldn't start Client. We eventually worked around this by editing ~/.servoy/servoy_client.properties

Is there some less inconvenient way of recovering from this?

Thanks,
Neale.

[ROCLASI]

The place to set those settings is in the Servoy Server admin pages or in the Developer preferences (when run on that machine).
The admin pages are accessible through http://yourserverip:8080/servoy-admin/
When a admin password is set inside developer (on that server) then you get a login dialog first.

The client doesn't have such settings since this is a server setting.

[ROCLASI]

Reading your post again I see you are talking about not being able to use the (already available) clients on the users machines because of the local settings inside servoy client.

I guess the only solution is to download the client again from the webstart page on the server (http://yourserverip:8080). This will take the current server settings.