Quote:
Originally Posted by RayPesek  That's not accurate. I routinely use SecureClient from our plant locations with Office Mode to pick up a known Office Mode address so I can connect to the firewall to manage it. The plant IP ranges are inside the encryption domain. |
This is something that works for me to if I'm located inside my encryption domain, but my SecureClient connects to the firewalls internal (LAN) interface and not the external one.
I have managed to "cobble" together a userc.C file with only 4 host addresses in it, and with the limited testing I have managed to do, this seems to work. This way I have at least reduced the chance of an address clash by several 100%.
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.
So, in general, I guess my problem is more or less resolved. I will only encounter a problem if I'm assigned one of these four addresses, and this would be really bad luck.