In my case, a) the VPN client and Network Connect Service have been started up with the same start parameters (they are not even configured with %HOME). The console log on all things have the same settings, and the -v option is set to always. On the client side, the -v option was set to overwrite.
If you are more adventurous, you can instead try to patch the Juniper Network Connect Service executable to make it assume that there are no routes to monitor. You may require a tool similar to the IDA Pro Disassembler to assist you in patching the executable.
There are some route table changes from version 6.4 onwards, which makes the routing modifications a bit more more difficult (Juniper eliminates the directly connected routes). You may either opt to patch the Network Connect Service version 6.4 or 6.5 or you can simply downgrade the Network Connect Service to version 6.3 instead. Downgrading to version 6.3 will get you back the route modification flexibility.
The network password to login to the control software is made up of two characters, e.g. \"-H\". You need the same characters to set up the network password for the Juniper Network Connect admin password. 7211a4ac4a