| Search |
Languages
Related Topics
Zoo Overview, Features and FAQ
Zoo Installation and Configuration
Overview
The Zoo uses a simple, protocol-independent messaging technology called Mailslots to communicate with Rhino. Microsoft networks use mailslots messages in a variety of areas, including domain logon service. Mailslot messaging works on all modern Microsoft operating systems. Mailslot messaging works on both Workgroup networks and on Domain networks.
In terms of configuring the Zoo, there really is nothing to do. As long as all machines involved belong to the same Windows Domain or Workgroup and are installed on the same subnet, then the Zoo should be able to allocate licenses upon request. A couple of things to keep in mind when working with the Zoo.
- Make sure you are running the latest version of the Zoo.
- Make sure you are logged in as the Administrator or as a member of the Administrators group when running the Zoo.
- Make sure you are running the latest service release of Rhino and other Zoo-supporting plug-ins, such as Brazil, Bongo, Flamingo and Penguin.
Application Notes
- The Zoo will run on Windows 2000, Windows XP, Windows Vista, Windows Server 2000 and Windows Server 2003 systems.
- The Zoo requires that the Microsoft C++ 2005 SP1 Redistributable Package (x86) be installed on the system.
- The Zoo will not work with Rhino 2.0 or 3.0 Educational or Educational Lab licenses (CD-Keys).
- The Zoo will not work with Rhino 2.0 or 3.0 running on Asian versions of Windows.
- Not all products are capable of acquiring licenses across a routed network. The products that support the Zoo running on a routed network includes:
- Rhino 4.0 SR3 or greater
- Brazil 2.0 or greater
- Flamingo 2.0 or greater
- Penguin 2.0 or greater
- You should be logged in as the Administrator or as a member of the Administrators group when running the Zoo.
Networking Notes
- All systems must belong to the same Windows Domain or Workgroup.
- Make sure the network connection that you are using has the Client for Microsoft Networks installed and enabled. Otherwise, you will get Failed to write to client mailslot errors written to the Zoo log file.
- If you using TCP/IP, make sure to Enable NetBIOS over TCP/IP in the advanced TCP/IP options. Otherwise, you will get Failed to write to client mailslot errors written to the Zoo log file.
- If the computer running either Rhino or the Zoo is using a firewall, be sure that the following ports are open:
- UDP Ports 137 and 138
- TCP Port 139
- Note, these are ports that Windows uses for NetBIOS communications. If you are using the built-in Windows Firewall, you will want to enable File and Printer Sharing as an allowed exception.
- If you have not configured your Rhino systems for either DNS or Registry Key lookup, then all Rhino workstations and the system running the Zoo must be installed on the same network subnet. This is because both Rhino and the Zoo will broadcast messages. Broadcast mailslot messages will not cross network routers and some switches. Wireless routers will also not forward broadcast messages.
Zoo Notes
- Make sure the user who is logged into the Zoo server has sufficient privileges to run the Zoo. Otherwise, the Zoo will display a Unable to create a mailslot message at startup.
- The Zoo does not run as a service - it is a regular Windows application. This means that you must log in to the computer and start the Zoo if you reboot the server.
- The Zoo can maintain a log file (ZOO.LOG) of conversations with Rhino clients. The log file can be useful in diagnosing some communication problems. If you do not see a log file in the same folder as ZOO.EXE, then you can turn on logging by selecting Tools->Options from within the Zoo application. Check the log file, using NOTEPAD.EXE, to see if Rhino messages are making it to the Zoo, and that the Zoo is responding to these messages.