Unfortunately the first time a topology update comes down, the userc.c file will get replaced with the standard one.
You shouldn't have to be doing this, though.
Quote:
| This new userc.C file has however a side effect. When connected to my internal LAN, I'm not able to access these 4 hosts if my SecureClient is started (icon in bottom right hand corner) but not connected. In order to access these 4 hosts, I either have to stop the two SecureClient services or connect with SecureClient as described at the beginning of this entry. |
This also should not be happening. There is a property in userc.c to send in the clear while in the encryption domain than can be set to true.
How do your default SecureClient policy rules look, the ones for "all users@any"? You should have those defined so you can access your internal subnets with "accept" rules in the outbound section.
Ray