Firewall issue - v5 client and Windows XP

[chrishemingway]

I don't know if anyone has had the same problem but we have found that to install the client (dating back to v3!) you have to install the full local version first, run it so that Windows Firewall prompts you to unblock the various modules, then set the client settings and run the client.

If you just try and install the client alone, it seems Windows Firewall silently blocks all communication to the server.

Chris

[Martinadu]

This is not a known issue. It also sounds odd, as that is not the way it is designed to work.
I can understand that the first time you install the full client which has all the various modules,
you need to unblock. The thin client will only need to talk to the Server PC as we know.
The ports need to be unblocked there at the server PC for sure.

However rather that installing the full standalone client software first, you may want to allow
communication to the file OLFClient.exe in your firewall.

[chrishemingway]

If only the client is installed, when starting it it brings up the settings screen (for choosing a server IP address) - even if the firewall has been updated to allow communication with OLFclient.exe

On our systems, the client installation doesn't prompt for the firewall unblocks which you get with the full installation, but it seems to require the latter. Maybe it's unique to our systems?!

Chris

[mcowell]

when we upgraded from v4 to v5, we used the following batch file to setup the firewall etc

Code: Select all

netsh firewall add portopening TCP 11000 EPOline5_port
netsh firewall add allowedprogram "C:\Program Files\EPO_OLF5-TC\OLFClient.exe" EPOline5_app ENABLE
netsh firewall add allowedprogram "C:\Program Files\EPO_OLF5-TC\cl_cm.exe" "eOLF2 Client for EPO servers" ENABLE
CACLS "C:\Program Files\EPO_OLF5-TC\OLFClient.ini" /E /G <AD group name>:C

the last line is to add write permissions to the ini file for a group of users in our AD structure who might use that computer.