DR connection problem

[bardo]

Dear Chaos,
i've downloaded your last nightly build of Vray Standalone 3 SDK (vraystd_adv_32501_x64_vc101_hwlic_25805) and the last Blender for Vray (vrayblender3-2.74-60092-dfbb876-fd9aca6-x86_64-windows).

Locally it works but DR doesn't.
On the slave I've installed just the Vray for Standalone. Then I created a link to vray.exe with the -server and -portnumber options.
I've started the vray.exe on the slave and I can see it in the slave list of the master so the license is ok.

I've tried to launch a DR render (the startup scene) with the option to use only the slave but it doesn't start and the master says me:

[2015/May/19|15:46:00] warning: Could not connect to host 192.168.96.65:20207: Connection timeout
[2015/May/19|15:46:00] warning: Could not use any of the selected (1) hosts for distributed rendering!
[2015/May/19|15:46:00] warning: Local machine is not used for distributed rendering and no slaves can join!

First of all a question: why if I set 20204 port both in Blender and in the slave, it seems that vray is still searching for a slave on the port 20207?

I tried to change the port to 20207 both in Blender and in the slave but with no luck, it still searching a slave without found it.

Where am I wrong?

Thanks in advance

[bdancer]

1. Does ping 192.168.96.65 works fine?
2. Try checking the firewall settings on both master and slave, may be it's blocking the connection.

[bardo]

1. Pinging works fine.
2. Could you write me the names of the processes and the port numbers involved in the DR system? In this way I can be precise with our IT guys to check the firewall settings.

Until some months ago (the last time I've tested Blender4Vray) the DR works fine. Is something changed in the last builds?

Thanks in advance

[bdancer]

2. DR node is V-Ray Standalone actually, so the process is vray.exe (.bin on linux / os x). Port number could be specified with -portNumber=<number>.

Is something changed in the last builds?

No.

Also make sure V-Ray versions are the same on master / slave.

[bardo]

So, if the process is the same, it should works. I'll check with our IT guys.

About the vray versions I've checked the console and they're the same.

[2015/May/28|09:43:48] V-Ray Standalone, version 3.25.01 for x64
[2015/May/28|09:43:48] Copyright (C) 2000-2015 Chaos Group Ltd. All rights reserved.
[2015/May/28|09:43:48] Use -credits option for additional third-party copyright notices.
[2015/May/28|09:43:48]
[2015/May/28|09:43:48] Build 25805 from May 19 2015, 10:55:19

[bardo]

Just to inform that our IT guys open the traffic to/from and now it works.

[bdancer]

Great, glad that it worked =)

[VOYT]

Hello, I also have a problem:
I want to test DR rendering based on "Shared Directory" (not V-Ray Transfer), and under windows I input:
Shared Directory: E:\DIST\ .... (the subdirectory "textures" and all 8 .vrscene files are created successfully during render start)
Share Name: DIST ....(I also tried: /dist //dist \dist \\dist and options like //computeranme/dist )
I allways end up with missing buckets(no lightmaps and textures are transferred to nodes)
When I set up V-Ray Transfer - it runs fine
What do I do wrong? (Im on engine 2.55.01 nightly version)

[bdancer]

Have you shared E:\DIST\ this path? What is this share name? Enter this name under "Share Name".

[VOYT]

Thanks Andrey,
Yes, nodes see this directory and have full access rights.. You can see on the screenshots the way I'm trying to configure it now..

[bdancer]

VOYT, then use V-Ray Transfer =) I was actually planning to remove shared directory option...

[VOYT]

..OK... but please note there is some exception happening even with "VT" - this is when pre-rendered lightmaps are to be transferred to nodes and the lightmaps are to be merged (e.g. "interpolation frames" set=2). - After successful start of such render the nodes are loosing "the rhythm" (it takes about 5 frames) only one or two of them keep rendering till the end - the rest stalls (please see the screenshot attached)
Thanks.

[VOYT]

...the solution is to copy lightmaps to every node manually
Does it work the same in V-Ray 3.x?