Page Comparison

...

Alternatively, you have two options to make sure all nodes find the textures:

1. You can keep your textures in a shared folder and when building your scene, load the textures from this folder starting from Network in the File Browser so that the texture paths are in UNC format.
   
   For example, your texture folder may be c:/mytextures, which is shared. Your computer name is “renderbox1” which is part of the Workgroup named “farm”. Browse from My Network Places> Microsoft Windows Network> farm> renderbox1> my textures. The path for the texture will then be

...

1. \\renderbox1\mytextures\texture.jpg
   
   You can also type directly in the File name input of the File Browser:

...

1. \\renderbox
   and your mytextures folder will appear in the list of shared folders. In this case it is not necessary to also move your textures to the same shared folder as the MXS.
   
   
2. Or you can keep your textures in a shared folder and when adding the job through the Add Job Wizard, you can specify this shared folder in the “Textures” dialog.

Using a mapped network drive

...

Now, you can mount the shared resource \\MyServer\Share1 in the folder /MyServer/Share1 (pay attention to the particular back and forward slashes) using this command as root:

mount \-t cifs //ip-of-the-server-MyServer/Share1 /MyServer/Share1 \-ousername=an-authorized-user,password=the-appropriate-password

If you have smbfs module loaded in your kernel, then you can do:

mount \-t smbfs //Myserver/Share1 /Myserver/Share1

For example: if the IP of MyServer was 10.10.10.1, then:

mount \-t cifs //10.10.10.1/Share1 /MyServer/Share1

...