Yo,
Sorry for late answer.

Here are the information from server 1 and 2 at least. Server 3 and 4 ports i am not sure yet. But Servers 2-4 will go off soon anyway so we could at least fix the problem for server 1.
This is in my LFSLapper ''LFSServers.cfg'' :
# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|81.207.36.235|29999|./default|default_1.ini|autowork
insim port: 29999
normal port : 63392
For Server 2:
(Copy of LFSServers.cfg)
# Configuration of LFSServer to be Managed with LFSLapper
# One line per server
# Remote port is the port used to manage LFSLapper remotely, future extension
# One remote port per LFSLapper on one machine, autoStart is optionnal
#Unique ID|GroupId|Ip|Port|WorkDir|IniFile|autowork
timeOutScript=2000;
remotePort=3001;
DEF1|gr1|85.17.183.199|29999|./default|default_1.ini|autowork
Insim port : 29999
normal port : 63392
3 and 4 not needed

I can fix it for them same as for those 2 if needed


Hope we get the problem fixed

See you
-jsrk-