Network troubleshooting

Network troubleshooting

General info

1. Basic trouble-shooting steps

  • Make sure firewalls do not interfere with the network communication by first running a job with firewalls disabled. Network uses by default the TCP and UDP port range of 45454- 45474. You can change this port range but it is very important in that case to change the range in the preferences of Manager/Monitor and all Nodes running on all computers. The port range can be changed from File>Preferences in the Manager/Monitor/Node.

  • Make sure the same version of Maxwell Render (and thus Network) is running on all your nodes. If an older version is running in one of the Nodes, the MXI merging process may fail. You can check the Manager log for any warnings of different versions running - it will also inform you which Node(s) is running a different version. The "Minimum Log Verbosity" setting in Manager preferences must be set to at least "Warnings" level to see both errors and warnings logged. You can also check the version number in the title window of the Manager/Monitor/nodes.

  • When rendering at high resolution and especially with Multilight turned on, each MXI file can grow to several gigabytes - ensure you have enough disc space available in the final output paths when Manager transfers the MXI files of each node there to begin the final merging process. The Manager will give you an error message in the log window if there is insufficient disc space.

  • Do not run several Managers on the network. If you want to check the jobs running from several computers, you can run several Monitors on the network and add jobs from each one.

2. Setting up the network for optimum performance

  • Make sure that all the machines in the network have the same version of Maxwell Render installed. Many transference problems in the network are caused by having different Maxwell Render versions all over the network. Updating to the last version on all machines will
    ensure the best communication between nodes.

  • Make sure that all the nodes have the same network card or cards with similar transfer capabilities. This will ensure a good transfer speed between all nodes. We recommend gigabit network.

  • Keep your network as homogeneous as possible. Similar computing powers and transference ratios will make the communication between all the machines much easier.

  • Remember to turn off your firewall if you are getting issues detecting nodes in the network.

  • DO NOT set the temp files folder for Manager/Nodes/Monitor to point to the same networked folder as this will have two very negative consequences:

You should always set local temp folders. Or you can leave the settings at default in which case the temp files will be saved in the systems temp folder. The temp folder location can be customized from File>Preferences (in Manager/Monitor and each Node).

3. Antivirus can interfere with Network rendering

We have had reports of Network behaving strangely, eventually a Node stops communicating with the Manager and seems frozen but it is in fact still rendering. The node cannot be stopped from the Monitor either. The solution was to prevent the Anti Virus application (Avast in this case but other AV software may also cause problems) from monitoring the activity of the Maxwell install folder and the temporary folder that mxnetwork uses for network rendering. You can find out where the temporary folder is on a particular node by going to the Node UI and choosing File>Open temp folder.

So please make sure in the AV software to exclude monitoring of the network temp folder and the Maxwell install folder.

4. The manager does not receive the previews or the mxi files from the nodes at the end of the render

If the manager cannot receive the preview files as well as the mxi files from the Nodes at the end of the render, most probably, the firewall is blocking the incoming connections on the computer running the Manager. You will have to create a rule in the Firewall so it allows the mxnetwork application to go through (you can find it in the Maxwell installation folder). If you are using the Windows Firewall, you can just tap the Windows key and start writing this: "Allow an app through Windows Firewall" and tap enter. In the window that will show up, you have to click on the "Change settings" button; this will enable the options below. Click on "Allow another app..." and look for mxnetwork.exe in the Maxwell installation folder.

 

 

OSX

4. File path problems when submitting a job

5. Launching a network render in a mixed (PC/ Mac) network fails

You should have all the files necessary for the render in a Windows shared folder on your PC, as Mac can handle Windows network paths automatically, but not vice versa.

6. Files location on OSX

All the files for a network render must be located in your user folder (or any of its subfolders) or in any secondary drive.