Author Topic: Team Render machine not reachable  (Read 1217 times)

2024-11-10, 14:53:30

petrue

  • Users
  • *
  • Posts: 3
    • View Profile
I have 5 machines on a TR network working fine, this week I've bought a new Mac mini Pro 4. The new machine is set up with the same version of C4D and Corona, I can render in Corona in the full version of C4D so I know it's working, when I put it on Team Render client I can see it on the team render machine list on my main Mac, I've verified it, but the machine icon is red and it won't connect properly.
The message I get is:
(Error) Transfer of job failed: 'Give me Render-Job' could not connect to 192.168.1.204:1
  Cause: Connect() to 192.168.1.204:1 failed
  Cause: Errno #65: No route to host
Is there something I need to change?
thanks!

2024-11-13, 09:09:14
Reply #1

HFPatzi

  • Active Users
  • **
  • Posts: 147
    • View Profile
Hey petrue,

there's one thing that could cause this: Are you sure you are running on port 1? Unless you canged it, it should say something like: "192.168.1.204:5401"

Greetings,
Moritz

2024-12-02, 09:51:15
Reply #2

petrue

  • Users
  • *
  • Posts: 3
    • View Profile
hi Moritz, it says I am on port :5401, I reinstalled everything back to cinema v2024.1.0 and it worked until I shut the machine down, now it won't connect again. I think it's time to switch to Redshift

2024-12-02, 12:28:02
Reply #3

Nejc Kilar

  • Corona Team
  • Active Users
  • ****
  • Posts: 1313
    • View Profile
    • My personal website
hi Moritz, it says I am on port :5401, I reinstalled everything back to cinema v2024.1.0 and it worked until I shut the machine down, now it won't connect again. I think it's time to switch to Redshift

Not trying to be that guy but that sounds like a general Team Rendering issue that is probably related to your network setup / firewall. Given that you get the "red" icon there you'll have the same issue with Redshift :)

One thing that has tripped me up in the past was surprisingly the actual C4D versions themselves. IIRC I had something 2024.1.0 installed on most of my nodes but some apparently got updated with like 2024.1.02 which then prevented TR from working. Of course the error I was getting didn't mention that :)
Nejc Kilar | chaos-corona.com
Educational Content Creator | contact us