Am having a bit of difficulty getting a colleague’s workstation connecting to our company’s LAN based Zoo server via VPN. What makes this particularly perplexing is I have no issue accessing the Zoo license on my own workstation using the same connection method. He seems to mostly fail in step 4 of the zoo diagnostics tool, the zoo port check.
Even more confusing is occassionally he can get step 5 to say the connection to the zoo server was successful, while still not being able to get the license (step 4 seems to always fail).
Attached are the outputs from the zoo diagnostic checks, first from my successful attempt to connect, followed by two outputs from his diagnostic check, and a screenshot where the diagnostic tool says connection successfuly while Rhino fails to get the license.
We’re both running the same spec computer, windows 11.
Any help or insight into resolving this would be appreciated.
Correct me if I am wrong, but it looks like you are using a Rhino 7 SR24, which is good.
Rhino communicates with a LAN Zoo server via TCP Port 80 (HTTP), which is used by browsers to communicate with web servers. Because of this, it’s generally pretty easy to get Rhino to access a LAN Zoo, as most Windows firewalls have TCP Port 80 open for outgoing traffic.
Accessing LAN Zoo servers that are behind a VPN can be a little more work, as these application have their own security. But it sounds like this works, as you’re not having difficulty.
I guess I’d start by looking to see what other security apps your colleague’s workstation has. For example, Windows comes with a firewall, but so do other security suites.
Thanks - Theoretically he has the same antivirus as I do, but there may be a deeper security setting specifically related to his user account that is causing issues. This issue isn’t unique to Rhino either - having issues with FlexLM for other programs as well. Was just hoping you’ve might have come across this. It really may be port 80 interference - he mentions losing Outlook or Teams as well when connecting to the VPN. I’ll keep our IT guy on it and try to help him narrow down the issue.
We’ve managed to brute force through eventually. Not sure how or why - but as seen from the logs, occassionally Rhino would catch the license - eventually it did long enough to check it out from the server and now he’s good for the time being. If we get this resolved long-term, I’ll post the solution to help others.
