DR will not work with high resolution

[glorybound]

i d do a typical debug in this case...

1. turn off all the firewalls
2. run the slaves manually not as a service
3. try the 2012.1 backburner if you havent already
4. check the vray licences setup on the slaves machines (i write computer names there)

firewall is off, but it is strange that when I ran BB, one of the slaves showed a blocked dialog (I unblocked). I ran a small job using backburner, and it ran fine. Everything is looking good, so far.

[PIXELBOX_SRO]

it must have been the wonderfull Windows update that messed aroud with your FW settings.
We update only from time to time....and have the automatic update function turned off....onl yfor this particular reason
glad it works!

[glorybound]

I took everyone's suggestions, but I'm still having issues. My VRaylog is saying:

warning: DR request received from 192.168.8.101, but currently busy with 0.0.0.0

[PIXELBOX_SRO]

have you tried restarting the router? and switch?

[glorybound]

I have unplugged it, and plugged it back in. I did this early on in my troubleshooting.

[glorybound]

I just spent the last 1 1/2 days re-installing a ton of stuff. I made sure all machines are running the same BB, VRay, and MAX Updates. I actually removed, and re-installed, just to make sure. I totally torn down one machine, and reformatted. Everything seems to be running well now. No errors!!!

[PIXELBOX_SRO]

cool you got it working...
now make sure you save your wokring confing with windows restore
muste have been windows update what else could it be...

[glorybound]

it was a nightmare. It could have been an Autodesk update. I downloaded all the updates, 4 in all, and it was weird. When I ran update 1, it said 3, and update 2 said 4... They didn't have any naming convention for the executable files. It was very sloppy, and makes you wonder what the code looks like. Anyway... I'll create a restore point.

cool you got it working...
now make sure you save your wokring confing with windows restore
muste have been windows update what else could it be...