Hi all,
I’ve a problem with 3dsmax 22 and distribuited render with Vray in slave machines.
My first question that I’d like to ask you is if you had to run 3dsmax and set something after installed 3dsmax on slave machines.
I’m asking this because the slave machine aren’t authorized to surf on the web (IT security policy) and , without connection, I’m not able to run 3dsmax as was possible in the past for the first 30days after installation and I want to be sure that this is not the reason for this problem.
Recapping: when you set a DR system, you install 3dsmax, then Vray, you set the IP (or computer name) where find the license, start VraySpawner and that’s all. Correct?
But , if I’m not in trouble, I can set the slave to lokk to the workstation to get the license for render node and then, all the licenses are managed by the workstation that is connected correctly with the Chaos servers.
Yes. What kind of error message are you seeing? As Morne said, there may be trouble accessing the license server.
Yes, you can set the slaves to use the workstation’s license server. You can do that by changing the license server settings - here’s how wherein the Primary License Server IP you set the workstation’s IP. Another method that should work is to borrow licenses.
About how to change the license server settings ok, I known it and it’s set correctly.
About borrowing it’s quite interesting…but anyway, after few days I should re-borrow that licenses? Reading manual seems like this.
Hello, if you have one machine with Internet access you don’t need to borrow licenses, just have license server there and point the slaves to it. However it will be best if you submit a ticket in the link below so we could assist further, we’ll need the email associated with your licenses and other info that is not advisable to share on forums: https://support.chaos.com/hc/en-us/requests/new
Before opening a new ticket I’ll wait our IT dpt as before change my workstation from Win7 to Win10 everything runs correctly.
After this change not, so probably there is some internal policy that block network communications.
As I was suspecting, the change of the workstation and the security policy for W10 users was the reason.
After IT colleague modified something, everything working back.