Author Topic: DR- license server: config files  (Read 3000 times)

2016-07-21, 17:17:22

mraw

  • Active Users
  • **
  • Posts: 162
    • View Profile
Guys, sorry to bother you with this. But can maybe someone help me out with this? I already have two render nodes(I'm on Corona1.3 ) and they work fine generally.
I remember I had a tough time and had to do some research to get them reading the license information. It was something about placing a text-file containing my license information?

I'm setting up a new render node and because I'm an old fart I forgot how to do it and I can't find it anymore. The DR-server says something about creating a new config-file and it is not found by the master when I press search 'LAN'.

Any help greatly appreciated!!! thanks.

2016-07-21, 17:24:42
Reply #1

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5465
    • View Profile
Here's the post that describes it, should be all you need!

https://coronarenderer.freshdesk.com/support/solutions/articles/5000618553-corona-licensing-server

Holler if anything isn't clear.

PS I know the location of that post as I can never remember how to do it myself, since it is something I need to set up rarely :)
Tom Grimes | chaos-corona.com
Product Manager | contact us

2016-07-21, 17:44:32
Reply #2

mraw

  • Active Users
  • **
  • Posts: 162
    • View Profile
Thanks for the quick reply, TomG.
thanks to your link I remembered how I did it for the other nodes. The txt.file was placed in localuser/appdata/blah and I tried to mimic this for the new node.
Dr started fine like:
2016-07-21/17:33:50   DR server started
2016-07-21/17:33:50   Starting UDP socket, local hostname: Xeon-1
2016-07-21/17:33:50   Running Corona DrServer build Nov  3 2015 on ports UDP19666, TCP19668, loopback TCP19667

this looks just like the (working) node
2016-07-21/10:56:22   DR server started
2016-07-21/10:56:22   Starting UDP socket, local hostname: I-7
2016-07-21/10:56:22   Running Corona DrServer build Nov  3 2015 on ports UDP19666, TCP19668, loopback TCP19667

But Xeon-1 still can't be found.
One thing: In the working node's directory there are other files like licensing.log and a token. I remember reading or doing something about a token.

any ideas? thanks

2016-07-21, 18:26:37
Reply #3

mraw

  • Active Users
  • **
  • Posts: 162
    • View Profile
Solved.
After rebooting it worked. I'm using windows for over 20 years now- when I will learn that you have to reboot first each and every time something isn't working as expected?
:)
thanks, TomG.

2016-07-21, 18:30:09
Reply #4

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5465
    • View Profile
Glad you got it working! And most welcome!
Tom Grimes | chaos-corona.com
Product Manager | contact us

2016-07-21, 18:54:16
Reply #5

mraw

  • Active Users
  • **
  • Posts: 162
    • View Profile
..and when I will learn not to cheer to soon?
I got the client rendering, but the drive mapping isn't working.
I will open another thread.
cheers