Been getting these messages every couple of days now for awhile, then maybe tomorrow it will find the license again. No work interruption, but I don’t understand why this is happening.
That looks like a local DNS problem.
If you open a Windows CMD window and run:
ping cloudzoo.rhino3d.com
do you get a response from IP 13.65.212.252?
Pinging waws-prod-sn1-149.southcentralus.cloudapp.azure.com [13.65.212.252] with 32 bytes of data:
Reply from 13.65.212.252: bytes=32 time=120ms TTL=105
Reply from 13.65.212.252: bytes=32 time=120ms TTL=105
Reply from 13.65.212.252: bytes=32 time=120ms TTL=105
Reply from 13.65.212.252: bytes=32 time=120ms TTL=105
Ping statistics for 13.65.212.252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 120ms, Average = 120ms
C:\Windows\System32>
That looks exactly like mine.
I you try to browse to:
https://cloudzoo.rhino3d.com/
do you see:
For CloudZoo licensing to work, your firewall must allow:
https://wiki.mcneel.com/rhino/install/wizard/start/windows/6/commercial/czpersonal/firewall
Yes, I see that page exactly.
I don’t have a firewall (except for Windows Defender). All other internet services are up and running - they virtually always are, I have an extremely reliable ISP.
I overheard a couple weeks ago where a guy had turned on some Windows file security tool that effectively locked the folder where these files live:
C:\Users[your login]\AppData\Roaming\McNeel\Rhinoceros\6.0\License Manager\Licenses
I think the setting was here:
Windows file system access and privacy - Microsoft Support
Mine looks like this:
Yeah, but that would be permanent and I would find out when Rhino would no longer run. This is temporary and tomorrow it will probably fix itself. As there is no RefreshLicense command to try and test, I have to close Rhino and re-open it to see if it managed to communicate. Nope, still out.
Log out of my Rhino account and log back in again, restart Rhino. Nope, still out.
Restart Windows maybe?
Yep and nope, didn’t help.
I have brought @will in on this issue.
He will work his magic and maybe we’ll figure this out.
Thank for your patience.
License re-acquired this morning… This is exactly what’s been happening.
Fortunately as I have Rhino open on this machine nearly every day, I always have more or less the maximum grace period still remaining, so I have never been stopped from working.
The way it’s supposed to work is if the 20 day license lease is 10% or more used, it is supposed to check and refresh the local lease. That would be every other day. Your Notifications Panel records the event.
Maybe @will can have a look at the logs on our end and see if anything is happening here.
Hi @Helvetosaur,
Have a Windows cmd window open when you start up Rhino and if you get the error message run
C:\>tracert 13.65.212.252
This will display each of the router hops your communication uses to get from your PC to the licence server. If it times out on a hop too many times it will give up. The trace will show you where. On a one-off random test I saw a lot of time outs on the final leg but did eventually get through. If you get repeatable routing failures then it indicates a potential network bottleneck or component fault.
HTH
Jeremy
Traceroute is showing repeated timeouts for the final hop to the licence server which indicate high levels of traffic and/or possible component fault. Depending on how the licence traffic is configured that may be enough to stop your refresh. Rebooting your pc isn’t going to help in that scenario, I’m afraid.
But I’m following a different route, at a different time. To see if this could be the root cause (no pun intended) of your problem you need to run traceroute from your pc at the time you are having the problem.
Regards
Jeremy
I just picked up a license while experiencing a similar level of timeouts, so we can probably rule network issues out for now. Time to scratch head…
Day three…
1 Like