Troubleshooting

troubleshooting

The following is a list of problems that can occur when setting up parallel processing and tips for solving them:

• Using an IP address instead of a hostname can be problematic if there are DNS problems.

• Using computers that are not part of the same Windows domain will probably not work.

• Appending the name of the domain to the hostname can cause problems (this depends on how network connections are defined). The master and slave must have the same network settings (they must be able to communicate with each other without requiring the domain name suffix). For example, if the name of the master (including the domain name suffix) is IMAGINE-PC5.siemens.com , and the slave is named TECHNB03.siemens.com and due to the network configuration these two machines can only communicate when the .siemens.com domain name suffix is appended, parallel processing will not work. TECHNB03 must be able to communicate with the master using only the short name (IMAGINE-PC5). The reason for this is that when the master and slave communicate, the master sends the job to the slave but also sends its own (short) hostname so that the slave can return its computed values. Note that this communication is not one-way, so you must pay attention to network settings on both machines. If the slave can only communicate with the master using its long name, it will not work.

• Network drives must be mapped automatically for every login (using the option Reconnect at logon ).

• Avoid saving .ame files directly at the root of a mapped drive (for example Y:\file_name.ame).

• Use the application NSlookup Host to check whether the system can find a host (a ping is not sufficient; sometimes it is possible to ping an IP address, but because the DNS cache has not been updated, putting an IP address as the host does not work if the system cannot resolve the IP address).