upgraded PC hosting the Zoo server (v 8) to Win 11. Now unable to connect - ‘There was a problem communicating with … (the Zoo server)’.
Tried re-installing / repair. No change. Any known issues?
Hi Peter -
Have you taken a look at the Diagnostics page for the LAN Zoo?
-wim
1 Like
PING
Pinging server name [192.168.10.212] with 32 bytes of data:
Reply from 192.168.10.212: bytes=32 time<1ms TTL=128
Reply from 192.168.10.212: bytes=32 time<1ms TTL=128
Reply from 192.168.10.212: bytes=32 time=1ms TTL=128
Reply from 192.168.10.212: bytes=32 time=1ms TTL=128
Ping statistics for 192.168.10.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
NSLOOKUP
Server: DNS server
Address: 192.168.210.11
Name: server name
Address: 192.168.10.212
TRACERT
Tracing route to server name [192.168.10.212]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms server name [192.168.10.212]
Trace complete.
ZOOPORT
Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.10.212:80
ZOOECHO
Communication exception with “computer name”: There was no endpoint listening at http://server name/mcneel/zoo/5/client/basic that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
This was message from a workstation. However running diagnostic from the server indicated that port 80 was open.
ran through the steps to ensure port 80 is open on the server but no change - ZOOPORT and ZOOECHO still cannot connect.
.net 4.8 is installed
As described in the Zoo Diagnostics test descriptions, I suspect the Workstation is on a different Subnet than the LAN Zoo Host server.
The Port:80 rule on the Host server, needs to have the rule “Scope” changed to allow all subnets.
This is a task for your IT staff.
Any luck?
Checked that – changed to Allow All – no joy.
Hi @Peter_K,
The Zoo Diagnostic utility is meant to be run from the workstation that will be running Rhino.
If you run the Zoo Diagnostic from a workstation and tests 1 (PING), 2 (NSLOOKUP), and 3 (TRACERT) succeed but test 4 (ZOOECHO) fails, then the reason is usually one of the following:
-
The Zoo server service is not running. You can confirm the service us running by using either the Zoo Administrator (
ZooAdmin.Wpf.exe) or theServicesapplet Windows. -
Firewall software is blocking incoming or outgoing TCP Port 80 traffic. There is lots of information on the Zoo Wiki about opening TCP Port 80 in the Windows Firewall.
You’ve mentioned you’ve confirmed that TCP Port 80 is open for both incoming and outgoing traffic on the Zoo server system. But you want to have another look at this. I believe the Zoo installer tries to setup these port rules. Thus, if an older Zoo was working on this system, the installer might have modified any existing rule.
https://wiki.mcneel.com/zoo/window7firewall
Let me know if this helps.
– Dale
Confirmed Zoo service is running.
The current version of Zoo was an upgrade when we went to Rhino 8.
It was working fine until we upgraded to Win 11 from Win 10.
Hi @Peter_K,
From your Zoo server, open an administrative command prompt and run these two commands:
netsh advfirewall firewall add rule name="Zoo TCP Port 80" dir=in action=allow protocol=TCP localport=80
netsh advfirewall firewall add rule name="Zoo TCP Port 80" dir=out action=allow protocol=TCP localport=80
Does this help?
– Dale
no luck
What is the IP address of the computer from which you ran these tests?
192.168.10.66
Did you run from an elevated command prompt? Did the commanda finish with an OK message?
– Dale
yes and yes
I tried setting up zoo server on another machine to see if it made a difference. Same story.
Peter,
May I suggest checking the zoo server port is actually available from the client Rhino pc using a Windows test? That should show if you have a connectivity problem or a zoo/win11 software issue.
On the client PC, open a PowerShell window and run the command
Test-NetConnection -ComputerName *zoo-server-name-here* -Port 80
If the port is accessible, this will return (inter alia)
TcpTestSucceeded : True
If not, this will show False.
This was taking too long to assess, and we have work to do. So we are trying to go to Zoo Cloud. But that seems to have a separate (maybe related?) set of issues in that we cannot get the cloud to recognize we’ve removed the licences from the zoo server. Keep getting an error message when trying to install the keys in the cloud that they are still held by the server.
Tried this – it returned Failed.