Intel MPI 4 - Port Issues on secondary smpd process

[mcapogreco]

Hi,

I have got the intel mpi working when I have the firewalls turned off, however, when I turn on firewalls I have an issue;

I have unblocked port 8678 on both machines and the request is received on the second machine, however another smpd process is started which uses a different port each time and it is this port this is being block.

Does anyone know how to keep this fixed with a setting or something. Below is the debug information:

h:\\>smpd -port 8678 -d 3
created a set for the listener: 1688
smpd listening on port 8678
Unable to get the data for the key 'no_dynamic_hosts'
sock_waiting for the next event.
SOCK_OP_ACCEPT
authenticating new connection
posting a write of the challenge string: 3.1 848
sock_waiting for the next event.
SOCK_OP_WRITE
wrote challenge string: '3.1 848'
sock_waiting for the next event.
SOCK_OP_READ event.error = 0, result = 0, context->type=20
read challenge response: '5f27491e29ec9dfa16601a95eefca4e2'
sock_waiting for the next event.
SOCK_OP_WRITE
wrote connect result: 'SUCCESS'
sock_waiting for the next event.
SOCK_OP_READ event.error = 0, result = 0, context->type=20
read session request: 'process'
sock_waiting for the next event.
SOCK_OP_WRITE
wrote no cred request: 'nocredentials'
starting command: "C:\\Program Files\\Intel\\MPI\\4.0.0.012\\ia32\\bin\\smpd.exe" -d 3
-mgr -pipe smpd_temporary_pipe
CreateProcess
smpd reading the port string from the manager
smpd sending the account to the manager
smpd sending the password to the manager
smpd sending the smpd passphrase to the manager
closing the pipe to the manager
smpd writing reconnect request: port 1277
sock_waiting for the next event.
SOCK_OP_WRITE
wrote reconnect request: '1277'
sock_waiting for the next event.
SOCK_OP_CLOSE
op_close received - SMPD_CLOSING state.
Unaffiliated undetermined context closing.
freeing undetermined context.
sock_waiting for the next event.

Thanks

Mark

[mcapogreco]

I have worked out the above problem for anyone interesteded.

BAsically all you need to do is add the smpd.exe on each host machine to the program exceptions in the windows firewall.

[Dmitry_K_Intel2]

Thanks, Mark, for sharing with us.

--Dmitry