[numerobis]

[08/May/2014 16:35:12] Trying to detect license through broadcasting.
[08/May/2014 16:35:12] ERROR: RLM returned error : No Error
[08/May/2014 16:35:12] ERROR: TCP server can not listen port: 45459
[08/May/2014 16:35:12] Connecting to render process: Binding to port: 45463
[08/May/2014 16:35:12] Maxwell node 3.0.1.0 successfully initialized.

Error: No Error ... Error: TCP server can not listen ... Connecting to render process ... Maxwell node 3.0.1.0 successfully initialized

What?!?

I'm getting this error message on one node - It doesn't show up in the manager and it does not start the render.
I never saw this before. No problems so far with network rendering (besides the delayed starting of one machine!)
Nothing has changed since the last rendering. (3.0.1, Win7x64sp1)

[polynurb]

(besides the delayed starting of one machine!)

in one of my nodes, i accidently entered the hostname and not the IP of the license server when licensing maxwell.

that takes about 10-15 seconds longer for that machine to check out the license.

if i try to re-license with the IP, the licensing process produces errors/does not succeed. so i just left it, since it does work fine.

[numerobis]

interesting... i have only names and no IP. Maybe i should try with IP?

[numerobis]

Ok, today i tried to connect the nodes in a different order and again it was the last node that got no license... something must have been changed with the last update to v3.0.1, because it worked before without any problems!

I need to know how to fix this issue, because i need all nodes for a job urgently!


1 Workstation + 10 nodes all Win7 X64 sp1

[numerobis]

ok... it's working now. I deinstalled the firewall on the last machine and now it's getting the licence.

But why?!? I have the same config (firewall+maxwell) on all nodes, only the last one that tries to connect (not always the same) is failing.

[Mihai]

It may be your firewall has a limit on connections and how often they occur before it thinks it's an attack and blocks one of the nodes. Also keep in mind that it may re-block Maxwell after an update because it deems the application has changed and so it should ask you if you accept the modified application to connect.

[numerobis]

i use Comodo Internet Security on all nodes. It looks like the problem came with the last update. I think i have not updated all of them - i have to check this, when my current job is done.
Anyway... after i disabled all of the comodo services on that nodes (now two nodes) everything worked fine again. There where two services running in the background even if i closed CIS.
I have to look why these are not controlled by the application rules... (i already re-registered maxwell there and never had any connection problems before)

But thanks Mihai!