McNeel Wiki

Site Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
zoo:diagnostics [2021/07/26]
dale [Diagnostics] 		zoo:diagnostics [2024/03/14] (current)
dale [Diagnostics]
Line 10: Line 10:
  
 =====Download===== =====Download=====
-{{:zoo:zoodiagnostics.zip|Download Zoo Diagnostics.}}+Pick to [[https://s3.us-west-2.amazonaws.com/docs.mcneel.com/Share/Files/ZooDiagnostics8.zip|Download Zoo Diagnostics]]
  
 [[zoo:diagnostics|{{:zoo:zoo_diagnostics.png|Zoo Diagnostics}}]] [[zoo:diagnostics|{{:zoo:zoo_diagnostics.png|Zoo Diagnostics}}]]
Line 28: Line 28:
 4. **Zoo Port Check:** The Zoo Port Check (ZOOPORT) diagnostic utility verifies that a Zoo service is listening on TCP Port 80 on a server or workstation. 4. **Zoo Port Check:** The Zoo Port Check (ZOOPORT) diagnostic utility verifies that a Zoo service is listening on TCP Port 80 on a server or workstation.
  
-//If this test fails, then make sure the Zoo server service is running. You can do this by using either ZooAdmin.exe or the Services applet in Control Panel. Also, make sure __[[zoo:window7firewall|TCP Port 80 is open on any firewall software]],__ for both incoming and outgoing traffic, running on the Zoo system. +//If this test fails, then make sure the Zoo server service is running. You can do this by using either ZooAdmin.Wpf.exe or the Services applet in Control Panel. Also, make sure __[[zoo:window7firewall|TCP Port 80 is open on any firewall software]],__ for both incoming and outgoing traffic, running on the Zoo system.
 // //
 +
 +// Also look at the results above from Trace Route. If you see multiple subnets in the list, you will likely need to change the firewall rules on your LAN Zoo server to allow connections from multiple subnets. See [[https://wiki.mcneel.com/zoo/homenetsh|Open TCP Port 80 in Windows Firewall Using Netsh]] for details.//
  
 5. **Zoo Connectivity:** The Zoo Connectivity (ZOOECHO) diagnostic utility verifies that the Zoo service is running on a server or workstation.  5. **Zoo Connectivity:** The Zoo Connectivity (ZOOECHO) diagnostic utility verifies that the Zoo service is running on a server or workstation. 
  
-//If this test fails and all other tests succeed, then make sure the Zoo server service is running. You can do this by using either ZooAdmin.exe or the Services applet in Control Panel. Also, make sure __[[zoo:window7firewall|TCP Port 80 is open on any firewall software]],__ for both incoming and outgoing traffic, running on the Zoo system.//+//If this test fails and all other tests succeed, then make sure the Zoo server service is running. You can do this by using either ZooAdmin.Wpf.exe or the Services applet in Control Panel. Also, make sure __[[zoo:window7firewall|TCP Port 80 is open on any firewall software]],__ for both incoming and outgoing traffic, running on the Zoo system.//
  
-//This test can fail if the client and server are on different subnets. By default, the Zoo installer opens the Windows Firewall to the Zoo service on port 80 for the local subnet only. You will need to change the firewall rule to allow all any other subnets that need access.//+//This test can fail if the client and server are on different subnets. By default, the Zoo installer opens the Windows Firewall to the Zoo service on port 80 for the local subnet only. You will need to change the firewall rule "Scope" property to allow all other subnets that need access.//
  
 //This test can also fail if your system is configured to access the Internet by using a [[https://en.wikipedia.org/wiki/Proxy_server|Proxy Server]]. In this case, the test never reaches the Zoo server. If you are using a Proxy Server, make sure you allow access to local addresses. See __[[zoo:zooproxyserver|Using Zoo with a Proxy Server]]__ for details.// //This test can also fail if your system is configured to access the Internet by using a [[https://en.wikipedia.org/wiki/Proxy_server|Proxy Server]]. In this case, the test never reaches the Zoo server. If you are using a Proxy Server, make sure you allow access to local addresses. See __[[zoo:zooproxyserver|Using Zoo with a Proxy Server]]__ for details.//
 +
 +6. **Set Your Zoo Server Name**
 +Type your Zoo Server name or IP. (//This is our DNS name. You need to provide your own.//)
 +Pick the button to same your Zoo server name or IP to the Registry.
 +The Zoo server name is written to 
 +//Computer\HKEY_LOCAL_MACHINE\SOFTWARE\**WOW6432Node**\McNeel\Rhinoceros\x\License Manager// where **x** is the version of Rhino. 
 +{{:zoo:setzooserver2.png?400|}}
  
 =====Related Topics===== =====Related Topics=====
-[[zoo:diagnosticsmac|Zoo - Diagnostics Utility for Mac]]+  * [[zoo:diagnosticsmac|Zoo - Diagnostics Utility for Mac]] 
 +  * [[https://wiki.mcneel.com/zoo/findzooserverwin#rhino_8_7_and_6_for_windows|How Does Rhino for Windows Find a Zoo Server?]] 
 +  * [[https://wiki.mcneel.com/rhino/installingrhino/7|Automating installation Rhino 7 for Windows: Scripted Install]] 
 + 
zoo/diagnostics.1627341847.txt.gz · Last modified: 2021/07/26 by dale

Page Tools

© 1997-2024 McNeel • North America • Europe • Latin America • Asia • Korea     Recent Changes RSS Feed Driven by DokuWiki