I am running a local mpi job like this:
mpiexec.exe -n 2 process.exe
When I start my Juniper VPN client, the mpi job still runs fine, but if I close my VPN connection the mpi job no longer works. The mpiexec.exe still spawns an instance of smpd.exe, but the two processes are no longer able to talk to each other.
It seems to get upset about the changing around of network adapters and IP addresses with the start and stop of the VPN client (but only the Juniper client - I have never seen this happen with the Cisco AnyConnect VPN client that I used to use).
Anyone ever seen a similar problem with interaction between ms-mpi and a VPN client? Any insight into how mpiexec.exe and smpd.exe interact with the tcp/ip stack and network adapters on a system, or whether there are any command-line switches that
might be used as a workaround?