Is it possible to change the port of the Zoo license server? Port 80 is really a bad choice for a license server.
It is currently not possible to change the port number used by Zoo 5.0.
TCP Port 80 was specifically chosen because it is open on most all workstations and firewalls, and supported by most VPN products. Thus, it make is very easy to deploy Rhino configured as a network node.
Why do you think using TCP Port 80 is a bad idea?
As you know, there are port numbers wich are especially for certain services, like SMTP(25), POP(110), HTTP(80), HTTPS(443), ...
This ports are so called "well known ports" wich are defined by the Internet Assigned Numbers Authority. The service you provide with the license server does not really match the well known behavior of port 80, though you might use the htt-protokoll for transmission.
So in our network environment this results in many difficulties because of the behavior of our firewalls, proxys, anti-virus scanner, routers and servers. Further more, i MUST choose another port for the "real HTTP".
It would be great (i think for all big companys) if it is possible to change the port to another one.
Yes, I know the standard TCP/IP ports well - thanks for providing the review.
If it helps you, just think of the Zoo as a specialized HTTP server, which it is.
The Zoo will run on any Windows computer. So if your server has a TCP Port 80 conflict, you can just move the Zoo to some other system.
We will consider allowing for the changing of the port in a future release. But doing so will certainly cause administrators much more work.
Sorry Dale, but i am a administrator and for me it's pretty much work do administrate now the zoo server. We have hundreds of servers and i'm not willing to add a new one, just for zoo. So i have to change my HTTP Server to another port wich results in a lot of configuration and administration.
Why exactly is it more work if i can (not must!!) change the zoo-port? That makes no sense to me. If i can change it i have more opinions in big network.
But i would appreciate if i can change the port in a future release.
Thank you for your efforts.
On your hundreds of servers, are all of them running an HTTP service or some service that is using TCP Port 80?
We have a number of larger customers who are already successfully using Zoo 5.0 in their enviroments, are are pleased we are using Port 80, as it as has make installation and configuration easy for them.
In our case the availabiliy of servers wasn't so much the problem. (Although we actually had to disable some services to get port 80 freed. Many default Windows Server components tend to use the default web site...)
A bigger problem is the availability of public WAN IP addresses. They are very limited and, yes, we were all using them for http communications. Any other port would have been fine, but port 80 is just required for public access...
I'm a single rhino user and also a xampp and a dreamweaver user, and so on.
I've only one machine and sometimes I REALLY need to test things in localhost with apache. Changing the default apache port (wich is also #80)is not so easy in order to run the whole thing correctly so I'm searching a good solution to run apache and dreamweaver as I did before I purchased rhino5. Why can't we configure the zoo port # ?? I agree with wolfgang.
If you only have one machine, then why are you using the Zoo?
The Zoo is useful if you have more users of Rhino than you do licenses of Rhino...
Unfortunately, when I installed Rhino (with the CD).. that's the way it did by itself..maybe I've checked the wrong option. I'm stuck now :)
To convert a Rhino 5 installation from a network node to a standalone node, follow these instructions:
When finished, you will no longer need Zoo 5.0 on your system.